Flows, wireframes and interfaces designed by someone who also writes the code — so everything you approve can actually be built, on time.
From the Still case study
A good fit for
- Founders who need a prototype before raising or building
- Existing apps that feel dated or confusing
- Teams with developers but no product designer
Tools I use
Figma · FigJam · Prototyping · Design tokens · Accessibility (WCAG)
Discovery
Who it’s for, what they need to do and what success looks like, written down and agreed.
User flows & wireframes
The structure of the app mapped out before visual design begins.
Visual design
A considered interface with your brand — typography, color, motion and detail.
Clickable prototype
A Figma prototype you can put in front of users and investors.
Design system
Reusable components and tokens, so the app stays consistent as it grows.
Developer-ready handoff
Or, more often, I simply build it myself.
Have an app idea? Get a free, fixed-scope estimate.
- Reply within one business day
- No obligation
- You own the code
- 01Week 1
Understand
We talk through the idea, who it’s for and what success looks like.
- 02Weeks 2–3
Shape
Flows, wireframes and a clickable prototype, while decisions are still cheap.
- 03Weeks 4–10
Build
Design and engineering in short cycles, with a fresh test build most weeks.
- 04Ongoing
Launch & stay
Store release, monitoring and steady improvements once real users arrive.
Yes. Design-only projects end with a Figma file, a prototype and a component library your developers can build from.
Usually 2–4 weeks for a first version’s flows and key screens, depending on the size of the app.
Yes — starting with a short review of what’s working, what isn’t, and where users get stuck.
Yes. I design with both platforms’ conventions in mind, adapting where they genuinely differ.