01 / iOS · SwiftUI · StripeRebuilt a four-step checkout as a single screen with saved payment and address. Shipped to 50k users without a single rollback.
● Available · next slot [MONTH YEAR] · Amsterdam / remote
One senior engineer, from a rough brief to the App Store or production. No agency layer, no hand-offs, no surprises on the invoice.



Selected work · 4 case studies
01 / iOS · SwiftUI · StripeRebuilt a four-step checkout as a single screen with saved payment and address. Shipped to 50k users without a single rollback.
02 / Web · React · PostgreSQLA week-view scheduler for a 40-person field team, with conflict detection and a nightly export their accountant actually uses.
03 / iOS · Offline sync · NodeOffline-first checklists with photo capture and background sync. Works in basements and on rooftops; merges cleanly when it comes back online.
04 / Migration · Swift · CIMoved a legacy Objective-C codebase to Swift screen by screen, behind feature flags, while the app kept shipping every two weeks.
What I do · 3 ways in
Native Swift and SwiftUI, from first prototype to App Store release. You get the release, the source and the docs.
02TypeScript, React and Node, deployed on infrastructure you own and can take over any time. You get a production deploy on infrastructure you own.
03A fractional lead engineer for reviews, audits or a senior pair of hands. You get reviews, audits and a senior engineer on your team, no lock-in.
How a project runs · changelog
Scope is written down before code is written. You see a working build at every milestone, and the handover means your next engineer never has to call me.
We talk through the problem, the users and the deadline. If I am not the right person, I say so and point you to someone who is.
A short plan with milestones, what is out of scope, and a price. You sign off before any code exists.
Install it, click around, send notes. Each milestone ships with a short changelog of what moved and what is next.
Store submission or production deploy, crash and uptime monitoring, documentation, and a video walkthrough so the codebase outlives the engagement.
Contact · replies within one business day
Send a few lines about what you are building and when it needs to exist. You will get a couple of questions back and a suggested time to talk.
Write to me