Command

PePersonal JEJust Electrolyte RTRelease Timer TtTacTile CSClearSource AtAthletic

TacTile›Launch TacTile›Android›Android — Build & release·15 in this wave

Submit Android build for reviewTo do · blocker Approve: Android releaseTo do · blocker Seed a demo account — it blocks BOTH the Play screenshots and Caitlin's QA passBlocked · blocker Produce phone + tablet Play screenshotsBlocked Complete the Play Data Safety formIn progress Full device test pass on a physical Android phoneTo do Full device test pass on a physical Android tabletTo do Play Store review pre-flightIn progress Android CI + release automation (the wave goal had no task for it)Done Play feature graphic (1024x500) — hard submission requirement, nobody has filed itDone Public data-deletion page — Play requires it reachable WITHOUT sign-in (verified 307 today)Done The Android tier can be GREEN on a tree that does not clean-build — Hilt errors hide behind stale codegenTo do Write Play Store listing copyIn progress Play 7"/10" tablet screenshots — after the tablet adaptation landsTo do AssetsViewModelFailureTest flakes ~3% — cause not identified, symptom guarded not fixedTo do

Wave

Android — Build & release

No CI, no Play metadata, no release automation exist today. iOS has working Fastlane; Android has nothing.

TacTile › Launch TacTile › Android › Android — Build & release

3/15 done12 open3 open blockers

Selected taskclear

Produce phone + tablet Play screenshots

BlockedOwner · Vivt_d3930436

Unlocks 2Play Store review pre-flight Approve: Android release

Show the prompt

You are Viv, the agent for the TacTile lane of Command.

Open the lane and work there:

```bash
cd ~/Command/tactile && claude
```

Read that lane's CLAUDE.md and lane.json before you touch anything — they
carry your identity, your scope, and the hazards specific to this lane.
Read state from the hub (https://internal.tactile.to) or ask. Never guess at it.

## The task

**Produce phone + tablet Play screenshots** · blocked

Where it sits: TacTile › Launch TacTile › Android › Android — Build & release

## Unlocks 2

- Play Store review pre-flight
- Approve: Android release

## The brief on file

Viv — BLOCKED, on two separate things, and the second one is bigger than this task.

WHERE THEY GO when unblocked: apps/android/fastlane/metadata/android/en-US/images/ (phoneScreenshots/, tenInchScreenshots/, sevenInchScreenshots/), uploaded by `bundle exec fastlane metadata`. The directory and the upload path exist as of PR #225; only the images are missing.

BLOCKER 1 — the app cannot get past its own launch guard on this machine. apps/android/local.properties holds only sdk.dir, so BuildConfig ships empty networking config and NetworkConfig.kt throws on startup. An API 36 emulator is set up and working (Medium_Phone_API_36.1) and the screenshot pipeline is proven — `adb exec-out screencap -p` was used repeatedly during this session — but every screen past sign-in is unreachable. The only screenshot obtainable today is the auth screen. Tracked as t_f85c04f8; needs a 1Password read, so it is Matthew's.

BLOCKER 2 — TABLET SCREENSHOTS CANNOT BE PRODUCED AT ALL, and this task's title asks for them. The app is portrait-locked in the manifest (android:screenOrientation="portrait" on MainActivity) and 0 of ~53 screens are size-aware. There is nothing to photograph: a tablet run would show a stretched phone layout. Tablet support is its own from-scratch wave, w_b88ca898. Play only requires tablet screenshots if you declare tablet support, so THIS TASK SHOULD BE SPLIT — ship phone screenshots with the phone launch, and let tablet screenshots follow w_b88ca898. Do not hold the submission for them.

WHAT PLAY ACTUALLY REQUIRES for a phone-only launch: at least 2 phone screenshots (min 320px, max 3840px on the long edge, 16:9-ish or taller), a 512x512 app icon, and a 1024x500 feature graphic. The 512 icon already exists at brand/dist-v1/android/play-store-icon-512.png (generated in PR #225 from the same source art as the launcher icon). The FEATURE GRAPHIC does not exist anywhere and nobody has filed it — it is a hard requirement and will block submission on its own. Worth filing separately.

SUGGESTED SHOT LIST once unblocked, one per pillar rather than one per screen: (1) Dashboard with real data, (2) the destination create flow's category grid — it is the most visually distinctive screen, (3) a QR design in the studio, (4) the destination launchpad showing the live link + edit, (5) Analytics. Capture at the emulator's native 1080x2400.

## How to work this

- Do the work, don't just plan it. If the fix is obvious and safe, make it.
- Surface anything needing Matthew's sign-off instead of deciding it yourself.
- Short replies. Lead with the answer, then stop.
- Finish by saying what changed, what you verified, and what you'd do next.

To doIn progressDoneBlockedPick a wave on the left · tap a task to expand it

Lanes

Android — Build & release

Produce phone + tablet Play screenshots