Skip to content

Native

Everything operational about shipping the Tomoda native iOS and Android apps — local dev environment, release pipeline, store portal management, QA. Both binaries come from the same Expo codebase that also produces the web bundle; this section covers the workflows specific to the native side.

"Native" here means the platform-compiled apps that ship to the App Store and Google Play, as opposed to the web build covered in Frontend → Setup.

  • Release (EAS)

    The cross-platform build + submit flow via EAS. Profiles, version source, OTA updates, beta channels. Start here for the conceptual model of how a code change becomes a binary in the stores.

  • Play Store

    Google Play Console portal — Developer account, app record, App Signing (Play-managed), Maps SHA-1, store listing, content rating, Data safety, release tracks, post-launch ops.

  • App Store

    App Store Connect portal — Apple Developer Program, app record + ASC App ID, signing certificates (EAS-managed), TestFlight groups, App Privacy, App Review process, post-launch ops.

  • Local Development

    Running the native apps locally without EAS. Android Studio + emulator setup, iOS Simulator basics, expo run:android / expo run:ios, EAS dev clients, common pitfalls.

  • Testing

    QA workflows on simulators, emulators, and real devices. EAS dev clients, OAuth caveats, environment-specific keystore/SHA-1 considerations.

Where each concern lives

Task Page
"How do I run the app on my Mac?" Local Development
"How do I ship a new build?" Native Release — eas build && eas submit
"How do I push a Play Store listing change?" Play Store
"How do I set up a TestFlight beta group?" App Store
"Why are my map tiles gray?" Local Development → Google Maps (debug) or Play Store → App signing (production)
"How do I add a new tester?" Play Store § Release tracks (Android) / App Store § TestFlight (iOS)
"How do I QA on a real device?" Testing

See also