From Color Schemes to Code: How Designers & Developers Can Learn from One Another
As a designer, there is a tremendous amount of pressure to learn how to code. Or not…depending on which article you read. Instead of focusing on learning another language, there is another side to thinking about how to design for development. This includes communicating with your team, sitting in on meetings, and knowing the limits of what a software developer can do (even if you really, really like that animation). On the flip side, the developer has a lot to learn from the designer, whether it be design guidelines, asset gathering, or just if that one picture should be 5 pixels more to the right. There’s plenty to learn!
I will focus on ways a designer can think through their designs to include the best interests of the engineer and some helpful technologies and terms they should familiarize themselves with. Then I’ll switch gears and introduce a design primer that will help a developer should they ever need to decipher the why’s behind a mockup. After all, communication is key, and a project goes more smooth when both sides are on the same page, er, screen.
