Mobile Apps

Package name, Bundle ID & App ID

What are package names, bundle IDs and app IDs?

Every mobile app needs a unique identifier that distinguishes it from all other apps on the platform. These identifiers are platform-specific:

  • Android package name - a reverse-domain-style string like 
    com.yourcompany.appname
    that uniquely identifies your app on Google Play and Android devices.
  • iOS bundle ID - a similar reverse-domain string (e.g. 
    com.yourcompany.appname
    ) that identifies your app in the App Store and across Apple's ecosystem.
  • App ID - in Apple's developer portal, the bundle ID is registered as an "App ID" that controls entitlements, certificates and provisioning profiles.

Emergent automatically seeds these identifiers into 

app.json
at environment setup, in the format 
com.emergent.<words>.<suffix>
. The first-build form is pre-populated with these values and is editable before you trigger your first build. You will need to register the package name in your own Play Console.

Seeded at environment setup

The package name and bundle ID are seeded into 

app.json
when your environment is set up, in the format 
com.emergent.<words>.<suffix>
. The pre-populated first-build form lets you review and edit them before your first build is triggered.

Package name & bundle ID after first build

Once Emergent has published your first build, the app name locks after first build. Your display name remains changeable at any time. To change the Android package name, ask the agent - but if the app is already listed on the Play Store, you'll continue as a new listing. To change the iOS bundle ID, contact support.

Plan your identifier before first publish

Choose your app's name and branding carefully before triggering the first build. Changing the package name or bundle ID later requires creating an entirely new app listing in the stores - your existing installs, reviews and rankings will not transfer.

Align integrations with the same identifier

Any third-party integration you configure - Apple Music APIs, Firebase services, OAuth providers, push notification certificates - must be registered using the exact same bundle ID or package name that Emergent generated.

If you register an Apple Music integration under 

com.example.myapp
but your iOS bundle ID is 
com.example.myapp2
, the integration will fail at runtime. Always verify that external dashboards (Apple Developer, Google Cloud Console, etc.) use the identifier Emergent assigned.

Tip

You can find your app's package name and bundle ID by asking the agent itself.

Native mobile apps do not require a domain

Unlike web apps, native iOS and Android applications do not need a custom domain to function. The app stores distribute your APK or IPA directly to users' devices; there is no URL to visit.

No domain purchase required

You can build, publish and distribute a mobile app on Emergent without buying or configuring a domain. If you later decide to add a companion website or convert your app to web, you can attach a custom domain at that time.

Universal links (iOS) and App Links (Android) can use a domain to deep-link into your app, but the app itself runs independently of any web address.

Was this page helpful?

Related pages