Pretty pictures nobody can build from
A developer opens the file and finds no empty state, no error state, and different spacing on every screen. The rest gets filled in by guesswork — and the product drifts from the design.
UI/UX design for applications — from research to a build-ready interface
User flows, wireframes, a design system and a clickable prototype. Designs that ship to development without expensive rework in code. We also design without building afterwards — if your own team writes the code, you get the full set of files and the rights to the design.
Why teams come to us
Users never reach the goal
Traffic is there, sign-ups are not, and nobody has walked the onboarding, the form and the payment screen as a real scenario. You cannot see which step loses people — so you fix blind.
Every new screen drawn from scratch
A year in, the product carries three shades of one button and four versions of one table. Shipping a feature takes longer — the look is renegotiated every time.
What the service covers
Research and scenarios
User tasks and the paths people take to finish them
Information architecture
Screen structure, navigation and the split by role
Wireframes
Skeletons of the key screens, no colour or imagery
Interface (UI)
Screens on a grid, contrast checked against WCAG
Design system
Colours, typography, a spacing scale, components with states
Clickable prototype
Main flows wired together, on phone and desktop
What you get
- Wireframes of the key screens, including the empty and error states
- UI screens for phone and desktop, with states
- A design system: colours, typography, the spacing scale and the component library
- The source file and the rights to the design, on your side
How we work
Call and scope
1–2 daysWe agree on the product goal, who uses it, the technical constraints and the budget. We also write down which devices the product has to run on and what it has to match: an existing brand, a component library you already use, or the app store requirements. The output is a list of screens to design, a deadline and a price.
Research and scenarios
2–4 daysWe review the current product, competing solutions and analytics data. We record user tasks and the points where people stop today.
Architecture and wireframes
3–5 daysWe lay out the structure, navigation and screen skeletons. At the sketch stage we already settle what the user sees with no data and after an error, so those screens are not drawn in a hurry later. Feedback is collected on sketches, before the visual layer exists — that is when a change costs least.
UI and design system
5–10 daysWe design the screens and build the component library alongside them. We check contrast, tap target size and readability on small screens. Screens come to you in batches every few days, so you see the direction as it forms instead of saving up feedback for the end of the stage.
Prototype and testing
2–3 daysWe wire the screens into a clickable prototype and walk the scenarios through it. Feedback is collected in one place, as comments next to the screens, and ticked off once it is applied. Fixes land in the design files, not in shipped code.
Handoff to the team
1–2 daysWe tidy the file, document components and the spec, and hand over access. We walk the developers through the file in one session: where the components live, how to read the variables and where the exports come from. We stay available for questions while the build runs.
What the development team receives
This is where work with a designer usually breaks down. Below is exactly what reaches the developers, whether we build the product or your own team does.
A Figma file with a structure
One page per flow, named layers, screens in scenario order. Drafts kept apart from approved work.
Components with their states
Every element carries its variants: default, hover, active, disabled, loading and error. Variant names match the props used in code.
A design system, not a pile of screens
Colours, typography and spacing stored as variables, named after their job. A change in the library reaches every screen.
A spec for spacing, typography and breakpoints
A spacing scale, named text styles with roles, a grid for phone, tablet and desktop. Developers read values instead of measuring pixels on a screenshot.
The clickable prototype as the reference
Transitions, the order of steps and what happens after an error are visible in the prototype. We hand it over as a link that opens in a browser and on a phone.
Asset exports and naming
Icons as SVG and images in web, iOS and Android formats, named the same way as in the design. Developers never export anything by hand.
Edge paths and accessibility
Empty list, no connection, declined payment, expired session — each case has a screen and the wording of its message. Contrast and tap targets checked against WCAG.
Tools
- Figma
- Auto Layout
- Variables and tokens
- Figma prototyping
- FigJam
- WCAG 2.2
- Apple HIG
- Material Design 3
- React
- TypeScript
Projects where you can see it
Frequently asked questions
How much does a UI/UX design project for an app cost?
After a scoping call — we name the price before work starts. It moves with screen and role count, the platforms, and whether a design system exists. Research and user testing are quoted separately.
How long does the design take?
2–4 weeks from scope approval: a few days for research and architecture, one to two weeks for UI and the design system. Inside an MVP it fits within the 3–5 weeks once scope is agreed.
Do you design without building it afterwards?
Yes. The source file, the design system and the rights are yours — hand them to your own team or another contractor. We stay available for questions during the build.
What does the development team receive?
A structured Figma file, a component library with all states, colour and typography variables, a spec for spacing and breakpoints, asset exports and a clickable prototype. Plus edge paths: empty list, network error, expired session.
Do you audit an existing app?
Yes. We walk the main scenarios and collect problems in navigation, forms, contrast, states and error messages. The list is ordered by impact on conversion, and the top items arrive as build-ready designs.
Contact
Tell us what you are building and where you are — a new product, or an interface that needs order put back into it. We will reply within one business day with scope, timeline and price. We have been on the market for four years, and the products we have shipped have more than 50,000 users between them.