gmi.software
01 · Your app

Mobile apps

When the app is slow to change, crashes or nobody owns it.

  • Develop or take over an app
  • Loyalty apps
  • Mobile app code audit
  • App maintenance and releases

SFD: 100,000+ downloads, 4.9 App Store rating

02 · Your shop

Online shops

When the platform takes a cut of every sale or blocks what you need.

  • Online shop development
  • Shop app analytics
  • Plan and prototype before you build

120+ projects delivered

03 · Systems behind them

Integrations

When orders, stock and points are copied by hand.

  • ERP, warehouse and payments
  • AI for one manual process
  • Workshops and estimate

100+ integrations

Before a call
  • App cost estimateScope and a budget range
  • Shop platform adviserDecisions, risks and options
  • Shop cost over 5 yearsOff-the-shelf or custom, compared

After workshops: an agreed scope and a fixed price for delivering it

All services →
SFDLoyalty and shopping app100,000+ downloads · 4.9 App Store ratingMój Świat KsiążkiLoyalty programme for a bookstore chain100,000+ downloadsEMKAMedical waste tracking app5000+ downloads in first month
All 120+ projects →App ideas library
TeamAbout usWho we are and how we workCareersHow we work and open roles
Contact and stackContact[email protected]TechnologiesReact Native, MedusaJS, Node.js and the rest
Reviews5.0 on Google4.9 on ClutchClutch ↗ (opens in a new tab)
Blog
ENBook a free consultation
What we do+−

01 · Your app

Mobile apps

  • Develop or take over an app
  • Loyalty apps
  • Mobile app code audit
  • App maintenance and releases

02 · Your shop

Online shops

  • Online shop development
  • Shop app analytics
  • Plan and prototype before you build

03 · Systems behind them

Integrations

  • ERP, warehouse and payments
  • AI for one manual process
  • Workshops and estimate

Before a call

  • App cost estimateScope and a budget range
  • Shop platform adviserDecisions, risks and options
  • Shop cost over 5 yearsOff-the-shelf or custom, compared
All services →
Projects+−
  • SFD100,000+ downloads · 4.9 App Store rating
  • Mój Świat Książki100,000+ downloads
  • EMKA5000+ downloads in first month
  • All 120+ projects →
  • App ideas library
Company+−
  • About usWho we are and how we work
  • CareersHow we work and open roles
  • Contact[email protected]
  • TechnologiesReact Native, MedusaJS, Node.js and the rest
Blog→
Book a free consultation

5.0 on Google · 4.9 on Clutch

Back to blog
Services
Updated: July 11, 2026· Originally published: March 12, 2026
19 min read

How do you launch a React Native app without App Store or Google Play delays?

A practical React Native and Expo release checklist: developer accounts, EAS Build/Submit, TestFlight, Google Play closed testing, privacy, payments, reviewer access and rejection recovery.

Mikołaj Lehman, CEO & Founder, GMI Software
Mikołaj Lehman
CEO & Founder, GMI Software

In brief

Short answer: React Native store launch does not start on upload day. A safe release needs early checks for Apple/Google account ownership, EAS credentials, permissions, privacy labels, Data safety, payments, reviewer access, review backend availability and hotfix plans. Expo EAS speeds up the pipeline, but it does not replace App Review Guidelines or Google Play policy compliance.

TL;DR - Quick summary

  • Business risk: A rejection from Apple or Google can delay launch by 1-2 weeks. Tight certificate hygiene and UX polish before review matter most.
  • Faster pipelines: Expo EAS automates production binaries (.ipa, .aab) and cuts hand-rolled Xcode/Android Studio drift.
  • Ship fixes faster: OTA updates push JavaScript-layer fixes without a full store review cycle, within safe limits (no critical native changes via OTA).
  • Battle-tested: GMI Software has shipped dozens of apps; the SFD release passed both stores from one codebase, with 100,000+ downloads and a 4.9★ rating.

The problem: the app is “done”, but Apple says no

Engineering signs off, marketing is booked, you upload to App Store Connect and the status is Rejected. Common causes: vague camera permission copy or a login screen that breaks Apple rules (for example missing Sign in with Apple when social logins exist).

At GMI Software, with 16+ years and 120+ projects, we treat store submission as a technical and policy audit, not paperwork. Launch readiness sits inside DDT (Discovery, Design & Technology) and we own the outcome.

App Store vs Google Play - how reviews differ

Know the two philosophies before you freeze scope:

  • Apple App Store: Human reviewers exercise the build end-to-end. UX quality matters, not only crashes. First response often lands in 24-48 hours, but rejection loops can stretch a week.
  • Google Play: Heavy automated scanning plus privacy rules. New personal developer accounts created after November 13, 2023 must complete closed testing with at least 12 testers opted in for 14 continuous days before applying for production access.

Technical checklist: preparing React Native for release

A great roadmap fails if the reviewer hits a crash on first launch. Before we ship, we run checks such as:

