Service 03

UI/UX

Design that survives contact with real content, real browsers and real users. We draw it and then we build it, so nothing gets lost in a handover.

Sub-services

What's included.

Every line below is something we do in-house. Take the whole service or one piece of it.

UX research & flows

Who uses it, what they're trying to do, and where they currently give up.

Wireframes & prototypes

Clickable structure agreed before anything gets styled.

UI design

Screens designed against your real content, not placeholder text.

Design systems

Components, tokens and rules so the tenth page still looks like the first.

Landing & conversion design

Pages built around one action and measured against it.

Responsive design

Works at 360px, works on a laptop, works on the tablet in your showroom.

Accessibility

Keyboard paths, contrast and semantics checked as we go, not audited at the end.

Redesigns & audits

A clear read on what your current site is costing you before anyone redraws it.

Process

How we run it.

  1. 01

    Understand

    Your audience, your competitors and the jobs the site has to do.

  2. 02

    Structure

    Sitemap, flows and wireframes — the argument before the aesthetics.

  3. 03

    Design

    Full UI against real copy, in light and dark where it applies.

  4. 04

    Build

    We implement it ourselves, so the built page matches the design.

Designed here

Three apps, three different jobs.

Bite is a marketplace, so it is really three products: someone hungry, someone cooking and someone riding. We drew every screen in all three — and then built them — so a customer, a restaurant and a courier never see the same order described three different ways.

Screens from all three Bite apps — customer, restaurant and courier
Bite customer app — browse, order and track
Customer
bite Vendor — orders, menu and payouts
Restaurant
Bite Rider — shifts, jobs and zones
Courier
Read the Bite case study

Stack

What we build with.

Chosen per project — this is what we reach for most.

  • Figma
  • Design tokens
  • WCAG 2.2
  • Framer
  • Adobe CC
  • Lottie

FAQ

Questions we get asked.

Can you design without building?

Yes — you'll get a full system and a spec your developers can work from. We just think the result is better when the same team does both.

Do you use templates?

No. We use our own component system as a starting point for speed, but the design is drawn for your brand and your content.

What if we already have a brand?

We work inside it. If the guidelines have gaps — and they usually do for web — we extend them and hand the extensions back to you.

How many rounds of revisions?

Two structured rounds per stage are built into scope. In practice, agreeing the wireframes early is what keeps that number low.

Tell us the riskiest
thing about your idea.

Thirty minutes. We'll tell you what we'd build first, what we'd cut, and roughly what it costs. No deck.

Book the call

Or email hello@devjunction.co