4 ms·

That’s not figma’s fault, that’s a team communication and workflow issue. We have that at work too and the solution is to communicate. Have a big red box with t

That’s not figma’s fault, that’s a team communication and workflow issue. We have that at work too and the solution is to communicate. Have a big red box with text saying the modal is not ready, or simply don’t have a modal until it’s ready. Better stick, create placeholder components and use those. Replace when ready.

Stevvo 6y ago
Agreed. In my company, your responsibility as a developer is to implement the design as shown on figma, pixel perfect. If something is incorrect on the design, someone will usually have noticed it and fixed it before I get the chance, because there are 4 sets of eyes on it (CTO, PM, Designers, Developer)
- waheoo 6y ago
  I hope this is sarcasm.
  - geoffw8 6y ago
    Seems pretty reasonable to me. If it’s a rough wireframe it can be just that, rough. If it’s a pixel perfect mockup then it’s a contract for final product IMO. Of course whether there are that many sets of eyes on it depends how big a co you’re working for!
    - gitgud 6y ago
      Pixel perfect? So if a css box-shadow is 11px instead of 12px someone will notice? ...I don't think so Maybe if the pixel perfect design is diff'd against the final product...
  - deleted 6y ago
    [deleted]
- nojvek 6y ago
  It depends on what is being built. Pixel perfect on the first iteration is not a great idea. Because on the first iteration we are usually trying to figure out “does this even solve the problem” and show that to users. After many iterations you have a rough plan. Then you build a quirky mock with existing components you have. Then you let users play with it and find existing rough edges and smooth them out. Then you build a much nicer version (perhaps pixel perfect) and then have a lot of users play with it, and then your analytics funnels tell you where the bottlenecks are. So you make even more iterations until you make something that solves the problem in a delightful manner and users are going bonkers about it. The TLDR is, there is no point getting pixel perfect in the first iteration. Good software requires tons of iterations and the entire pm-design-eng-user workflow should be optimized for faster iterations and learning. A good design system + mockups get your that.

Stevvo 6y ago

Agreed. In my company, your responsibility as a developer is to implement the design as shown on figma, pixel perfect. If something is incorrect on the design, someone will usually have noticed it and fixed it before I get the chance, because there are 4 sets of eyes on it (CTO, PM, Designers, Developer)

waheoo 6y ago
I hope this is sarcasm.
- geoffw8 6y ago
  Seems pretty reasonable to me. If it’s a rough wireframe it can be just that, rough. If it’s a pixel perfect mockup then it’s a contract for final product IMO. Of course whether there are that many sets of eyes on it depends how big a co you’re working for!
  - gitgud 6y ago
    Pixel perfect? So if a css box-shadow is 11px instead of 12px someone will notice? ...I don't think so Maybe if the pixel perfect design is diff'd against the final product...
- deleted 6y ago
  [deleted]
nojvek 6y ago
It depends on what is being built. Pixel perfect on the first iteration is not a great idea. Because on the first iteration we are usually trying to figure out “does this even solve the problem” and show that to users. After many iterations you have a rough plan. Then you build a quirky mock with existing components you have. Then you let users play with it and find existing rough edges and smooth them out. Then you build a much nicer version (perhaps pixel perfect) and then have a lot of users play with it, and then your analytics funnels tell you where the bottlenecks are. So you make even more iterations until you make something that solves the problem in a delightful manner and users are going bonkers about it. The TLDR is, there is no point getting pixel perfect in the first iteration. Good software requires tons of iterations and the entire pm-design-eng-user workflow should be optimized for faster iterations and learning. A good design system + mockups get your that.