# Play Store assets

What to upload, and where it came from.

## Ready to upload

| Asset | File | Size |
|---|---|---|
| **App icon** | `../assets/google-play-icon-512.png` | 512×512 ✅ |
| **Feature graphic** | `feature-graphic-1024x500.png` | 1024×500 ✅ |
| **Screenshots** | `screenshots/0*-1080.png` | 1080×1920 ✅ (4 of them) |

Play requires the icon, the feature graphic, and at least 2 phone
screenshots. All three are covered.

## Feature graphic

Generated by `feature-graphic.js` — run `node feature-graphic.js` to
regenerate the SVG, then rasterise with `sharp`. It is built from the app
icon's own vocabulary (radar arcs, sweep, one detected blip) so the store
listing and the icon read as one product.

Three things drive the composition, and all of them are about how Play
actually displays it rather than how it looks at full size:

- **Text left, radar right.** Play overlays the app title on this graphic
  on some surfaces; a centred radar would collide with it.
- **Nothing important near the edges.** It gets cropped on some layouts.
- **One accent colour.** It is shown around 340px wide in search results,
  and accent-everywhere reads as noise at that size.

## Screenshots

`screenshots/0*-1080.png` are the ones to upload. The `432×768` originals
are kept beside them as the source.

**These are upscaled, not re-captured.** The source was 432×768 at
exactly 16:9, so scaling to 1080×1920 needed no cropping, and Lanczos
resampling keeps the text edges clean because the UI is vector-rendered
rather than photographic. They read well at full size.

**A native 1080×1920 capture would still be sharper.** If you want that:
run the app on a 1080p device or emulator, capture with
`adb exec-out screencap -p > shot.png`, and replace these. Worth doing
before a wider launch, not worth blocking the first submission on.

## Not needed for this app

- **Tablet screenshots** — only required if you target tablets in the
  store listing.
- **Promo video** — optional.
- **TV / Wear / Auto assets** — the app targets phones only.