See our Expo development guide for EAS builds, OTA limits and store-release patterns we use in production.

  1. Expo EAS setup: `eas build` produces .aab and .ipa from a consistent cloud environment instead of “works on my laptop” certificates.
  2. Performance (Hermes and logs): Hermes stays on, production bundles drop stray `console.log` calls to reduce noise and battery burn.
  3. Permissions copy: Info.plist and AndroidManifest.xml carry precise, user-facing reasons (for example location to show the nearest drop-off points - the same pattern we proved on EMKA Mobile).
  4. Certificates and keystores: Apple provisioning profiles and Android keystores are generated, stored and handed over securely. Losing an Android keystore blocks updates for that package name.
  5. Reviewer demo accounts: Logged-in experiences (for example Berg System-style CRM apps) need working credentials or reviewers reject within hours.
Article graphic: React Native app store launch checklist for App Store and Google Play
Article graphic: React Native app store launch checklist for App Store and Google Play

Top rejection reasons we see from Apple and Google

Reading **App Store Review Guidelines** and Play policies saves launch week:

  • Missing Sign in with Apple when Google or Facebook login exists.
  • Screenshot/device mismatches, such as iPhone notch shots uploaded to an iPad listing.
  • “Beta” or “Test” strings in production UI. Use TestFlight or Play internal tracks instead.
  • External payments for digital goods: Digital courses or subscriptions usually require in-app purchase (Apple’s 15-30% cut). External gateways such as Stripe with MedusaJS are typically fine for physical goods and real-world commerce flows.

Less launch stress with GMI Software

Leaders need predictable delivery. At GMI Software we offer a fixed-price guarantee after DDT for building and publishing React Native apps.

The SFD app shipped on both platforms from one codebase, handled heavy session load and earned a Mobile Trends Awards 2025 nomination. You keep the source, avoid vendor lock-in, and get hands-on help with developer accounts and build pipelines.

Our React Native development practice covers store submission, certificates and launch readiness end to end.

If App Store or Google Play submission is a launch risk, review builds, accounts and policies before the final sprint. Explore mobile app development

Frequently asked questions

How long does App Store and Google Play publication take?
The review response itself can be quick, but a safe project buffer is usually 1-2 weeks from release candidate. For new personal Google Play accounts, add closed testing: at least 12 testers opted in for 14 continuous days before production access can be requested.
Who creates developer accounts - GMI Software or the client?
The client should create accounts under its own legal entity. GMI can guide setup, configure roles, build pipeline and submission, but ownership of the app, ratings, certificates and distribution channel should stay with the client.
Is Expo EAS enough to publish an app?
EAS helps a lot with builds, credentials, submit and OTA, but it does not replace App Store Connect, Google Play Console, metadata, screenshots, privacy labels, Data safety, reviewer access and store policy compliance.
What are React Native OTA updates and how do they relate to store review?
OTA can ship JavaScript, copy, translation, layout and small bug fixes without a full store cycle. It is not for native code, new SDKs, permission changes, App Store capabilities or Expo SDK upgrades - those need a new build.
What if Apple or Google rejects my app?
First classify the rejection: metadata, reviewer access, privacy, payments, crash, UX or policy. Sometimes metadata or review notes are enough; sometimes a new build is needed. That is why campaigns need a decision owner, buffer and hotfix plan.
Does an ecommerce app need Apple IAP or Google Play Billing?
Usually not for physical products and services consumed outside the app. A store, marketplace or loyalty app can use external payments for those transactions. Digital content, subscriptions and in-app feature unlocks require separate Apple and Google policy analysis.

Content updated: July 11, 2026

Mikołaj Lehman, CEO & Founder, GMI Software
Mikołaj Lehman
CEO & Founder, GMI Software

Mikołaj Lehman is the CEO and founder of GMI Software. On the blog, he covers decisions around mobile apps, ecommerce and digital product delivery.

  • Mobile apps and React Native
  • Headless and B2B ecommerce
  • MedusaJS
  • Digital product delivery

Google Preferred Sources

See GMI more often in Google

Add gmi.software as a preferred source. Google may highlight our new articles more often in Top Stories and supported AI experiences.

Share article:

Related articles

Services

CPQ for manufacturing and B2B ecommerce: pitfalls, architecture and cost

A practical CPQ guide for manufacturers: where configuration rules should live, how to connect BOM, ERP, pricing, 3D and B2B storefronts, and when MedusaJS + NestJS makes sense.

→
Services

B2B marketplace split checkout: orders, payments, payouts and invoices

A practical guide for founders, CTOs and B2B marketplace operators: how to split one buying experience into vendor orders, payments, platform fees, invoices, refunds and ERP integrations.

→

Let’s discuss your project.

Tell us what you need. We’ll suggest the next step.

[email protected]
gmi.software Sp. z o.o.ul. Jana Heweliusza 11 / 819
80-890 Gdansk, Poland
Rated 5.0 out of 5 on Google5.017 client reviews on Google
TechnologiesReact NativeExpoNext.jsReactTypeScriptMedusaJS3D configuratorsNode.jsNestJSPostgreSQLDockerAWSPlaywrightMaestro
© 2026 gmi.software Sp. z o.o.
Privacy PolicyTerms