The rise and fall of InVision (2021)

uxdesign.cc

9 pointsianhawes3 comments

> We can certainly point to the meteoric rise of Figma as being a key factor, but that alone is too simple.

I think it's just simple enough.

Going from a Sketch + InVision + Zeplin workflow to a Figma workflow was a revelation. Figma replaces those 3 products, and does a better job of all of them, plus it adds a lot of new things (multiplayer alone would sell most teams on it, but you could name 10 other killer features).

For a lot of designers, the first time they tried Figma, they didn't ever want to go back.

At that point, it didn't matter what InVision did in response, they never stood a chance.

So what’s the deal on realistically being able to generate something based on Figma? For example - if I have a custom UI framework can I generate a skeleton my front end team can use?

And second - how much “behavior” can we write in to the generated artifacts?

If this is nonsensical lmk. From the marketing materials it looks like there’s something neat there that InVision can’t do for me.

Archived link: https://archive.ph/qnJbQ

Reply on news.ycombinator.com