ServicesApp development
Apps built end to end
Most app projects stall in the gap between the design and the build. A studio hands over a file, a developer reads it differently, and the thing that ships is not the thing that was drawn. I do both halves, so there is no gap to fall into.
The flows before the screens
Every app is a set of decisions someone has to make, in an order that makes sense to them rather than to the database. I map that first: what a person is trying to get done, what they need in front of them to do it, and what happens when they get it wrong. Wireframes come out of that, and a wireframe is cheap to argue with. Screens drawn before the flows are settled are expensive to argue with.
A component system, not a pile of screens
Buttons, fields, tables, empty states, error states, the loading moment nobody designs until it is already live. Built once, named, and reused, so the app stays coherent as it grows and the twentieth screen costs a fraction of the first.
Then it gets built
The development is mine too. You do not leave with a folder and a problem, you leave with something running. It also keeps the design honest about what can actually be built, because the person promising it is the person who has to deliver it.
Made to be handed on anyway
Even though I build it, everything is documented and organised as if someone else will pick it up, because one day someone might. A system nobody else can read is not a deliverable.
What you get
- User flows and wireframes
- Screen design, every state
- A named component system
- The build, through to something running
- Documentation your next developer can read
Who it is for
- Founders with a product in their head and no team yet
- Companies whose internal tool is a spreadsheet held together by one person
- Anyone quoted once for design and then again for the build
About this service
- Do I need the idea fully worked out?
- No. Most people arrive with a problem and a rough shape. Working out what it actually needs to be is the first part of the job, not a prerequisite for starting it.
- What does an app cost?
- Apps start at $2,000, and move from there with what the app has to do. Websites start lower, at $750. Either way you get a written proposal with a real number before any work begins.
- Can you work with my existing developers?
- Yes. If you already have a team, the deliverable becomes the design and the component system, documented for them to build from.