
Banking · 2025
A mobile banking app, rebuilt from scratch
A bank with 30 branches
148,000monthly active users 12 months after launch
- Kotlin
- Swift
- Java, Spring Boot
- PostgreSQL
We draw screens after testing them with users and hand them over as components developers can take as they are.

Our design team has 9 people. Every project starts with interviews with 5 to 8 users: a bank’s clients, a warehouse’s operators, a clinic’s patients. We test the prototype with the same people, then build the design system in Figma: colours, type, components and their states.
Interviews, a review of the current system, a look at competitors, the key scenarios.
A clickable prototype, tests with 5 to 8 users, notes and fixes.
For phone, tablet and desktop, with empty and error states.
Tokens, components, rules; the same names as the developers’ code components.
Contrast, keyboard use and checks with screen readers.
1–2 weeks
We talk to users and your team and write down the scenarios.
1–2 weeks
Wireframes of the key screens and a clickable prototype.
1 week
Users try the prototype; we fix what they trip over.
2–6 weeks
All screens, all states and the design system.
Prices without VAT (18%), at the rates in force since 1 January 2026.

Banking · 2025
A bank with 30 branches
148,000monthly active users 12 months after launch

Healthcare · 2026
A private network of 8 clinics
17% → 9%missed appointments, March to August 2026

Retail · 2024
A supermarket chain with 84 stores
410,000app users in the first 12 months
Yes. At handover we hold two sessions with your developers and answer their questions through the first two sprints.
Colours, type and the logo come from the brand book. What it lacks for screens, such as error and success colours, we add after checking contrast.
Write one sentence or pick the screens, integrations and deadline: the team, the weeks and a price range appear at once.