New app, start to store
From idea to a published app: design, build, backend, payments, and submission to the App Store and Google Play.
iOS and Android from one codebase with React Native and Expo — including the part most people get stuck on: certificates, builds, TestFlight, and App Store review.
Fixed price, fixed scope, and a working build early instead of a status report.
From idea to a published app: design, build, backend, payments, and submission to the App Store and Google Play.
Built something with Lovable, Bolt, Replit or an old team and it won't ship? I finish it, stabilise it and get it through review.
Replace the spreadsheet: dashboards, booking, forms with photo upload, customer portals — with a real database behind them.
Shipped, not mocked up.


No long discovery phase. You see something working in days.
You describe it, I ask the questions that decide the scope.
Scope, price and date in writing. 50% to start.
Working builds on your phone early, daily updates, changes as we go.
Store submission and review handled. Maintenance monthly if you want it.
A focused MVP is usually 1–2 weeks of build time. Store review adds a few days, and a brand-new Google Play account needs a testing period before an app can go public — I plan around both.
You do. Full source, repository access and documentation on handover.
Yours. The app is published under your Apple and Google accounts so you keep control of the listing, the reviews and the revenue.
Yes, that's a large part of what I do — half-finished AI-generated apps, abandoned React Native projects, or apps that keep getting rejected.
Apps need at least one update a year for new OS versions. Maintenance is a monthly plan: updates, small changes, monitoring.
A short description is enough for a fixed price. Replies within a day.