play-store_skill

Overview

This skill helps developers publish and optimize Android apps on Google Play. It guides listing creation, ASO keyword strategy, screenshot and asset specs, policy checks, and release planning to improve visibility and reduce rejections. Practical checklists and traps help avoid common submission problems.

How this skill works

The skill inspects store listing fields, screenshot assets, metadata, and release configuration against Google Play requirements. It recommends ASO-driven title/description choices, verifies screenshot sizes and counts, checks policy red flags, and suggests an appropriate release type and staged rollout plan. It also validates pre-launch items like target API, bundle format, privacy policy, and deobfuscation files.

When to use it

• Preparing a new app for first submission to Google Play
• Optimizing an existing listing to increase search visibility and conversions
• Validating assets and metadata before a staged or full production rollout
• Checking policy compliance to avoid rejection or removal
• Planning beta tests (internal, closed, open) and staged rollouts

Best practices

• Use a concise title (≤30 chars) with 1–2 primary keywords and brand name
• Write a hook-driven short description (≤80 chars) and natural keyword-rich full description (≤4000 chars)
• Provide 2–8 screenshots per device; make the first two hero shots clear and conversion-focused
• Target current API requirements (API 33+), build as an AAB, include 64-bit support and deobfuscation files
• Run staged rollouts (start 5–10%), monitor crashes/ANRs and expand only after stability checks

Example use cases

• Create optimized title, short and full descriptions for improved search ranking
• Validate all screenshot sizes and feature graphic before uploading to the console
• Audit listing for policy risks like misleading claims, impersonation, or missing privacy policy
• Plan an open beta to gather indexed feedback while preserving a production rollout strategy
• Prepare a pre-launch checklist ensuring content rating, API level, and aab format are correct