Stats
Actions
Tags
From mobile-store-assets
Authoritative reference for Google Play Console requirements (May 2026): screenshot specs, feature graphic rules, metadata field limits, ASO/NLP indexing, store-listing experiments, custom store listings (CSLs), promo video, localisation, and recent Play policy compliance. Read this whenever you are authoring Android store copy, sizing Google Play assets, or advising on experiments / CSLs / ASO. The /store-spec skill consults this for every Android field.
How this skill is triggered — by the user, by Claude, or both
Slash command
/mobile-store-assets:android-store-requirementsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill captures the current Play Console rules so `/store-spec` authors
This skill captures the current Play Console rules so /store-spec authors
copy and screenshots that pass Play's metadata and content policy. All
facts include source URLs; uncertainties are flagged.
Format & general rules (all device types):
Google Play accepts portrait, landscape, or mixed orientations within the same set. For phones the canonical aspects are 9:16 portrait or 16:9 landscape; for tablets, 3:4 portrait or 4:3 landscape.
| Surface | Min/Max | Portrait | Landscape | Notes |
|---|---|---|---|---|
| Phone | 2–8 | 9:16 (e.g. 1080×1920, 1440×2880) | 16:9 (e.g. 1920×1080, 2880×1440) | Recommended 1080×1920 |
| 7" tablet | up to 8 | shortest ≥ 1080; e.g. 1200×1920 | 1920×1200 | |
| 10" tablet | up to 8 | 1600×2560 or 2048×2732 | 2560×1600 or 2732×2048 | Both accepted in 2026 |
| Wear OS | ≥ 1 | 384×384 (1:1, no orientation) | n/a | |
| Android TV | ≥ 1 | n/a — TV is landscape-only | 1920×1080 banner / screenshots | |
| Android Auto | n/a | — | — | Not separately required for store-listing visuals |
Sources: App Radar — Play screenshot guidelines · Google — preview assets
Restrictions (will cause ineligibility or removal):
High-conversion design playbook (cross-referenced from Apptamin, Gummicube, ScreenshotWhale, 2026):
| Rule | Why |
|---|---|
| One hook, one focal point. 5–8 word benefit-led headline. | Users assess the graphic in <1 second. |
| Don't repeat the app name in the graphic. | Play renders the name adjacent — repetition wastes pixels and risks the duplication penalty. |
| Drop the giant app icon. A small brand chip (≤12% of canvas height) is acceptable; full icon-style branding is flagged. | The system already shows the icon next to the graphic in every surface. |
| Show a real visual — a featured screenshot, character, or product hero. | Telegraphs the category and the experience instantly. |
| 70–100 px safe margins on every edge. | Crop zones differ per surface (search, listing, promo cards). |
| Centre kept clear for the play-button overlay (centre ~280×140 px). | Promo-video listings overlay a semi-transparent play button. |
| Theme-match the screenshots (palette + tone) but don't duplicate screenshot #1. | Brand consistency without redundancy — Play penalises duplicates. |
| Vibrant background that contrasts with Play's white chrome. | Pure white / pale grey vanishes against the store UI. |
| Test at thumbnail size. Bold weights, big text, text-shadow halo. | CTR is the dominant ranking input for search visibility. |
store-assets-gen's built-in feature graphic implements all of the above:
benefit headline from screenshots[0].headline (the value slot), tilted phone
showing the same screenshot, theme background, 70 px safe margins, no large
app icon, 24-bit PNG flatten.
Sources: ScreenshotWhale — feature graphic spec · Apptamin — feature graphic examples · Gummicube — feature graphic ASO best practices
| Field | Limit | Notes |
|---|---|---|
| Title | 30 chars | Highest ranking weight |
| Short Description | 80 chars | Second highest; shown in search results |
| Full Description | 4,000 chars | Indexed via NLP |
| What's New (release notes) | 500 Unicode chars per language | Per release |
| Developer Name | ≤ 50 chars | Per Play Console UI; not formally documented as a hard public number — uncertain |
| Privacy Policy URL | n/a | Must be active, publicly accessible, non-geofenced, non-PDF; no documented char limit |
Sources: App Tweak — metadata policy 2025 · FoxData — short/full description · SplitMetrics — full description · App Store Manager — release notes · TermsFeed — privacy policy URL
Google Play uses semantic indexing + NLP across title, short description, and full description. Keyword priority:
Title > Short Description > Full Description
Recommended keyword density still ~2–3% (≈ one exact match per 250 chars) for top 2–3 terms. Keyword stuffing triggers metadata-policy rejection and ranking suppression.
The full long description is fully indexed (unlike App Store). "What's New" is NOT a primary indexing surface — treat as user-facing only.
Since 2025 Google rolled out Guided Search (AI-organised category buckets) which weights stability, update cadence and retention more heavily than pure keyword match.
Sources: MobileAction — ranking factors · ASO World — 2025 keyword guide · ASOMobile — ASO 2026
| Setting | Value |
|---|---|
| Concurrent localised experiments | 5 |
| Concurrent default-language experiments | 1 |
| Testable | Text variants (title, short desc, full desc), graphic variants (icon, feature graphic, screenshots, video), or whole custom listings |
| Confidence levels | 90 / 95 / 98 / 99 % (selectable) |
| Traffic split | Auto-equal between variants |
| Audience | First-time visitors only |
Higher confidence requires more first-time installers — your sample size budget grows quickly.
Sources: Play Console — experiments · App Radar — A/B testing
| Setting | Value |
|---|---|
| Max CSLs per app | 50 (Play partners: 100) |
| Targeting types | Country/region, install state (new/inactive/installed), pre-registration, Google Ads campaign, deep-link URL |
| Country exclusivity | Each country can be assigned to only one CSL at a time |
| "Inactive users" definition (added 2025) | Downloaded > 28 days ago and not opened in last 28 days, or uninstalled |
Sources: Play Console — CSLs · Phiture — CSL guide
Sources: Apptamin — promo video guide · App Radar — promo video · Google — YouTube on Play
Sources: Google — translate & localize · Google — supported languages · OneSky
Now mandatory for every app (even non-financial) — updates blocked until completed.
Clarified to cover medical, health, and government-services disinformation.
Pricing shown in screenshots/video must be reflected accurately for the target region.
External hardware dependencies must be disclosed in description.
No specific new 2025/26 listing-copy rule beyond the longstanding "Contains ads" badge driven by the Ads declaration. No fresh "as seen in" / fake-social-proof carve-out — these still fall under Misleading Claims.
Sources: App Tweak — metadata policy 2025 · MyAppMonitor — health policy update · ASOWorld — Oct 2025 updates · Google Developer Program Policy
Google official:
Reputable secondary references used inline above: AppRadar, Apptweak, Apptamin, MobileAction, Phiture, ScreenshotWhale, ASOWorld, SplitMetrics, FoxData, Gummicube, TermsFeed.
Provides CDSS development patterns for drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), and alert classification integrated into EMR workflows.
npx claudepluginhub dbroadhurst/mobile-store-assets --plugin mobile-store-assets