The difference between a designer and a developer.

Getting Started · 6 min read

I get this question more than any other. "Do I need a designer or a developer?" The answer is both. But in a specific order. And understanding the difference between the two is probably the single most important thing a first-time founder can learn before spending any money.

Most people outside the tech industry use "designer" and "developer" interchangeably. Or they think a designer just makes things look pretty while the developer does the real work. Neither of those is true. They're completely different disciplines, with different skills, different tools, and different roles in the process. And the order you engage them matters enormously.

What a designer does

A designer figures out what you're building. Not in a vague, conceptual way. In a detailed, screen-by-screen, interaction-by-interaction way. They research your users. They map out every flow in the app. What happens when someone signs up? What do they see first? What happens when they tap this button? What happens when the list is empty? What does the error state look like?

Then they turn all of that into wireframes, which are structural layouts without visual styling. Then into visual designs, which add colour, typography, spacing, and brand. And finally into a prototype, which is an interactive version you can tap through on your phone. It looks and feels like a real app, but there's no code behind it.

A good designer also writes developer notes. Detailed documentation that explains every decision, every interaction, every edge case. These notes are what the developer uses to build the app. The better the notes, the less the developer has to guess. And guessing is expensive.

What a developer does

A developer takes the designs and builds the actual working app. They write the code. They set up the database. They connect the backend services. They handle authentication, payment processing, push notifications, and everything else that makes the app functional. Their job is to turn the designer's blueprint into something that actually runs on a phone.

Developers also handle testing, bug fixing, performance optimisation, and deployment to the App Store and Google Play. It's technical, detail-oriented work that requires a completely different skill set from design. Some developers have a good eye for design. Some designers can write code. But specialisation exists for a reason. Trying to do both usually means doing neither well.

Why the order matters

Here's where it gets expensive. When someone skips the designer and goes straight to a developer, the developer has to make design decisions. What should this screen look like? How should this flow work? What happens in this edge case? They'll figure it out, but they'll figure it out as engineers, not as designers. The result is usually an app that works but doesn't feel right.

Research from the Nielsen Norman Group consistently shows that fixing a problem during development costs ten times more than fixing it during design. And fixing it after launch costs a hundred times more. The design phase is where problems are cheap to solve. Every decision you defer to development becomes a more expensive decision.

Design first. Then develop. That's not a preference. That's the process that protects your budget and produces a better product. You wouldn't build a house without plans. Don't build an app without designs.

Sources
UX Design Process (Nielsen Norman Group) - Why discovery and design must precede development.
Design Thinking (Interaction Design Foundation) - How the design process reduces risk and cost in product development.

Related blog posts:

What to look for when hiring an app designer →

Your timeline is wrong →

A prototype is not an MVP →