The Problem with Photoshop
The web used to be hideous—envisioned by engineers, it was hard to navigate and ugly to look at. To flourish with users, it desperately needed professionals to provide what print already had: stability, usability, and cohesiveness. And so designers like us were called in to create attractive, coherent user interfaces before a developer wrote a line of code.
Fast forward 20 years—while today’s web designers have tools available to them—like Photoshop—that make early design apps look positively prehistoric, the process of translating designs into websites has hardly evolved at all. Designers still hand their carefully-honed vision off to front-end developers who take the desired look of the website and attempt to create the same thing in a completely different medium: code.
Sound challenging? Add to it that today’s web apps are more complex than ever, and that the design and dev teams are often working in silos and speaking different languages, with a project manager in the middle to translate and iron out inevitable issues, and it becomes very challenging.
It’s Broken; Let’s Fix It
For things to get better, some things need to change, the main thing being the way web designers—whose titles are morphing into Web UI Developers—do their jobs. Continuing to design in programs like Photoshop just doesn’t make sense. Since the web’s medium is code, shouldn’t we use code to design in the first place?
We are well past the days of creating simple, static web pages. Now we design user interfaces that our audience interacts with on many devices in various sizes. More and more, we think about mobile first. This shift requires new tools and a new approach to web design.
Even HTML & CSS Are Not Enough
Web apps are systems that can produce dynamic content. Even whole UI components can be delivered on demand. This changes everything. A base-level knowledge of code can only go so far. To be effective, you need a clear understanding of how a back-end system interacts with the front-end code you’ve written.
The Great Divide
Historically, designers and developers haven’t understood enough of each other’s process. There would be two distinct teams working on the same end product, which created an unhealthy dynamic where each side had its own agenda, rather than a single, common goal.
UI developers working in code who understand their development partners better, and vice versa, creates a strong team that allows for better front-end to back-end integration and enables both partners to learn about the other’s outlook on the project. The outcome is a better relationship between the roles and a better product overall.
Enter UI Developer
Web UI Developers not only design user interfaces, they may also develop living UI style guides that help solidify and document an application’s user interface and must possess a high-level understanding of how to develop user interfaces that are ready for back-end integration. They are designers at heart who use code to create.
The demand is high for people who possess both design and development skills. Their scarcity leaves many high-paying positions open or partially filled.
According to Glassdoor, last year the average salary for a UI Developer was $75,000 (and rising). There were 1.3 million unfilled UI/front-end positions, a number that’s expected to rise 28% by 2018. Graphic designers, by comparison, had an average salary of $50,000. There were only 200,000 open graphic design positions and growth is projected to be just 7%. Those are staggering numbers that highlight the shift in the market towards designers who can code.
UI at Code Fellows
What does this mean?
If you are a UI Developer, you need to become immersed in the ecosystem you’re designing for. Design for the web with code to increase the cohesiveness of your team and the quality of your product.