Store Setup
Apple App Store and Google Play need no extra store configuration — your framework setup guide covers them. This section is for additional store targets: Meta Quest (Horizon OS), the Amazon Appstore (Fire OS and Vega OS), and the Onside iOS alternative marketplace. Finish your framework setup first, then add the store target your release artifact needs. The purchase APIs stay identical on every store; only build-time and runtime store selection differ. Each store guide lists the exact values you need, where to get them, and where each framework reads them.
Store Targets#
| Target | How it is selected | Setup guide |
|---|---|---|
| Horizon OS | Build the Android Gradle horizon product flavor for Meta Quest devices. | Horizon OS Setup |
| Amazon Fire OS | Android amazon flavor for Amazon Appstore builds. | Amazon Store Setup — Fire OS |
| Amazon Vega OS | Vega devices run apps on Amazon's Kepler JavaScript runtime instead of Android; react-native-iap and expo-iap switch to their Kepler adapter at runtime. | Amazon Store Setup — Vega OS |
| Onside | iOS alternative marketplace; expo-iap selects the Onside runtime automatically (Expo only). | Onside Setup |
Framework Model#
Every store guide shows two setup paths, so know which one your project uses. Expo projects declare store values in the Expo config, and a config plugin writes the native files during expo prebuild. Bare React Native, Flutter, KMP, MAUI, Godot, and native Android projects edit their native build files directly.
- Fire OS and Vega OS are separate release artifacts even though both use Amazon receipt verification — do not reuse one build for the other.
- Onside is currently
expo-iaponly; other frameworks have no Onside build option.