This is a very good idea. I see a lot of friction (and lack of process) with product -> UX -> dev than with product and dev able to iterate on things like screen flows very quickly, and UX feeding in more from the user research angle.
Currently a lot of UX work is "translate what you said into Figma and wait for comments" which is very automatable, and I think frustrating for UX people as much as anyone.
I just had a cool experience with it doing some simple design. It prompted back to me usefully as well.
I can imagine also uploading a component library that this thing then uses the components from, to add styling for higher-fidelity designs, and allow app designers/builders to just use the components built by an internal team (who might also use magic patterns, I suppose).
Comments
This is a very good idea. I see a lot of friction (and lack of process) with product -> UX -> dev than with product and dev able to iterate on things like screen flows very quickly, and UX feeding in more from the user research angle.
Currently a lot of UX work is "translate what you said into Figma and wait for comments" which is very automatable, and I think frustrating for UX people as much as anyone.
100%. This is what we hear and see from our customers, many now skipping Figma entirely.
I shared this post before below, but to share it again: https://www.linkedin.com/posts/stephenwitmer_you-gotta-love-...
I just had a cool experience with it doing some simple design. It prompted back to me usefully as well.
I can imagine also uploading a component library that this thing then uses the components from, to add styling for higher-fidelity designs, and allow app designers/builders to just use the components built by an internal team (who might also use magic patterns, I suppose).