React Native App Setup Guides
Use this page to choose the right app guide after downloading an Instamobile React Native app package. Each app guide focuses on the product-specific setup, then links to the shared docs for environment setup, Firebase, customization, troubleshooting, and store release.
Quick Answer
Start with your app guide, run the app locally, connect the required backend services, then complete the shared release checklist before publishing. App folders only need extra pages when the app has product-specific backend data, roles, algorithms, media workflows, payments, OpenAI setup, or other behavior that is not already covered by the shared docs.
Start Here For Every App
These docs apply to most React Native app packages:
- Set Up Your React Native Environment
- Run on iOS
- Run on Android
- Configure a Firebase Project
- Link Firebase to Your Mobile App
- Firebase Production Checklist
- React Native App Release Checklist
- React Native Troubleshooting
App Guides
| App package | Start here | App-specific docs |
|---|---|---|
| Social Network App | Getting Started | Firebase data and feeds |
| Instagram App | Getting Started | Firebase media setup |
| TikTok App | Getting Started | Manage songs, Composer, Hashtags |
| Uber Eats Clone | Getting Started | Firebase tables, Admin and restaurant owner app, Driver app, Order tracking |
| Taxi App | Getting Started | Taxi Firebase tables |
| Appointments App | Getting Started | Appointments Firebase tables |
| ChatGPT React Native App | Getting Started | Firebase and OpenAI setup, Customization, Troubleshooting |
| Fitness App | Getting Started | CLI version, Expo version |
| Real Estate App | Getting Started | Real estate Firebase data |
| Dating App | Getting Started | Recommendation algorithm |
| WooCommerce Store | Convert a WooCommerce Store | Use the shared release checklist and WooCommerce-specific setup steps in the main guide. |
When An App Has Extra Pages
An app gets extra docs only when the setup differs from the shared guides. Good examples are:
- app-specific Firestore collections, seed data, rules, or indexes;
- role-based flows such as customer, driver, restaurant owner, vendor, or admin;
- media workflows such as video upload, thumbnail generation, songs, or hashtags;
- payment provider setup, webhooks, or order dispatch;
- AI backend setup, OpenAI keys, Firebase Functions, or model configuration;
- matching, recommendations, feeds, chat, reporting, or other app-specific logic.
If the topic is generic, use the shared docs instead of adding another app page.
Common Next Steps
- Customize the App Name
- Change the App Icon
- Change the Splash Screen
- Translations and RTL
- Firebase Costs and Blaze Plan
- Publishing to the App Stores
FAQ
Why do some app folders have more pages than others?
Some apps need product-specific backend data, roles, media flows, or algorithms. Simple apps can stay on one setup guide and link to the shared documentation.
Should I follow an app-specific release checklist or the shared one?
Use the shared React Native App Release Checklist for the full release process. App-specific release pages, when linked from an older route, should be treated as extra smoke tests for that product.
Where should Firebase setup live?
Generic Firebase setup lives in Firebase Integration. Only app-specific collections, seed data, rules, indexes, and backend flows belong in an app folder.