Skip to main content

Getting Started

Thank you for purchasing the React Native Fitness App template. This product ships in two separate variants:

  • a React Native CLI-first version in cli-version/ReactNativeFitnessApp
  • an Expo version in expo-version/ReactNativeFitnessApp

Choose one workflow and start from that folder only. Do not try to combine both variants into the same app setup.

Follow these steps in order:

  1. Choose the workflow you want to use
  2. Build and run that version on iOS and Android
  3. White-label the app name, bundle identifiers, icons, splash screen, and theme
  4. Replace starter content and placeholder profile data
  5. Connect your own backend or third-party services if needed
  6. Run the release checklist before store submission

Step 1. Choose Your Workflow​

React Native CLI version​

Choose the CLI version if you want:

  • full native iOS and Android projects in your repo
  • standard React Native CLI workflows
  • direct native editing in Xcode and Android Studio
  • Expo limited to helper native modules only

Start here:

Expo version​

Choose the Expo version if you want:

  • Expo development tooling
  • Expo run commands and prebuild workflow
  • Continuous Native Generation
  • EAS Build profiles for development, preview, and production

Start here:

Step 2. Build and Run the App​

After you choose a version, follow the matching setup guide:

If you picked the CLI version, these shared docs also apply:

Step 3. Understand What Ships by Default​

The fitness boilerplate intentionally ships with:

  • neutral app naming and starter content
  • no live Firebase, Facebook, Maps, analytics, or push notification credentials
  • buyer-owned service configuration left intentionally blank
  • separate CLI and Expo variants so you can choose the workflow that fits your team

This makes it safer to white-label and publish under your own account.

Step 4. Customize the Product​

Before launch, replace at least the following:

  • app name and display name
  • Android package name
  • iOS bundle identifier
  • Expo slug if you use the Expo version
  • icons and splash screen
  • theme colors
  • onboarding copy
  • profile and community starter data

Step 5. Add Your Own Services​

The template is ready to be extended, but service integrations are intentionally left to the buyer.

Common additions include:

  • Firebase
  • push notifications
  • analytics
  • maps
  • custom backend APIs

When you add those, also add the corresponding keys, config files, permissions, privacy disclosures, and store metadata required by your own app.

Step 6. Use the Launch Checklist​

Before publishing, complete the full checklist here: