product designers are the architects of software.

architects create blueprints, instructions for others to hit hammer to nail.

what if architects could create blueprints for cranes, instead?

in other words, why are you, a product designer, using figma instead of vibe coding?

Because mostly design is about rapid iteration. 

which is done via blueprints and prototyping, not full fledged production. 

better to let a skilled builder/engineer take care of implementation so you can focus on gauging user needs and translating them in product design.

designing for consumer trust // prev UX + protocol-design at rara.social // EV winner @Mercatus // IIT Kanpur CS // IRL host - walk & talk club, Chandigarh

prototyping is prototyping 

you can choose the tools that you are most comfortable in. 

most vibecoding is about prototyping

its faster to vibe code then create it in figma