Change the App Name
Changing the visible app name is only one part of white-labeling. Start by deciding whether you need a display-name change or a new application identity: those are different changes with different release consequences.
Quick Answer
Update the iOS display name and Android app_name, rebuild the app, and verify
the label on device. If you also change the bundle identifier or Android
application id, create matching Firebase app entries and download new config
files.
Before You Start
Have a working local build before changing native settings, and keep a note of the current bundle identifier and Android application id. You will need a simulator, emulator, or device to verify the new label after rebuilding.
| Goal | Change | What stays the same |
|---|---|---|
| Show a new name below the app icon | iOS display name and Android app_name | Store app identity, signing, and existing integrations |
| Ship a separately identified white-label app | Bundle identifier and applicationId | Nothing automatically: reconfigure every service that uses the old identity |
If the app is already published, treat an identifier change as a release and migration decision rather than a cosmetic rename.
1. Change the iOS Display Name
Open the iOS workspace in Xcode:
open ios/*.xcworkspace
Then:
- select the app project;
- select the app target;
- open General or Info depending on Xcode version;
- update the display name value;
- confirm the bundle identifier if you are white-labeling for release.
You can also search native files if the display name is configured in plist or build settings:
rg "CFBundleDisplayName|PRODUCT_NAME|INFOPLIST_KEY_CFBundleDisplayName" ios
2. Change the Android Display Name
Open:
android/app/src/main/res/values/strings.xml
Update:
<string name="app_name">Your App Name</string>
Search for additional flavor-specific values if the app has build variants:
rg "app_name" android/app/src/main/res android/app/src
3. Review App Identifiers
The display name and the application identity are different settings. You can change the name users see without changing the identifier used by stores, signing, push notifications, deep links, and backend credentials.
For Android, changing applicationId creates a different app identity in
Google Play. For Apple platforms, a bundle ID associated with an uploaded build
cannot be changed for that app record. If an app has already shipped, keep the
existing identifiers unless you intentionally plan a new store listing and a
separate migration. See the official Android application ID guidance
and Apple's bundle identifier guidance.
For a new, unpublished app or a deliberate white-label build, update identifiers intentionally:
| Platform | Identifier |
|---|---|
| iOS | Bundle identifier, for example com.company.app. |
| Android | applicationId, for example com.company.app. |
If identifiers change, update:
- Firebase iOS app and
GoogleService-Info.plist; - Firebase Android app and
google-services.json; - Apple Developer App ID and provisioning profile;
- APNs credentials;
- Google Play app entry;
- third-party OAuth providers;
- Stripe/Apple Pay merchant settings if used.
- URL schemes and universal/app links;
- App Groups, Associated Domains, Keychain groups, and other entitlements;
- notification service, share, widget, watch, and other extension identifiers;
- CI, environment, analytics, crash-reporting, and credential mappings that use the old identifier.
4. Rebuild and Verify
corepack yarn ios
corepack yarn android
If the old app name remains on the home screen, delete the installed app and run again.
For a display-name-only change, check the home screen before changing any identifier or service configuration. This keeps the smallest change easy to verify and makes a later identity migration deliberate.
Verification Checklist
- iOS home screen shows the new app name.
- Android launcher shows the new app name.
- Bundle identifier/application id are correct for the target environment.
- Published store identities were left unchanged unless a new app record is the explicit release plan.
- Firebase config files match the identifiers.
- Extensions, URL schemes, App Groups, Associated Domains, and entitlements use the intended identifiers.
- Push, social login, and payments still work after identifier changes.
- Store listing name matches the release plan.
Troubleshooting
| Problem | Fix |
|---|---|
| Old name still appears | Delete the installed app and rebuild. |
| Firebase stops working after rename | Download new Firebase config files for the new identifiers. |
| Social login fails | Update provider app settings with the new bundle/package values. |
| Push stops working | Recreate or update APNs/FCM credentials for the new app id. |