Branding and assets

Replace starter branding before producing store builds. Expo resolves mobile image paths relative to apps/mobile.

Identity values

Edit the marked values near the top of apps/mobile/app.config.js:

const APP_NAME = 'Northstar';
const BUNDLE_ID = 'com.example.northstar';
const SCHEMA = 'northstar';

The config derives development and preview names, bundle suffixes, and URL schemes from these values. EXPO_PUBLIC_APP_ENV selects development, preview, or production behavior. Also review apps/mobile/app.json for values that are not derived by app.config.js, including:

Expo owner, slug, version, and EAS project ID
universal-link hosts and iOS associated domains
Android adaptive icon background
iOS team and permission descriptions
update URL and runtime-version policy

Mobile image assets

The current Expo configuration reads assets from apps/mobile/assets/images:

Purpose	Configured file
App icon	`icon.png`
Android adaptive foreground	`adaptiveIconForeground-1770559191548.jpeg`
Web favicon	`favicon.png`
Light splash	`splash-light.png`
Dark splash	`splash-icon-dark.png`

Replace the files or update every matching path in apps/mobile/app.json. Keep source artwork such as amisi.svg only when the application still uses it.

Validate branding changes

Native icons, splash configuration, bundle IDs, schemes, associated domains, and plugin settings require a new native build. They cannot be delivered only through an over-the-air update. Before release:

Confirm icon and splash crops on iOS and Android.
Test development, preview, and production schemes.
Verify universal links and associated domains.
Run bun run doctor.
Run bun run verify.

Working with the starter

Caveats

Identity values

Mobile image assets

Validate branding changes

​Identity values

​Mobile image assets

​Validate branding changes

Identity values

Mobile image assets

Validate branding changes