A mobile app for iOS and Android
One codebase, both stores — instead of paying twice for the same product. Built on React Native and Expo.
I answer within one working day, in writing. I never call.
When people come for this
- Clients live on their phones and the site alone no longer covers it.
- The work happens away from a desk: a warehouse, a site, a road — and the data has to be entered where it happens.
- Notifications are the point. Mail is ignored, a push is not.
- An app exists but was built twice, for each platform, and every change now costs double.
What is inside
One codebase, two platforms
React Native and Expo: iOS and Android from the same source, so a change is written once and lands on both.
Store submission
Builds, certificates, descriptions and screenshots. Review rejections are handled by me, not sent to you as a screenshot.
Push notifications
Set up so they arrive and are read — not so they annoy people into switching them off in the first week.
Offline behaviour
The app decides what to do when the connection dies mid-action, instead of losing what the person just typed.
Its back end
The app talks to something: accounts, payments, your existing systems. That side gets built too, not assumed.
Updates without the store
Small fixes reach people over the air instead of waiting days for another review.
How the work goes
You describe the task
A short form: what the business does, what should change. No calls — I answer in writing, within one working day.
You get a quote
Within two working days, one figure for the whole scope, before any work starts. Not a range that doubles later.
You see the first screen
The opening screen as a layout, before anything is built. Wrong direction is cheap to fix here and expensive to fix later.
It gets built
Phone first, then desktop. Checked on a slow connection and on a real device, not only in a browser window.
It goes live
You get every access on day one: domain, hosting, analytics, the code. Nothing is held hostage.
What it costs
A mobile app is priced by what it does and what it connects to. One figure for the whole scope within two working days, before anything starts — store accounts and their yearly fees are paid by you directly, they are not marked up through me.
- How many screens, and whether there are accounts and payments.
- What it connects to: your systems, maps, cameras, scanners.
- Whether it must work offline.
- Whether both stores are needed or one is enough for now.
There is no public mobile case yet
Nothing invented goes on this page, so here is the honest state of it: the mobile work I have done is not public, and I will show a build on request instead of pointing at a store link that does not exist. What does stand behind the skill is Cuttle — a desktop product built from scratch, with licensing, payments and signed releases. If a public case matters to you more than a demonstration, say so and I will tell you straight whether I am the right choice.
This block will change the day there is something public to show. Until then it stays as it is.
See what is publicQuestions people ask
Why one codebase and not native?
Because for most business apps the difference is invisible to the user and very visible in the bill. If your case genuinely needs native, I say so instead of selling what I have.
Do I need my own developer accounts?
Yes, and that is in your favour: the app belongs to your company, not to me. Apple and Google charge you directly.
How long until it is in the store?
The build comes first, then review — Apple usually answers within days. The term goes into the quote before the work.
What if the store rejects it?
I deal with the rejection: rewrite what they flagged and resubmit. That is part of the job, not extra work.
Do you call?
No. I answer in writing, within one working day, in the channel you left.
Get a price for your app
Describe what it has to do — the figure comes within two working days, before any work begins.
Get a price