Designing for code - John Meguerian (Config 2021)

Everyone on a product team is working together to make one thing: real software in the hands of their users. Design mocks are simply a communication tool in service of this shared goal. But the way a typical design file is structured does not set the team up for success. In fact, they result in unnecessary cycles of work for the whole product team. In this talk, John walks us through how and why design files should mirror how the design will be implemented.

0:00 Introduction
2:22 Design files are a communication tool
3:17 Why?
6:09 How?
14:03 When?
15:14 So What?
18:00 Conclusion

#figma #config2021 #InTheFile #config #design #ProductDesign #FigmaDesign #DesignforCode #Code #Squarespace #SquarespaceDesign #FrontendDeveloper

[fastphoud]

So much realness in this talk. This is day-to-day what a good UI designer does, and what a lot of people don't understand about "UX/UI". Also thank you for emphasizing on the communication. I hope devs will also watch this talk :)

[Leonardokoss]

To me, the best talk in ConFig 202. Thank you!

[senior_java]

Figma + React + StyledComponents = Game Changer for entire industry!

[senior_java]

This should have 243K views instead of 2K.

[leeboyin]

Should designers code?
Should devs design? (This is the topic of another talk!)
I believe we should learn each other's tool to bridge the gap in between and build trust.
So as a frontend developer, I'm currently learning Figma to understand how designers design.

[the.aydinabbas]

It is a very necessary topic. Thank you!

[jwoods]

NO reason not to learn how to code. Learn everything you can