BowlerKitBowlerKit

Rename Package & App Name

10/11/2026

Safely change Flutter package/application identifiers, display name, Firebase config, and deep-link scheme.

The template's current native identifiers are com.soewidiputra.flonlate.mobile and the Dart package name is mobile.

Changing a package/bundle identifier creates a new store identity and invalidates links to existing Firebase, Google/Apple, RevenueCat, AdMob, and signing configuration. Plan the migration before changing a published app.

Automated native rename

From mobile-app/:

dart run change_app_package_name:main com.example.yourapp

Review the result rather than assuming every platform file/plugin was updated. Verify Android namespace/applicationId, Kotlin package paths, iOS bundle identifier, tests, and generated references.

Update display names separately:

  • Android android/app/src/main/AndroidManifest.xml android:label.
  • iOS ios/Runner/Info.plist CFBundleDisplayName/CFBundleName.

Dart package name (optional)

Changing name: mobile in pubspec.yaml is a source-wide rename. Replace every package:mobile/ import, then run:

flutter clean
flutter pub get
dart run build_runner build --delete-conflicting-outputs

Do not edit generated .g.dart/.freezed.dart files by hand; regenerate them after the rename.

The Account deep-link contract is:

flonlate://link?destination=reset-password&token=...&email=...

To change it:

  1. Update Endpoints.deepLinkScheme in lib/constants/api_endpoints.dart.
  2. Update Android <data android:scheme="..." android:host="link" /> in AndroidManifest.xml.
  3. Update iOS CFBundleURLSchemes in ios/Runner/Info.plist.
  4. Update backend-generated verification/reset links.
  5. Test malformed/unknown destinations and the /link host contract.

Do not change the host to reset-password; link is the allowlisted entry point.

External services checklist

  1. Register the new Android/iOS identifiers in Firebase and rerun flutterfire configure.
  2. Update Google Sign-In client IDs and Apple Sign in with Apple capabilities/keys.
  3. Update RevenueCat app/store configuration and public build-time keys.
  4. Update AdMob app/ad-unit IDs.
  5. Reissue EAS/store signing credentials where required.
  6. Update privacy policy, store metadata, backend URLs, and notification config.

Verify

flutter analyze
flutter test
flutter build appbundle --release

Install the artifact on a physical device and test login, FCM, purchases, deep links, and account deletion before submission.