# Google Play

**Google Play is essentially unaddressed.** There are no Play, Data Safety, or
Play Console docs anywhere in the repo — every launch document is Apple/TestFlight
only. There is no `android/` prebuild and no Android submit profile in `eas.json`.
Android is a from-scratch enablement, not a final polish.

```mermaid
graph TB
    A["Add android.package to app.json"] --> B["First Android prebuild"]
    B --> C["Android EAS build (AAB)"]
    C --> D["Play Console: create app"]
    D --> E["Data Safety form"]
    D --> F["Content rating (IARC)"]
    D --> G["Privacy policy URL"]
    E --> H["Internal testing track"]
    F --> H
    G --> H
```

## Blockers

| Item | Status | Notes |
|---|---|---|
| `android.package` (applicationId) | **Open — blocker** | Missing from `app.json`; a Play build is impossible without it |
| AAB build profile + Play submit config | Open | `eas.json` has iOS submit only; no `serviceAccountKeyPath` or track |
| Data Safety form | Open | Must declare photos (biometric), health/measurements, email, name, purchases, crash — **and PostHog analytics + session replay**; none drafted |
| Permissions declaration | Open | `WRITE_EXTERNAL_STORAGE` is deprecated/ignored on Android 13+ and is a flagged permission — likely remove or declare |
| Privacy policy URL | Done (shared with iOS) | Same hosted policy |
| Target API level | Likely OK via Expo defaults | Expo SDK 54 / RN 0.81 targets a current API level, but this has never been built or verified for Android |
| Content rating (IARC questionnaire) | Open (manual) | Not started |
| Signed AAB / Play App Signing | Open | No Android keystore or build has been produced |

## Android remaining, in order

1. **Add `android.package`** to `app.json` (for example `com.kcb1099.drape` to
   match iOS), then run a first Android prebuild.
2. **Add an Android EAS build + Play submit config** and produce a signed AAB via
   Play App Signing.
3. **Remove or replace `WRITE_EXTERNAL_STORAGE`** so it does not trigger a Play
   permissions declaration.
4. **Complete the Data Safety form**, including the PostHog analytics and session
   replay data.
5. **Complete the content-rating questionnaire** and enter the privacy + support
   URLs.
6. **Produce a full Android screenshot set** and ship to an internal testing track
   first.

:::note[Reuse from iOS]
The privacy policy, terms, account deletion, consent flow, and most store copy are
already built and shared with iOS. Android is missing the platform plumbing and the
Play-specific console work — not the product itself.
:::