I see what you are saying and for very specific problems/explorations I do still reach for Figma. But the days of crafting static screens and multi-artboard flows are gone. It's better to prototype the entire flow/interaction directly than trying to reason about it 'statically'. LLMs have also opened up an entire array of new possibilities for e.g. combining meaningful 3D and taking a 'leap of faith' into visualizations/interactions that would simply be too costly to properly explore before
> But the days of crafting static screens and multi-artboard flows are gone. It's better to prototype the entire flow/interaction directly than trying to reason about it 'statically'.
I haven’t found this to be true but it could well come down to the type of design work I do. I’m usually working on new features for complex workflows within an already complex app. When I’ve tried to yolo designs with LLMs they never come up with elegant visual or UX solutions. They’ve been occasionally useful as a way to get something on the screen that I can work against — ie “well that’s clearly wrong in these 20 ways” — but at that point I usually then reach for figma so I can just do the damn thing myself.
Agree about the more complex design options it opens up, I just haven’t had call to do much in those spaces yet.