T Trackmint Docs
🔍Search docs…⌘K
🔍
Hands-on Guides ↓ Download original doc (.md)

Android Version — build today, Play Store later

The app has been cross-platform from day one (Expo/React Native) — the same code that ships to TestFlight builds for Android. What’s done, and exactly what you do after joining the Play Store.

What’s done now

The Android app identity is configured (com.apex.trackmint), and an APK build (the “preview” profile) is produced on the same EAS pipeline as the iPhone builds. An APK is a file anyone can install directly on an Android phone — no store needed: download it on the phone, tap it, allow “install from unknown sources,” done. That makes Android testing possible today, before any Play Store account exists. The signing keystore is generated and stored by EAS automatically (like your iOS certificates), so future builds are one command: eas build --platform android --profile preview.

What the Play Store needs from YOU (one-time, ~30 minutes)

  1. Create a Google Play Console account at play.google.com/console — $25 one-time fee (this is the step only you can do: it needs your Google account and a payment card).
  2. In the Console: Create app → name “Trackmint”, type App, free (billing comes later via Google Play Billing).
  3. Fill the required listing: description (use the slogans + doc 29 positioning), screenshots (the QA screenshots in the repo work), the app icon, a privacy policy URL (host doc 22’s privacy text on the website), content rating questionnaire, and data-safety form (we store account email + workspace data in Firebase — answer “data collected: email, user content; encrypted in transit; deletable on request” — doc 30’s delete workflow is your compliance answer).

What I do after you have the account (one command each)

Switch the build to an AAB (the store format): eas build --platform android --profile production, then either upload the AAB in the Console yourself (drag-and-drop under Production → Create release) or give me a Play service-account JSON (Console → Setup → API access) and submissions become automatic: eas submit --platform android — the same auto-submit flow the iPhone builds already use.

Differences to expect vs the iPhone build

None in features — same code. Two things to verify on a real Android phone (mirrors the iOS checklist): the board’s long-press drag, and the timer notification behavior. The QA suite already covers all logic on web; these two are feel-checks.