Do we get the Figma files?

Always, with the components and tokens, in your Figma workspace from day one.

Do you test with real users?

Yes, on the prototype, before code. Five sessions, recorded, with a short report of what to change. You can watch.

We only need UI, not research. Is that fine?

Fine. Bring the flows and we start at final UI. We will say so if the flows have a hole in them.

Service 01 · UX research · UI · Design systems

Design that the same team then builds.

Flows, prototypes and final screens from the people who will write the code. Nothing is lost in a handoff, because there is no handoff.

Book a design sprint What's included ↓

Designed in-house2026

01AlarmyxiOS · product designLive 02DocseeiOS · product designLive

03Your product—○ Next

01 — What's included

From the first interview to the last pixel.

Take the whole sprint, or only the step you are missing.

01Discovery and researchInterviews, support tickets, analytics and a competitor review. We leave with one problem worth solving, written down.5 days

02Flows and wireframesEvery screen and every state in low fidelity, fast to change and cheap to be wrong about.Figma

03Clickable prototypeTested with real users before a line of code. Five people and a prototype find most of what a launch would.Figma · tests

04Final UI and design systemTokens, components, light and dark, both platforms. The tenth screen as consistent as the first.Tokens · Components

05Store assetsIcon, screenshots, preview video and listing copy, so the store page sells what the app does.App Store · Google Play

06Design in the buildThe designer sits in the sprint. When the product changes, the design changes with it, not after it.Weekly

02 — Why design and code in one team

A prototype is a promise. We keep it because we build it.

Agencies hand over a Figma file and a wish. Then a different team discovers which screens cannot be built in the time, and the design quietly degrades.

Here the designer and the engineers are one team. What is drawn is what ships, and what cannot ship is found on the whiteboard, not in week eight.

Both of our own apps were designed this way. The App Store screenshots are the real screens.

Research

What users do, not what they say: interviews, tickets, analytics

Craft

Type, spacing and motion: the details that make a product feel finished

Systems

Tokens and components so new screens cost hours, not days

Testing

Five users on a prototype, before a line of code

03 — How it runs

What you get, week by week.

Week 1

Discover

You get: a problem statement, user profiles and a screen list.

Weeks 2–3

Flows and prototype

You get: a clickable prototype and the results of testing it.

Weeks 4–6

Final UI

You get: every screen, the design system and store assets.

Build

Design in the sprint

You get: a designer on the team until launch, and after if you want.

04 — Pricing

Design sprint

3 weeks: research, flows, tested prototype. You own the Figma file whatever you decide next.

Design in the build

A designer on your team for the whole build and after launch.

05 — Questions

About design projects.

Yes. Give us the brand book or the logo and three colours, and the design system grows from there. If there is no brand yet, the sprint produces enough of one to ship.

Book a design sprint

Show us the problem. We draw the first screen on the call.

Thirty minutes with whoever owns the product. You leave with a sketch and a plan for the sprint.

Book a design sprint Mobile app development →