# Native App Publish Ready

> Comprehensive app store submission readiness checker for mobile apps. Audits iOS App Store and Google Play Store requirements including build config, privacy compliance, store assets, metadata, technical requirements, and common rejection causes, including Apple review issues common in social/marketplace apps with UGC, chat, location, subscriptions, and accounts. Use when the user asks to "check if my app is ready to submit", "review for app store", "app store checklist", "pre-submission check", "ready for Play Store", "ready for App Store", "submission readiness", or wants to audit a mobile app before publishing. Supports native iOS (Swift/ObjC), native Android (Kotlin/Java), Flutter, and React Native (including Expo) projects.

- Skill: `ameistad/native-app-publish-ready` (Agent Skill, multi-file: 6 files)
- Install (CLI): `npx skillmds@latest add ameistad/native-app-publish-ready`
- Raw SKILL.md: https://api.skillmd.com/api/skills/ameistad/native-app-publish-ready/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Web & Frontend
- Author: ameistad (https://skillmd.com/u/ameistad)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/ameistad/native-app-publish-ready

---


# App Store Readiness

Audit a mobile app project for app store submission readiness. Detect the project type automatically and check against platform-specific requirements for the Apple App Store and Google Play Store.

## Workflow

1. Detect project type and target platforms
2. Run the automated scanner
3. Load relevant platform checklist(s) and review results
4. Walk through items that cannot be automated
5. Produce a final readiness report

### Step 1: Detect and Scan

Run the scanner to auto-detect framework and platforms and perform automated checks:

```bash
python3 <skill-path>/scripts/check_project.py <project-root>
```

Output: JSON with `project_type` (framework + platforms), `summary` (error/warning/pass counts), and `issues` array.

### Step 2: Load Platform Checklists

Based on detected project type, read the relevant reference files for the full checklist:

| Detected | Read |
|---|---|
| iOS target | `references/ios.md` |
| Android target | `references/android.md` |
| Flutter framework | Also `references/flutter.md` |
| React Native framework | Also `references/react-native.md` |

Each reference file contains a complete checklist organized by category. Use these to supplement the automated scan with manual review items.

For iOS apps with UGC, chat, location features, subscriptions, or user accounts, pay extra attention to the `Privacy and Permissions`, `Metadata and Compliance`, `App Review Preparation`, `Pre-Submission Testing`, and `Common Rejection Reasons` sections in `references/ios.md`.

### Step 3: Review Automated Results

Present scanner results grouped by severity:

1. **Errors** (blockers) - Must fix before submission
2. **Warnings** (risks) - Likely to cause rejection or should be addressed
3. **Passed** - Checks that look good

### Step 4: Manual Review

Walk through critical items that cannot be verified by scanning files alone:

**Store Assets and Metadata**
- Screenshots for all required device sizes
- App description, keywords, promotional text within character limits
- Privacy policy URL live and accessible
- Support URL or email functional
- Age rating questionnaire accuracy

**Testing**
- Tested on physical devices
- Tested on oldest and newest supported OS versions
- In-app purchases tested in sandbox (if applicable)
- Push notifications verified end-to-end
- Deep links and universal links working

**Legal and Compliance**
- Privacy policy hosted and URL submitted
- Data collection declarations match actual behavior
- ATT prompt before tracking (iOS)
- Account deletion offered (required by both stores)
- COPPA compliance if targeting children

**iOS App Review Hotspots**
- UGC, chat, or stranger-to-stranger interaction includes both report and block flows
- Location usage strings explain the exact data use and feature purpose; avoid vague copy
- Location permission is requested before any location access and only when the user reaches a location-based feature
- Account deletion is fully initiated in-app with confirmation, not by email or support ticket
- Subscription apps link Apple's standard EULA in the App Store description and inside the app
- Age rating matches the actual social/chat/location surface area of the app
- iPhone builds are tested on iPad compatibility mode and IPv6-only networking
- Support URL is live and reviewer-accessible

**App Review Preparation**
- Demo account credentials ready (if login required)
- Review notes for non-obvious features
- Contact information current

### Step 5: Produce Report

Summarize findings using this structure:

```
# App Store Readiness Report

**Project:** [name]
**Framework:** [detected] | **Platforms:** [ios/android]
**Date:** [date]

## Blockers (must fix before submission)
- ...

## Warnings (address before submission)
- ...

## Manual Checklist
- [ ] [items requiring human verification]

## Passed
- ...

## Recommendation
[Ready to submit / Not ready, N blockers remain]
```