Web designer and web developer are not the same job

People say “I need a website” and mean three different jobs: what the site is for, how it should look and move, and how it should actually work in a browser. A web designer owns the first two. A web developer owns the third. Some people, myself included, work across that line — but the line is still real.

What a web designer decides Who the site is for. What happens on the first screen. The order of pages. Type, space, color, states of a button, how a form should feel. In other words: the experience, including UI/UX.

What a developer decides How that experience is built: HTML structure, performance, forms that submit, languages, CMS, shop logic. A developer can make a weak design load fast. They cannot invent a missing strategy.

Why the overlap exists On the modern web, a designer who cannot think about markup will design things that cannot be built well. A developer who cannot see hierarchy will build things that technically work and still feel cheap. Frontend is the shared room.

How to hire without wasting a month If you have a clear structure and only need it built, you need development. If you have a product and a messy first impression, you need design first — then implementation. If you want both in one conversation, say so. Do not assume “web designer” includes a native app, and do not assume “developer” includes taste.

I design and implement websites as one process when that is the brief. App native engineering is a different craft. For the design side, see UI/UX and web design.