Product
Before the first screen exists, it is clear who uses it, at what point in their day, and what should be faster than it is now.
Web and mobile apps
An app is not a screen with buttons. It is a job someone has to get done faster.
I build tools that simplify a specific process: quoting, requests, customer service, team work. I start from that process, not from picking a stack.
- Web apps
- Mobile apps
- MVPs
- Internal panels and tools
More than code
The most expensive app is the one nobody uses.
Technology is the last of three problems to solve. The first two decide whether it is worth writing at all.
UX
The hard part of an app is not the feature, it is the path to it. I design flows, not a collection of separate views.
Technology
Architecture built for integrations and scale, so version two does not mean writing everything again.
What I build
Four things I do genuinely well.
Instead of a list of twenty items — the ones I put my name to.
Web apps
Tools that run in the browser, with no install and no app store.
Mobile apps
iOS and Android where camera, location or offline access actually matter.
MVPs
The shortest route to a version you can put in front of users and test the assumptions.
Internal panels and tools
Calculators, dashboards and panels that take manual work off the team.
From idea to product
Six stages, with the decisions made before the code.
The later an assumption changes, the more it costs. That is why most of the work sits at the start.
- 01DiscoveryThe problem, the users, and what should genuinely change after launch.
- 02Features and flowsA prioritised feature list and the paths users take through them.
- 03UXScreen structure and a prototype that shows whether the route to the goal is short.
- 04UIThe visual layer, states, messages and everything that happens between screens.
- 05Development and testingImplementation, integrations and checks on real devices.
- 06Release and growthShipping, watching how it is used, and the features that follow from it.
MARS — a complex product broken down into its parts
The app for Alvernia Planet has two independent modes, its own user paths and mission stages. A fourteen-page functionality document was produced for the build — mode by mode, screen by screen. You can page through it on the project page: it shows how I structure a product of that scale before it exists.
Selected work
Apps that solved a specific problem.
Selected launches from this category.
Describe the process that should run faster.
You do not need a finished spec. The problem is enough — we'll map out the rest together.