Command

PePersonal JEJust Electrolyte RTRelease Timer TtTacTile CSClearSource AtAthletic

TacTile›Launch TacTile›DevOps›DevOps Launch Readiness·20 in this wave

Wave

DevOps Launch Readiness

Gated by the surfaces existing. Android is the long pole — it has no release automation and no UI tests, while iOS already has working Fastlane.

TacTile › Launch TacTile › DevOps › DevOps Launch Readiness

4/20 done16 open1 open blocker

Selected taskclear

Add Android instrumented/UI tests

To doOwner · Vivt_f58af820

Unlocks 2Build Android release automation Approve: DevOps Launch Readiness

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

**Add Android instrumented/UI tests** · to do

Where it sits: TacTile › Launch TacTile › DevOps › DevOps Launch Readiness

## Unlocks 2

- Build Android release automation
- Approve: DevOps Launch Readiness

## The brief on file

Viv — build an androidTest/ instrumented UI test suite for apps/android covering signup and create-destination flows. Done when: the androidTest/ suite covers signup and create-destination and passes on an emulator. Android has zero UI tests today (androidTest/ does not exist) — this is greenfield.

## 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

DevOps Launch Readiness

Add Android instrumented/UI tests