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
What's worse is treating engineers like "just implement the mockup eyeroll" but then the logic of the mockup makes no sense with real data or product.

I'd rather have a napkin sketch that we can work on together vs throwing pictures over the wall.

As impressive as it is, I feel like Figma makes this situation worse. It's like "see we've figured it all out devs, look how nice this looks. No discussion needed"

>>gedy+Gl
they always use text that is ideally sized in mock-ups but completely falls over when real data is used in a responsive web app.

My favorite is when design adds data to a mock-up that we don't actually have. My company is, admittedly, a bit of a joke.

Also up there: design giving us mock-ups that are a composite of shit that needs done today and future shit they still haven't decided on. And then demand review approvals. No. You can't have it both ways you fucking morons. Either give me exactly what needs to be done, or you get no review rights. I'm not going to sit here for three weeks of back-and-forth while you play hunt-the-pixel and giving me hell for not matching the fog in your own head.

>>deckar+zr
> responsive web app

That's my favorite - if you mention responsive or how things should wrap or cascade you get the blank stares or "we aren't solving for mobile right now"

>>gedy+Xv
That's one of the few things done right at my previous consulting gig. They were mobile first, and didn't even start putting up a desktop web version until they had the core functions of mobile working they way they wanted.