Do you maintain a Figma prototype of your product?
Lorant Toth
3 replies
I know that many designers and design teams struggle with maintaining a high-fidelity prototype of their product, and they think the invested work doesn't pay out.
I think with the right approach the prototype should be a byproduct of the design workflow, and it represents the user flow much better than static screen designs. Having a prototype to explain your product to non-technical people, like investors can be a huge benefit for an early stage startup.
We've launched Templates for Once UI to provide a framework for crafting high fidelity prototypes. Learn more about it in our recent launch: https://www.producthunt.com/post...
What's your take? Do you think your business would benefit from a high fidelity prototype of your product?
Replies
Jonathan Ho@jonathan_ho4
We're a mobile app - once we got into Test Flight and then released, we didn't go back to Figma unless it was new features, but I am curious about workflows where Figmas are maintained post release
Share
@jonathan_ho4 I suppose you're a fairly small design & dev team, and it makes perfect sense to not rely too much on Figma when making small adjustments in this case.
Though as your team scales, you might want to consider syncing Figma designs with your app as much as you can. Sure, sometimes it feels unnecessary - for example, you just want to change a word here and there, why would you need designs for that?
Well, sometimes not for development, but for future-proofing. All of these minor adjustments will stack up on the long run, and at one point you'll have two completely different realities of your product at the same time, resulting in miscommunication and eventually frustration.
I've seen some teams deliver extraordinary product quality whilst having pretty poor Figma designs. With the right approach, it can happen, but more often than not a poor Figma structure results in poor product quality.