zlacker

>>emilsj+(OP)
Has anyone else worked with teams where their entire idea of "product" was to create 100s of designs in Figma, and then just hand them to developers?

What started this mentality?

>>roflye+pc
I'm curious what you'd prefer, a requirements document? Powerpoint slides? Photoshop files with a grid layer?

The best designer I ever worked with did full HTML/CSS mockups but even those had to be rewritten into the development framework of choice.

To me Figma is a step up from the other ways I used to get designs.

>>CSMast+xc1
If you want a figma, I'd prefer if you worked with a dev before making it, then also worked with them after making it, to get on the same page.

Creating a design out of whole cloth and handing it over to a dev, with minimal interaction, seems lazy.

The problem isn't figma - it is how it is being used. I do think that figma is super super overkill, as if you pick a good design kit what's the point? Lots of wasted time.

I don't see the point of doing all the extra work, when in reality a wireframe works better in most cases (doesn't set you up for the "why doesn't it look like the figma" responses)