Mobile Apps
New

On the home screen,
not just the browser.

Most businesses do not need an app. The ones that do know it: a loyalty programme nobody uses because it lives on a card, a field team typing into a phone browser, customers who book weekly and want it one tap away. When it is genuinely the right tool, a single build can serve both stores.

Book a discovery call See the work
What you get

The part that
actually matters.

  • One build, both stores

    A single codebase shipping to iOS and Android, instead of paying twice to build the same thing.

  • Push that gets read

    Notifications land on the home screen with a fraction of the noise of email — used sparingly, they work.

  • Works offline

    Field teams and patchy signal are the same problem. The app keeps working and syncs when it reconnects.

  • Shares your backend

    Built on the same data as your site and CRM, so the app is another window on one system, not a second one to maintain.

Deliverables

In the box.

  • Scoping session on whether an app is genuinely the right call
  • Clickable prototype before the build starts
  • iOS and Android build from one codebase
  • Push notification setup
  • App Store and Play Store submission, including the review process
  • Store listing copy and screenshots
  • Over-the-air updates so fixes do not need a review cycle

Best suited to

Businesses with repeat users, a field team, or something genuinely better on a home screen. If a fast mobile website would do the same job, I will tell you — and build that instead.

Built with
React NativeExpoTypeScriptEAS BuildPush NotificationsApp StorePlay Store
Process

How working together goes.

No mystery, no month-long silences. Five steps, and you can stop after any of them.

  1. Discovery call

    20 minutes, free

    We work out what you are actually trying to fix, what you have already tried, and whether I am the right person for it. If I am not, I will say so and point you somewhere better.

    You get: A clear read on whether this is worth doing

  2. Scope and proposal

    Within 3 days

    You get a written scope: what is included, what is explicitly not, the timeline, and a fixed price. No hourly surprises, and nothing starts until you have agreed to it.

    You get: A fixed-price proposal you can say no to

  3. Build in the open

    The bulk of the project

    A staging link is shared from the first week and updated as work lands. You see progress as it happens instead of waiting a month to find out we understood each other differently.

    You get: A live staging URL and weekly check-ins

  4. Review and launch

    Final week

    You go through it properly against the original scope, we fix what needs fixing, and then it goes live — with analytics connected from the first day, not bolted on later.

    You get: Live, measured, and handed over with training

  5. Support and iterate

    30 days, then optional

    Thirty days of support is included for anything broken or confusing. After that you either run it yourself with the training, or keep me on for ongoing work. No lock-in either way.

    You get: A system you own and can actually run

Questions

Straight
answers.

Do I actually need an app?

Often not, and I would rather say so in the first call than build something that gets installed once. The test is whether people will come back weekly, or need it to work offline. If neither is true, a good mobile site wins.

How long does store approval take?

Apple is typically one to three days, Google usually faster. Rejections mostly come from missing privacy details or unclear account deletion — I handle that paperwork as part of the build.

Who owns the developer accounts?

You do, in your company name. I will set them up with you, but the app belongs on your account — not mine.