[jauntywundrkind]

Worrying about wasted effort spent breathing some life into a mockup/prototype

vs Worrying about creating some figmentary Figma imaginarium that wont translate well into the actual app

I do think there is a risk, it's just not of throwaway code (the effort of that throwaway is vastly smaller than what this path replaces). The risk is more how & where the future could be constrained. If the prototype starts becoming the app, there's some risk the prototype imposes poor app architecture. If the prototype starts becoming the app the effort to mock/prototype new ideas risks becomes higher.

I strongly agree with the parent about getting in there & trying things semi live, not being afraid to wade in. The component offerings are excellent today, don't wire most of them up, just throw them on the screen as best you can & put in minimal stitching or hardcode a forward/back through states.

The fear of this going bad is way outsized. The design industry needs to get where the puck is going & stop playing around with fancy abstract design tools.

[brigadier132]

I don't code and design at the same time because I've noticed from experience that it's slower and gives worse results than designing first and then coding.

The wasted effort is one factor to it but another factor may be that I'm able to just focus on design and ux more and not think about implementation.