Overview

You already know the rhythm from the Quick start: edit .env through setup.html, then make run-* or make build-*. This page covers what actually happens under the hood, and the order to configure things in.

What the sync step patches

Every make run-* and make build-* target first runs:

bash scripts/env-sync.sh

That script reads .env and patches:

1. env.g.dart — the typed Dart bindings the app reads at runtime.
2. Android application android:label and iOS CFBundleDisplayName — from APP_NAME.
3. AdMob APP IDs into AndroidManifest.xml and Info.plist — only when AdMob is enabled.
4. pubspec.yaml's version: line — from APP_VERSION_NAME + APP_VERSION_CODE. Flutter propagates that to both stores.
5. Play Games APP_ID meta-data in AndroidManifest.xml.
6. android/key.properties — from your signing values.

When you're done working, make reset restores every touched file to its committed placeholder state. Your .env, Firebase files, and keystore stay put — they're never touched.

What to configure, in order

1. Identifiers — the Android package name and iOS bundle ID. You cannot change these once you've submitted to a store.
2. Firebase — run flutterfire configure after step 1.
3. App icon and general settings — APP_NAME, APP_VERSION_NAME, APP_VERSION_CODE, and swap in your icon.
4. Signing key — required before your first release build.
5. Features (optional) — AdMob or AppLovin, IAP, Play Games, logging. Leave each *_IS_ENABLED at false until you're ready — the corresponding subsystem stays completely inert.