01
Product engineering
Full web applications, front to back — an interface people can actually use, an API that holds up, and a data model that will not need rewriting in a year.
Independent software engineer
Twelve months of prototypes is not a product. I take an idea from the first sketch to something live on the web, on the App Store, and running in production — the architecture, the code, the interface, and the deployment pipeline that keeps it standing.
01 — What I do
Most software fails in the gaps: between design and code, between backend and mobile, between "it works on my machine" and a real deployment. I work across all of it.
01
Full web applications, front to back — an interface people can actually use, an API that holds up, and a data model that will not need rewriting in a year.
02
One Flutter codebase, both stores. Built, signed, submitted and shipped — including the certificates, review paperwork and release process nobody warns you about.
03
Summaries, risk scoring, trend analysis and assistants wired into a real product — with guardrails, citation checks and evaluation, so the model cannot invent things your users will believe.
04
Static analysis, architecture diagrams and CI gates for codebases nobody remembers writing. I publish open source in this space, and I build it for teams too.
05
Design tokens, a component library and a consistent visual language — so the tenth screen takes an afternoon instead of a fortnight, and looks like the first nine.
06
Containers, pipelines, environments and monitoring. Plus the unglamorous part: being there when the deploy goes sideways at an inconvenient hour.
02 — Selected work
03 — Toolkit
04 — How I work
We talk for half an hour about what you are trying to change. You get back a short written scope — what gets built, what does not, what it costs, and when. Free, and yours to keep whether or not we work together.
The first milestone is always something you can open and click, not a document. It settles the arguments a specification cannot.
A staging environment from week one, updated as work lands. You see progress continuously instead of a reveal at the end, which is when bad news gets expensive.
Production deployment, monitoring, and documentation written for whoever comes next — including you. No lock-in: the code, the accounts and the pipeline are yours.
Next step
Tell me what you are trying to make. If I am not the right person for it, I will say so and point you somewhere better.