Audit intermediate Works with: Any AI

Mobile Release Readiness Code Audit

Checklist Has example

Check release configuration before store submission.

The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.

[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.

Audit a mobile app release. Paste the build configuration summary, permission list, privacy declarations, third-party SDKs and crash report summary: [RELEASE_DATA]. Store listing claims: [STORE_CLAIMS]. Minimum supported versions: [VERSIONS].

Check that permissions match features, privacy declarations match SDK behaviour, debug code and keys are removed, crash-free rates are acceptable, upgrade paths are tested and store text is accurate. Identify risks of rejection or user harm.

Return a checklist with Item, Status (red, amber, green) and Action, and a staged rollout plan with stop conditions. Store rules change, so confirm them [VERIFY].

Also add a list of items to verify on a clean device, including installation, first launch, permission prompts and upgrade from the previous version, and a plan for monitoring crash rates and reviews in the first week after release.

Also list the items for the store listing, such as screenshots, descriptions and privacy details, that must match the build, and the person who signs off. Finish with the one release blocker I should resolve first.

Fill in before use

Optional: type your details and the prompt above updates. Nothing is saved or sent.

Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.

Checklist (invented release 3.4)
Permissions: location (background) requested; the feature uses foreground only. Red; remove.
Privacy declaration lists no analytics SDK, but one is included. Red.
Debug menu reachable via hidden gesture. Amber.
Crash-free users: 99.1% on the beta; one crash on Android 9 in the camera screen. Amber.
Upgrade from 3.3 tested on 2 devices; not on a device with low storage. Amber.
Store text says "works offline"; offline mode only covers lists. Red (accuracy).
Staged rollout: 5% for 24 hours, 20%, then 50%. Stop if crash-free users drop below 98.5%. Store rules [VERIFY].

• audit