---
name: mobile-platform-standard
description: Sets the eligibility gate and platform baseline for native iOS and Android work. Use when touching Expo, EAS, React Native, app.config, bundle identifiers, TestFlight, Google Play, push, deep links or store submission. Not for emulators; use mobile-device-lab.
---

# Mobile platform standard

Read before writing mobile code or touching any Apple, Google, Expo, EAS or Firebase surface.

```powershell
$mobile = "$env:LOCALAPPDATA\AgentHub\capabilities\mobile-development\mobile.ps1"
pwsh -NoProfile -File $mobile scope <productId> -Json
pwsh -NoProfile -File $mobile catalog -Json
```

## 1. Eligibility gate

`registry/mobile-scope.json` is the sole authority for which products may receive mobile work. Resolve the product there first.

| Bucket | Action |
| --- | --- |
| `include` | Proceed with the baseline. |
| `noNative` | Stop. No native surface intended. |
| `evaluateLater` | Stop. Reserve no identifier. |
| `excludedPendingReposition` | Stop. Identity is frozen. |
| absent | Stop and ask the owner to classify it. |

Only an exact `include` record authorizes product-targeted mobile work. A repository, app config, existing build, domain or remembered decision is not evidence.

For a frozen product, every class in `scopePolicy.frozenIdentifierClasses` is prohibited (Expo/EAS projects, bundle identifiers, store apps, Firebase apps, APNs/FCM credentials, deep-link associations, store metadata, branding, native code). A placeholder identifier is a prohibited identifier. Only the owner lifts a freeze, through the product's `exitCondition`. Bundle identifiers are permanent after the first App Store Connect upload, and a changed `applicationId` is a different Android app.

## 2. Baseline

| Layer | Standard |
| --- | --- |
| Framework | Expo SDK 57, React Native 0.86, TypeScript, Expo Router |
| Native | Continuous Native Generation, config plugins, `expo-dev-client` (not Expo Go) |
| Builds | Local; EAS cloud only when the macOS guest is unavailable |
| Release | EAS Submit, Update, Workflows, Metadata (`store.config.json`), Environment Variables, Credentials |
| Quality | Maestro E2E, Sentry per product, EAS Observe, `expo-doctor` and `expo install --check` in CI |
| Push, links | `expo-notifications` (APNs, FCM v1); Universal Links, Android App Links |
| Versioning | EAS remote versions, `autoIncrement`, `runtimeVersion: { "policy": "fingerprint" }` |

Unchanged native state ships as EAS Update; changed native state builds and submits. Track npm `latest` of `expo`, never prereleases, and pin the EAS CLI version. Target Android 16 / API 36. The macOS guest is x86_64, so Xcode stops at 26.x (`registry/mobile-development.json` `expectations.xcode`).

## 3. Local builds

| Target | Command | Where |
| --- | --- | --- |
| Android APK | `gradlew` (see mobile-device-lab `references/lab-operations.md`) | Windows |
| iOS Simulator `.app` | `xcodebuild`, `ios.simulator: true` | macOS guest |
| Signed iOS `.ipa` | `eas build --platform ios --profile <p> --local` | macOS guest |

`--local` contacts Expo only for the project check and credentials. Zero identities from `security find-identity -v -p codesigning` is normal afterwards (throwaway keychain); check for the signed artifact.

Install an `.ipa` on a phone from Windows with `pymobiledevice3 apps install` over USB; readiness is `usbmux list` answering. `usbmuxd` comes from the Apple Devices app (`AppleDevices` MSIX: no service, needs one launch) or from Apple Mobile Device Support (runs `Apple Mobile Device Service`); don't judge one form by the other's checks.

## 4. Identity

- One bundle identifier and one EAS `development` profile per product until it ships; every suffix is another Apple App ID and profile. Add variants only for a real store or side-by-side need, and record the reason in the authority.
- `registry/mobile-scope.json` is the sole product identity authority. Use the product's `mobileIdentity` exactly; never derive, normalize or improve it from this skill, another product, an old build or a dashboard.
- One EAS project per eligible product unless the authority records an exception. Treat EAS IDs and slugs, Apple team and certificate state, App IDs, profiles, devices and account topology as live facts: resolve them at execution time and do not persist a second table in a skill.
- Identity, signing, registration, submission, credential changes and profile cleanup are owner-gated. If authority and provider disagree, stop and report.

## 5. Health-sensitive products

Where `healthSensitive` is true, enable no screenshot collection, session replay or broad AI/MCP access against real patient data; review the model provider's retention policy first and use synthetic fixtures.

## References

- `references/store-compliance.md`. Read when preparing a store submission.
- `references/release-infrastructure.md`. Read when setting up Apple or Google accounts, API keys, beta lanes or EAS variables, or installing an `.ipa`.