Files
otunes/apps/mobile
T
..
2026-11-03 14:30:38 -05:00
2026-08-02 04:14:02 +00:00

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 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.

Adaptive iOS sidebar

Expo Router owns navigation through NativeTabs sidebarAdaptable. Expanded iOS windows prefer sidebar placement, including the unfolded iPhone Duo. Compact windows use the phone player accessory and player layout. Layout selection uses the current window dimensions rather than the device's iPad identifier. Horizontal safe areas protect content from the sidebar and either rail edge, and player spacing updates as the window folds or resizes. native/TabletSidebar.swift adds UIKit Library and Playlists groups and the pinned account footer, which the current Expo Router API does not expose. The bridge reuses the router's tab instances so each destination retains its navigation stack. On Duo, hiding the sidebar restores the native tab rail.

The react-native-screens patch resolves groups to their selected leaf controller for tab selection and routes compact group buttons directly to that screen. It also notifies the sidebar bridge after each native tab reconciliation, so startup updates cannot replace the Library and Playlists sections with a flat tab list. Keep these behaviors when updating the dependency. After changing native modules or dependency patches, run pod install in ios and rebuild the development app.