Fitness App Launch Checklist

Use this checklist before you submit the app to TestFlight, App Store Connect, Google Play, or an EAS production build.

Also review the general React Native App Release Checklist for shared signing, Firebase, privacy, store listing, and QA requirements.

1. Confirm Which Version You Are Shipping

Before release, make sure your team is shipping only one product variant:

• cli-version/ReactNativeFitnessApp
• expo-version/ReactNativeFitnessApp

Do not mix release steps across both workflows.

2. Branding

Confirm that you replaced:

• app name and display name
• Android package name
• iOS bundle identifier
• Expo slug if you ship the Expo version
• app icons
• splash screen assets
• theme colors

3. Starter Content

Replace or review:

• onboarding copy
• profile placeholders
• community posts and comments
• notifications copy
• any stock images you do not want in production

4. Native Capabilities

If you add extra features such as camera, location, push notifications, analytics, or maps, also update:

• Android permissions
• iOS privacy usage descriptions
• store privacy disclosures
• Expo config fields or plugins if you ship the Expo version

5. Third-Party Services

If you integrate external services, verify that you added your own:

• API keys
• config files
• signing credentials
• backend endpoints
• store metadata and privacy disclosures

Do not ship demo credentials or vendor-owned project identifiers.

6. QA Commands For The CLI Version

If you are shipping cli-version/ReactNativeFitnessApp, run:

corepack yarn install --immutable
yarn lint
yarn test
cd ios && pod install && cd ..
corepack yarn ios
cd android && ./gradlew app:assembleGooglePlayDebug && cd ..

7. QA Commands For The Expo Version

If you are shipping expo-version/ReactNativeFitnessApp, run:

corepack yarn install --immutable
yarn doctor
yarn lint
yarn test --watchAll=false --watchman=false
corepack yarn ios
corepack yarn android
npx expo export --platform ios --output-dir /tmp/react-native-fitness-app-export

If your release process depends on EAS, also validate the matching build profile before store submission.

8. Manual Smoke Test

At minimum, test:

• onboarding flow
• authentication flow
• drawer or tab navigation
• create-post modal
• comment modal
• image picker and document picker
• nutrition flow
• workout flow
• any custom backend integrations you added

9. Store Submission Readiness

Before release, confirm:

• the shipped brand is yours everywhere user-facing
• privacy copy matches enabled features
• signing is configured with your own credentials
• screenshots and listing copy match the actual app
• no demo content or vendor credentials remain