Listing requirements
Each app version carries a store listing modeled on Google Play requirements.
Every text and asset field is per language, and en_US is the default
language that must always be complete.
Text fields (per language)
| Field | Limit | Notes |
|---|---|---|
| App title | ~30 characters | Short, descriptive |
| Short description | ~80 characters | One-line summary |
| Full description | ~4000 characters | Long-form description |
| Release notes (“What’s new”) | per version | What changed in this version |
Asset fields (per language)
Assets are validated against fixed formats and dimensions on upload; non-conforming assets are flagged as findings.
| Asset | Format | Dimensions |
|---|---|---|
| App icon | PNG, square | 512 × 512 |
| Feature graphic | PNG/JPG | 1024 × 500 |
| Phone screenshots | PNG/JPG | Min/max count and aspect ratios, like Play |
| Head-unit screenshots | PNG/JPG | Landscape head-unit captures (e.g. 1408 × 792) |
Default language and fallback
- A version cannot be submitted for review without the required fields
(title, short description, full description, icon, and at least the minimum
screenshots) present in the default language
en_US. - Additional languages are optional but are validated when present.
- When a vehicle requests a language you have not localized, the listing falls back
to
en_US.
Tips
- Write the
en_USlisting first; it is your safety net for every market. - Keep screenshots current with the shipped UI — stale screenshots are a common review note.