PutThrough Product engineering studio
Book a build call

Mobile apps

An iOS and Android app, submitted in about a week.

One codebase for both platforms, built and submitted to the App Store and Google Play within the week, then taken through review. Store review then takes as long as Apple and Google take.

Prefer to write? Send your requirements

In short

PutThrough builds iOS and Android apps from one React Native codebase and submits them to the App Store and Google Play in about a week, at a fixed price agreed in writing after a free scoping call. Store review then takes as long as Apple and Google take; we answer the reviewers’ questions until the app is approved, and you own the code and both developer accounts.

01Who it’s for

For an app people will install and keep.

  • Products that need a phone in the loop

    Your web product works, but customers want notifications, the camera or quick access from their home screen.

  • Businesses taking orders or bookings

    An app your regular customers use to order, book or reorder, with payments and notifications.

  • Teams working away from a desk

    Field staff who need forms, photos, checklists and job details on their phones, synced back to the office.

02Example uses

What a one-week mobile app usually is.

  1. Companion apps for your web product

    The parts of your product people use on the go, sharing accounts and data with the web app.

  2. Ordering and booking apps

    Browse, book or order, pay, and get notified, with an admin view for your team.

  3. Field-team tools

    Job lists, forms, photos and sign-offs for staff out on site, synced when they’re back in signal.

03What fits in a week

Both platforms, one core workflow.

Fits in a week

  • iOS and Android from one codebase
  • Accounts and sign-in
  • Push notifications
  • Payments or subscriptions
  • Camera and photo uploads
  • Submission to both stores

Needs longer, or a call first

  • Heavy offline sync or conflict resolution
  • Hardware integrations such as Bluetooth devices
  • Games or heavy graphics
  • Guaranteed store approval dates — review is Apple’s and Google’s

04A sample week

Seven days, one mobile app.

The same seven days as every build, with this product’s work in them. Your week is planned on the scoping call.

  1. Day 0

    Scoping call and fixed quote

    The core workflow, what the app needs from the phone, and the store developer accounts you’ll need.

  2. Day 1

    Screens and data

    The screens, the navigation and the data behind them, agreed in writing. Store listings started.

  3. Days 2–5

    Build, in the open

    The app on both platforms, with a test build on your phone from the first days and an update every evening.

  4. Day 6

    Harden

    Tested on real iOS and Android devices, privacy details and data-safety answers completed, crash reporting switched on.

  5. Day 7

    Submit and hand over

    Submitted to both stores, then the handover. We take it through review, including any questions the reviewers raise.

05What you get

What you walk away with.

  • The app, submitted to the App Store and Google Play
  • Store listings and privacy details, in your developer accounts
  • Crash reporting and push notifications set up
  • The backend it runs on, live in your accounts
  • Help through store review until it is approved

Plus the standard handover every build ends with: source code, a written handover, a recorded walkthrough and every account in your name. The full Day 7 list

06Stack

One codebase, both stores.

Two native codebases cost roughly twice as much to maintain for as long as the app exists. We go native only when the product is the platform experience.

App
React Native and Expo
Builds
EAS Build and submission
Backend
Postgres, usually through Supabase
Accounts
Apple and Google developer accounts in your name

07Pricing

A fixed price for a fixed scope.

Your exact price is fixed in writing after the scoping call, before you commit to anything.

After launch, the care plan is from $499 per month.

08Questions

Questions about mobile apps.

Something we haven’t covered?

Ask on a call
01 How long does store review take?

It varies and it isn’t ours to control. Most reviews finish in days, but some take longer or come back with questions. We handle those until the app is approved.

02 Do I need developer accounts?

Yes, in your name: Apple’s developer program and a Google Play console account. Apple’s can take a few days to approve, so we ask you to start it before Day 1.

03 Can it share accounts with our web app?

Yes, when the web app’s backend allows it. If we built the web app, it is designed for this from the start.

04 What happens when Apple or Google change their requirements?

They do, every year. The care plan keeps the app current with each year’s requirements, or the handover shows you what to update yourself.

What do you need?

What it should do, who will use it, the must-haves, and any links. A few sentences is plenty.

Budget, if you have one in mind
When would you like to start?