Overall Satisfaction with InVision
InVision is used by our UX team in order to stitch together prototypes. Often we create mockups and wireframes in Sketch, import them into InVision, add hotspots and scroll zones to the screens, and link the screens together in a clickable prototype that can then be shared with customers externally, or our developers internally.
- InVision is great for putting together prototypes because it's fast and simple.
- InVision is great for giving specs to your developers that they can inspect because it gives them the information they need to build it.
- Large InVision prototypes can often be slow on mobile phones because they have to download so many screens.
- InVision prototypes are pretty limited in terms of functionality.
- InVision has helped us to validate ideas with customers before investing time and effort with development.
- InVision has helped reduce the need to go back and forth with development on mockup specs.
Other design tools have been creating their own prototyping functionality, which has made InVision less valuable over time. It is much more convenient to use the same tool for both design and prototyping, because it removes the unnecessary steps of exporting, importing, and syncing. InVision has tried to solve this by creating their own design tools. However, their design tools just aren't up to par with other design tools.
InVision is great for app flows and simple screens stitched together. It's also great when you have pixel-perfect mockups for your developers to inspect. Where InVision struggles is in making advanced prototypes with custom animations, interactions, and dynamic content. In addition, InVision prototypes don't allow you to use keyboard input from a user, making it difficult to truly test usability with forms and other input-heavy applications.