Android Readiness
Purpose
Verify the Android app is ready to build and submit: application id, signing, permissions/manifest, target/compile SDK, 16KB page-size support, and Play policy fit.
When to Use
- Before an Android Play build/submission.
- When adding a permission/capability or bumping SDK targets.
- Not for iOS specifics (
ios-readiness).
Inputs
- Android config (applicationId, manifest, Gradle, signing).
- Permissions/capabilities used; native libraries present.
Discovery Questions
- Is the applicationId correct and stable?
- Is signing (keystore/Play App Signing) configured?
- Do manifest permissions match used features (and none extra)?
- Are target/compile SDK current, and is 16KB page-size support in place for native libs?
Responsibilities
- Verify applicationId and signing (keystore / Play App Signing).
- Verify manifest permissions match used features (no over-permissioning).
- Verify target/compile SDK meet Play requirements.
- Verify 16KB memory page-size support for native
.so libraries.
- Check Play policy/data-safety fit; flag gaps without changing signing.
Required Workflow
- Read Android config + permissions + native libs.
- Cross-check permissions vs used features.
- Verify SDK targets + 16KB alignment for native libs.
- Check Play policy/data-safety.
- Record readiness findings + gaps.
Decision Rules
- Manifest permissions must match used features — remove over-permissions (Play rejects/flags them).
- Target SDK must meet current Play minimums.
- Native libraries must support 16KB page sizes for modern devices/Play requirements.
- applicationId and signing are not changed without approval (
../../../system/OPERATING_RULES.md).
Rules
- Do not change signing/applicationId without explicit approval.
- No keystore/secrets committed (
../../security-review).
- Verify against current Play requirements (SDK, 16KB, data safety).
Anti-Patterns
- Over-permissioned manifest.
- Outdated target SDK.
- Native libs not 16KB-aligned.
- Changing signing/applicationId silently.
Validation Checklist
Definition of Done
A recorded Android readiness report: verified applicationId/signing, correct permissions, current SDK targets, 16KB support for native libraries, and Play policy fit — with gaps flagged and no unapproved signing changes.
Related Skills
mobile-builds, mobile-release, mobile-native-modules, mobile-notifications, mobile-background-tasks, mobile-location-maps, ../../security-review
Related Knowledge
../../../knowledge/ (Android config, Play account).
Related References
../../../references/mobile/native/ when populated.
Context Loading Guidance
- Requires: Android config, used permissions/capabilities, native libraries.
- Does not require: app screen logic, the full mobile skill set, unrelated references.
- May load:
mobile-builds, mobile-release, mobile-native-modules.
- Stop when: Android readiness findings are recorded.
Token Efficiency Guidance
Read Android/Gradle/manifest config + native libs; don't read app logic. Summarize gaps.
1---2name: android-readiness3description: Use to validate Android release readiness — application id, signing (keystore/Play signing), permissions and manifest, target/compile SDK, 16KB page-size support, and Play policy fit. Read-and-verify; flags gaps before submission.4---56# Android Readiness78## Purpose910Verify the Android app is ready to build and submit: application id, signing, permissions/manifest, target/compile SDK, 16KB page-size support, and Play policy fit.1112## When to Use1314- Before an Android Play build/submission.15- When adding a permission/capability or bumping SDK targets.16- Not for iOS specifics (`ios-readiness`).1718## Inputs1920- Android config (applicationId, manifest, Gradle, signing).21- Permissions/capabilities used; native libraries present.2223## Discovery Questions2425- Is the applicationId correct and stable?26- Is signing (keystore/Play App Signing) configured?27- Do manifest permissions match used features (and none extra)?28- Are target/compile SDK current, and is 16KB page-size support in place for native libs?2930## Responsibilities3132- Verify **applicationId** and **signing** (keystore / Play App Signing).33- Verify **manifest permissions** match used features (no over-permissioning).34- Verify **target/compile SDK** meet Play requirements.35- Verify **16KB memory page-size** support for native `.so` libraries.36- Check **Play policy/data-safety** fit; flag gaps without changing signing.3738## Required Workflow39401. Read Android config + permissions + native libs.412. Cross-check permissions vs used features.423. Verify SDK targets + 16KB alignment for native libs.434. Check Play policy/data-safety.445. Record readiness findings + gaps.4546## Decision Rules4748- Manifest permissions must match used features — remove over-permissions (Play rejects/flags them).49- Target SDK must meet current Play minimums.50- Native libraries must support 16KB page sizes for modern devices/Play requirements.51- applicationId and signing are not changed without approval (`../../../system/OPERATING_RULES.md`).5253## Rules5455- Do not change signing/applicationId without explicit approval.56- No keystore/secrets committed (`../../security-review`).57- Verify against current Play requirements (SDK, 16KB, data safety).5859## Anti-Patterns6061- Over-permissioned manifest.62- Outdated target SDK.63- Native libs not 16KB-aligned.64- Changing signing/applicationId silently.6566## Validation Checklist6768- [ ] applicationId + signing verified.69- [ ] Manifest permissions match features (no extras).70- [ ] Target/compile SDK current.71- [ ] 16KB page-size support verified for native libs.72- [ ] Play policy/data-safety reviewed.7374## Definition of Done7576A recorded Android readiness report: verified applicationId/signing, correct permissions, current SDK targets, 16KB support for native libraries, and Play policy fit — with gaps flagged and no unapproved signing changes.7778## Related Skills7980`mobile-builds`, `mobile-release`, `mobile-native-modules`, `mobile-notifications`, `mobile-background-tasks`, `mobile-location-maps`, `../../security-review`8182## Related Knowledge8384`../../../knowledge/` (Android config, Play account).8586## Related References8788`../../../references/mobile/native/` when populated.8990## Context Loading Guidance9192- **Requires:** Android config, used permissions/capabilities, native libraries.93- **Does not require:** app screen logic, the full mobile skill set, unrelated references.94- **May load:** `mobile-builds`, `mobile-release`, `mobile-native-modules`.95- **Stop when:** Android readiness findings are recorded.9697## Token Efficiency Guidance9899Read Android/Gradle/manifest config + native libs; don't read app logic. Summarize gaps.
ahtishamshahzad