2.0 KiB
Mobile build variants
EAS profiles set APP_VARIANT to select the app identity in app.config.ts.
Both iOS bundle identifiers and Android package names use these values:
| Profile | App name | Identifier |
|---|---|---|
| development | oTunes (Development) | com.abunchofknowitalls.otunes.development |
| preview | oTunes (Preview) | com.abunchofknowitalls.otunes.preview |
| production | oTunes | com.abunchofknowitalls.otunes |
Build with eas build --profile development, --profile preview, or
--profile production from this directory.
For local builds and Metro, select the same variant explicitly:
APP_VARIANT=development pnpm ios
APP_VARIANT=development pnpm android
APP_VARIANT=development pnpm start
An unset APP_VARIANT keeps the production identity. Unknown variants fail
configuration. URL schemes are otunes-development, otunes-preview, and
otunes respectively, allowing the apps to be installed together.
Shared links and artwork
Shared URLs stay as ordinary HTTPS links. The web page's "Open App" action
opens otunes://open?url=<encoded HTTPS URL>, including the server address and
album, artist, or playlist destination. No domain association files, signing
settings, or per-server mobile builds are needed.
The app checks the link's server against its configured server before opening media. Links for another server do not switch the current server. On a fresh installation, the server address is prefilled in setup. The destination is kept in memory through setup and sign-in, and is opened after authentication. The browser may ask before opening the app. If the app is absent, the web page remains available. Native changes still require a new mobile build.
Native sharing supplies media titles and artwork through iOS link metadata and Android's chooser thumbnail, while sharing the original HTTPS URL. Receiving apps control whether they display previews. If artwork cannot load, the URL is still shared. Existing builds without the native sharing module fall back to URL-only sharing.