The company discontinued its design collaboration services, prototypes, Inspect, DSM, boards and the rest, on December 31, 2024, and everything stored in an account was deleted at the end of that day. Freehand, the visual whiteboard piece, had already been sold to Miro in 2023. So none of what follows is something you can sign up for and try today. It is an account of what the tool did well across the years my teams actually ran on it, written while the memory of using it daily is still close.
The prototype sharing link was the thing that made InVision matter, and it is the thing I missed first once it was gone. The workflow was simple in a way that is easy to undervalue now that everyone expects it. I uploaded a set of static screens, wired them together with hotspots, and got a single URL I could send to a client or a product owner. They clicked through the flow on their own machine, on their own time, no software to install and no account hoops in the early days. Before this existed, showing a flow meant a screen share on a call, or a folder of flat PNGs with arrows drawn on them, or worse, a slide deck pretending to be an interactive product. InVision turned a pile of artboards into something a non-designer could navigate and reason about, and that one capability reset how stakeholders expected to receive design work.
Craft Sync was the piece that made the prototype side bearable to maintain. I worked primarily in Sketch for most of the InVision years, and the Craft plugin pushed selected artboards straight into an InVision project without an export step. Save in Sketch, sync, and the screens updated in the prototype. The alternative, which I lived through before Craft matured, was exporting images by hand and re-uploading them every time a screen changed, which is exactly the kind of friction that quietly kills a tool inside a team. With Sync, keeping a prototype current stopped being a chore I dreaded and became a button I pressed without thinking. It was not flawless, syncing over a slow connection at a client site could be genuinely painful, but on a normal day it did its job.
Contextual comments pinned to the screen were where InVision earned its keep on the collaboration side. A reviewer did not have to describe where the problem was, they clicked the spot and left the note right there. When I shared a flow with five stakeholders across three time zones, the feedback came back attached to the exact pixel it referred to, instead of arriving as a paragraph in an email that I then had to translate into a location on a screen. That single behavior collapsed a whole category of back-and-forth. I could open a screen, see every comment threaded against it, mark them resolved as I worked through them, and have a clean audit trail of what was raised and what was addressed. For client work especially, that record mattered as much as the feedback itself.
Inspect was the developer handoff feature, and it was the part that justified the subscription line item to people who were not designers. Once a prototype was synced with assets marked for export in Sketch, a developer opened Inspect mode and pulled dimensions, hex codes, font details, spacing and downloadable assets straight from the screen. No redline document, no designer sitting next to a developer reading off measurements, no Slack thread asking what shade of grey that divider was. The developer self-served the spec. On teams where design and engineering sat in different rooms or different companies, Inspect removed a daily source of interruption for me and a daily source of guesswork for them. It also slotted into a Jira workflow, so a prototype with Inspect enabled could hang off the ticket the developer was already looking at.
The integration posture in general was a strength while it lasted. InVision positioned itself as the collaborative layer on top of whatever design tool you actually drew in, Sketch first and most deeply, but it accepted uploads from Photoshop and Adobe XD too, and later connected to the Jira and Confluence stacks teams already lived in. The pitch was that you did not have to abandon your drawing tool to get collaboration, prototyping and handoff in one place, and for a good stretch that pitch held. It meant I could standardize a team on InVision for the shared layer without forcing everyone onto one design application.
DSM, the Design System Manager, was the ambitious part, and when it worked it was genuinely useful for keeping a team consistent. The idea was a living library of components, colors and text styles that designers pulled from and that stayed connected back to the source. On larger projects, having a single place that defined what a button or a type ramp actually was, rather than every designer reinventing it per file, cut down the slow drift that turns a tidy design system into a mess six months in. I will be honest about its limits in the next section, but the intent was right and the basic version of it saved real rework.
Ease of onboarding for non-designers deserves a specific mention, because it is the reason InVision spread inside organizations rather than staying a designer tool. I handed prototype links to executives, marketers and clients who had never touched a design tool, and they figured out clicking through a flow and leaving a comment within a minute or two. There was nothing to learn. That low barrier is why a design team could pull the whole company into the review process instead of presenting to it, and pulling people in is almost always the better outcome. Review collected by and hosted on G2.com.
The bigger structural problem was that InVision was never the place you actually designed. It sat on top of Sketch or Photoshop or XD, which was the whole pitch, but it also meant the moment a single tool could do design, prototyping and handoff in one canvas, the multi-tool dance InVision required started to look like overhead rather than a workflow.
When Figma arrived with real-time design and prototyping in one browser tab, the question stopped being which features InVision had and became why I was round-tripping between two tools at all. InVision's answer to that was too slow in coming and never convincing.
Cost was a recurring sore point, particularly for smaller teams and independent practitioners. The pricing added up quickly once you were past the most basic usage, and there was a real sense of being nickel-and-dimed, including charges that gated archived projects. For a freelancer or a small studio watching every subscription, InVision sat in the bracket where you regularly asked whether it was worth it, and toward the end the answer kept tilting toward no. Review collected by and hosted on G2.com.
