From working build to submitted app

Your app is built. I'll get it released.

For teams with an Expo, React Native, iOS, Android or macOS app that's stuck on builds, credentials, signing, store setup, privacy forms, TestFlight, Play testing or submission.

Start the release fit check See scope and pricing

No mail app? Copy the fit-check questions.

Copy the questions below and send your answers to this address from any email:

hello@mikeoladapo.com

Fit-check questions

App or repository URL:
Framework and version:
iOS, Android, macOS, or more than one:
Current build status:
The exact release blocker:
Developer accounts active: yes / no
Store assets and privacy policy ready: yes / no
Target submission date:
Available budget:
Anything else I should know:

Copying this text does not send anything.

Who this is for

The app already exists

There's code, a build or an app you can test. I'm not designing and building the whole thing from an idea.

The problem is with releasing it

A failing build, app IDs, signing, permissions, settings, privacy requirements, store listing details, or replying to a review rejection.

I can get access safely

You give me a limited role on your accounts. I never ask for the owner's password or two-factor codes.

Start small

Three options

Release Triage

$300

Delivered within 48 hours

I reproduce the build or submission failure
List what's blocking release, in order
A written plan and a fixed scope for the next step

No implementation or store submission is included.

One-platform Release Rescue

From $1,000

Three to five business days

One iOS, Android, or macOS release target
Fix the build, signing and settings, and check the app runs
Submitted, or a release build you can reproduce

What you get at the end depends on how ready your accounts are and where the build is now.

Dual-store Release Sprint

From $1,500

Five to seven business days

iOS and Android release paths
Store listings, privacy, testing and submission checks
One round of fixes per store if review rejects it for a technical reason

Apple and Google decide when to approve. I handle the technical submission. I can't promise an approval date.

What I inspect

Build and environment

Expo and EAS configuration, Xcode or Gradle state, bundle and package identifiers, environment variables, release schemes, dependency compatibility, and reproducible build commands.

Signing and account roles

Certificates, provisioning, entitlements, app records, restricted team access, TestFlight or internal testing, and a clean record of who owns each release asset.

Store and privacy readiness

Privacy policy alignment, data declarations, permissions, screenshots and metadata, versioning, reviewer notes, and technical responses to an in-scope rejection.

Background

Apps I've shipped

I've built native iPhone and Mac apps, released React Native and Expo apps, and been through App Store Connect, TestFlight, Google Play testing, in-app purchases and privacy checks many times. Camora and Inksong are two you can look at.

See the products behind the work.

Not included

Rebuilding the whole app for the price of a release.
Unlimited review rounds, or building new features.
Logging in with shared passwords or two-factor codes passed around.
A promise that Apple, Google or anyone else will approve by a certain date.

Next step

Send me the code, where the build is, what's blocking you, which store, your date and your budget.

I'll tell you which one fits: Release Triage, a one-platform rescue or a two-store sprint.

Start the release fit check