Abstract vs. InVision

• Large teams with dedicated design operations support
• UX managers that want a facilitated workflow for their teams
• Disciplined teams of individual contributors that want to adopt a process in their UI workflow
• Cross-discipline teams that want a central collaboration space for reviewing and critiquing UI artifacts
• If your files are named "FOR-REALS_FINAL_FINAL_FINAL_Super-Important-Project (copy).sketch"
• If you're managing multiple pattern libraries

Incentivized

InVision is well suited for design reviews and immersing yourself in the experience of an app-to-be. As a Product Manager, it's difficult to take abstract concepts, user pain points, and business needs, and produce a vision for an app without a visual aid to communicate a vision. InVIsion offers PMs, designers, and developers the opportunity to sketch a vision, communicate about it with inline commenting, and shareable with other stakeholders.

Incentivized

• Versioning for desginers
• Collaboration between team members

Incentivized

• Very easy to export Sketch files (where prototypes are actually created) into Invision and preserve the interactivity.
• Additional interactivity can be added in InVision. Like scrolling with locked footer.
• Clients, designer and developers can collaborate - leave notes and respond to notes made by others.

Incentivized

• Asset exports are not as great as Zeplin and others.
• Filtering within files.

Incentivized

• would be nice to have commands for quick access to shapes from the keyboard
• Quicker integrations with Notion and lucid chart to have a slick experience
• The auto organize option should have multiple frame selection, sometimes is not the arranged expected for the wireframe

Incentivized

it does what we bought it for, so would buy again :)

Incentivized

Abstract has a difficult learning curve. If a feature-branch workflow is new to you, then it will take some getting used to. They make a lot of updates to the interface and these feature releases get ahead of their documentation. They rely heavily on an excellent customer support team and are present on various Slack channels to help design professionals with issues.

Incentivized

Easy for prototyping, sharing for comments and review changes with version. lags a bit when the design is heavy and large design models learning curve is shorter so saves time with new stakeholders responsiveness could be better and auto modeling can be introduced Not much advance features that can be used

Incentivized

Abstract by nature is complex and has to respond to whatever changes in Sketch. So there are frequent issues. Support can be slow to respond and are not always helpful, but they are quick to find and patch the bugs. Overall, it's not the best support, but it hasn't been detrimental.

Incentivized

I didn't need to contact InVision support, as I've never needed it. They have an intuitive UI, and most of the questions are answered in their help portal or in tutorials online. Since many people use it, there a great resources available on for example YouTube. No problems so far with InVision.

Incentivized

I purchased and administer Abstract. It was requested by our design department who evaluated it.

Incentivized

We only tested out using Adobe XD for similar uses and found it to be more challenging to fit within our processes. It didn't have as robust a set of capabilities as InVision and wasn't as easy to use enterprise wide. I recall also having issues with working with Sketch.

Incentivized

• Single source of truth for the team.
• Could quickly get expensive with corporate accounts.

Incentivized

• InVision helps our team better and more professionally portray the value and the work we do as designers, leading to more company buy-in in supporting and funding our work. In the past, we would create PowerPoints with screenshots to portray a user workflow that we would share out to stakeholders. Once we began to use this app, where stakeholders could click through and comment as though they were “real” users, stakeholders began to better understand our work, designs, and workflows. This has led to more productive conversations that, in turn, lead to more effective end products that have more consistently served our business goals in tangible ways.
• InVision helps us save production time, effort, and cost, as we are able to solve design issues early in the process by having clickable prototypes to show to internal stakeholders and external users. It’s, understandably, difficult for people to provide effective feedback on screenshots. Using the clickable prototypes we created in InVision, we are able to get more effective feedback to solve user workflow issues before we spend time and money developing problematic designs (and later having to redesign them).
• It’s easier to market designs to potential buyers with clickable prototypes than with screenshots. With these prototypes, we’ve been able to sell more digital products before product release dates, which has helped to secure many contracts and new business relationships that continue to this day.

Incentivized