Build · Service
App Design
We design the flows, screens and component system for iOS, Android and web apps, and test them as a clickable prototype before a line of production code is written.
No bookings yet
IllustrationThe states most apps forget to design. We design them before anyone builds them.
Who is App Design for?
For teams about to build an app, or fixing one users struggle with.
What do you get?
- User flows and wireframes for every key task
- High-fidelity screens, including empty, loading and error states
- A component library and design tokens your developers can map to code
- A clickable prototype for stakeholder and user testing
How do you know it's done?
- Every screen has its edge states designed, not improvised in code
- Developers can build from the file without a meeting per screen
- Key flows are tested in the prototype before build starts
How does an engagement run?
- 01
Brief. A few minutes with our intake. Your context arrives before the call does.
- 02
Intro call. Thirty minutes. We ask the hard questions and tell you honestly whether we're the right fit.
- 03
Written scope. Scope, exclusions, milestones and a fixed price per phase, in writing, before any invoice.
- 04
Architecture. Diagrams and decision records you review and approve before the build starts.
- 05
Build. Working software on staging, demoed on a fixed cadence. You see progress, not status reports.
- 06
Handover. Code, infrastructure, docs and runbooks in your accounts. Ongoing support only if you want it.
How is it priced?
By scope. After the call you get a written scope with exclusions, milestones and a fixed price per phase. Payment follows accepted milestones. The budget range you pick in the brief isn't a quote; it helps us suggest a first phase that fits.
Which technologies do you use?
Our usual stack for App Design. We work with yours when you have one.
- Figma
- Design tokens
- React
- Next.js
App Design: questions and answers
Do you design for iOS, Android and the web?
Yes. We design the flows, screens and component system for iOS, Android and web apps.
What do our developers receive?
High-fidelity screens including empty, loading and error states, a component library with design tokens they can map to code, and a clickable prototype, so they can build without a meeting per screen.
Do you test the design before development starts?
Yes. Key flows are tested as a clickable prototype with stakeholders and users before production code is written.
Start a brief for App Design.
A few questions, about three minutes. Nothing is sent until you review it and press Send, and the first call is thirty minutes to check fit, both ways.