NativePilot guides React Native and Expo apps through subscription setup, validates provider configuration, detects mismatches, and shows the next action in one workspace.
Provider-side actions still happen in RevenueCat, Apple, Google, and Expo. NativePilot keeps the path clear and the evidence together.
Launch workspaceOrbit Mobile
2 need review
RepositoryApp identifiers matched✓
RevenueCatOffering graph connected✓
App Store Connect3 products synced✓
Google PlayPackage mismatch detectedReview
Next actionConfirm the Android package in your Play app.
Built for
React Native
Expo
RevenueCat
Apple
Google Play
What NativePilot solves
The hard part is everything between the dashboards.
A subscription launch can depend on repository config, EAS environments, provider permissions, product IDs, entitlements, offerings, and two store consoles. A one-character mismatch can be easy to create and hard to find.
NativePilot brings the instructions, source evidence, connection status, and validation results into one guided view—so you know which dashboard to open and what to do there next.
How it works
One visible path from project to launch readiness.
Direct provider links, concise instructions, official documentation, and live status stay attached to each step.
01
Connect project
Start with the app and repository you are preparing to ship.
02
Connect providers
Add supported read-only connections and project metadata.
03
Follow guided setup
Open the right provider page with the identifiers and instructions you need.
04
Validate configuration
Compare saved workspace values with repository and provider evidence.
05
Fix mismatches
Use specific recovery actions and official provider documentation.
06
Review readiness
See what is ready, what still needs attention, and what requires a manual check.
Guided setup
NativePilot guides you while you integrate.
Validation is not saved for the end. NativePilot turns incomplete provider setup into a sequence of specific actions, with the relevant identifier and provider destination beside the instruction.
Direct buttons to the relevant provider pages
Copyable package names, bundle IDs, and other supported identifiers
Official documentation attached to the step it explains
Setup status and recovery actions after a failed check
Google Play setupGrant app access
Needs attention
Service accountnativepilot-reader@project.iam.gserviceaccount.comCopy
Android packagecom.example.orbitCopy
Open Users and permissions in Play Console.
Invite the service account and grant app-scoped read access.
Return here and verify the saved connection.
Open Play Console ↗Official docs ↗
Integration status
What's available today
These integrations inspect and compare supported configuration. They do not promise full provider setup automation.
Google Play
Available
Read-only Android subscription catalog connection with guided setup and precise recovery states.
Service-account onboarding with guided Cloud, JSON key, and Play permission setup
Package, credential, and authentication verification
Subscription, base-plan, and offer sync — including valid empty catalogs
API-disabled and access-denied recovery with saved encrypted-credential retry
Match/mismatch and readiness visibility using GET-only provider operations
NativePilot does not write to or manage Google Play settings.
RevenueCat
Available
OAuth-first, read-only connection for projects, apps, products, entitlements, offerings, and packages, with workspace and provider comparisons.
App Store Connect
Available · Phase 1
Read-only API-key connection, exact app selection, and sync for bundle IDs, subscription groups, products, states, and localization records.
GitHub
Available
GitHub App repository scanning for Expo configuration, app identifiers, dependency signals, and referenced environment-variable names.
Expo / EAS
Available
Read-only checks for EAS project metadata, build profiles, environment names, and required RevenueCat public-key variables.
Public workspace access
Coming soon
The interactive workspace is being built and tested privately. No public login, signup, or project access is exposed from this page.
Match / mismatch
Compare what your code, workspace, and providers say should exist.
NativePilot normalizes supported evidence into plain-language comparisons. A match confirms the sources agree. A mismatch names the affected value and points to the next place to check.
App identityBundle identifier and Android package nameMatch
CatalogSubscription product IDs and provider productsReview
Access modelEntitlements, offerings, and package mappingsMatch
Runtime configPublic SDK key formats and environment-variable namesMatch
Readiness and output
Know what is verified—and what still needs a human.
Readiness is evidence-based. Manual checks remain visible instead of being presented as automated success.
✓
Launch readiness
Deterministic findings and a launch checklist separate ready items, blockers, warnings, and manual verification.
</>
Generated artifacts
Generate copyable implementation snippets and setup artifacts where supported. NativePilot does not install code into your app.
→
Clear recovery
Errors retain the last safe provider snapshot where supported and route you to a relevant retry or configuration step.
Security by scope
Inspect what matters. Ask for less.
NativePilot uses read-only provider connections where applicable and a least-privilege approach. Google Play catalog access is GET-only, and NativePilot does not write or edit Google provider settings.
Stored provider credentials are encrypted. Sensitive credentials are not included in generated artifacts or returned to the browser after connection.
Next up
NativePilot Workspace — coming soon
The interactive workspace is already being built and tested. It will let developers connect projects and providers directly, follow guided setup, and review validation results in one place.
The workspace is currently in private testing. Public access is coming soon.
React Native
Expo
Apple
