Command

PePersonal JEJust Electrolyte RTRelease Timer TtTacTile CSClearSource AtAthletic

TacTile›Launch TacTile›Web›Web → app handoff·12 in this wave

Approve: Web → app handoffTo do · blocker Register the deep-link scheme on iOSTo do Set up iOS Universal Links for the handoff pathsTo do Set up Android App Links for the handoff pathsTo do Build the deep-link routing layerTo do Design the handoff experienceTo do Build the desktop handoffTo do Build the mobile-web handoffTo do Handle the not-installed case gracefullyTo do Build the return path after programmingTo do Make the capability boundary honest in the web UITo do Verify the handoff end to endTo do

Wave

Web → app handoff

Web can't write NFC tags, so programming a physical tag has to hand off cleanly to the native app. Deep-link infrastructure may not exist at all — verify before building on it.

TacTile › Launch TacTile › Web › Web → app handoff

0/12 done12 open1 open blocker

Selected taskclear

Design the handoff experience

To doOwner · met_1dc66e7d

Matthew — Decide what a web user sees when they need to program a physical tag. Done when: a documented decision covers (a) desktop QR-to-phone, (b) mobile-web direct app-open, (c) app-store fallback preserving intent, (d) the return path after programming — ready to hand to engineering. File: apps/web-mobile/features/nfc/components/NfcExplainerSection.tsx, apps/web-mobile/features/nfc/constants.ts.

Unlocks 5Build the desktop handoff Build the mobile-web handoff Handle the not-installed case gracefully Build the return path after programming Approve: Web → app handoff

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

**Design the handoff experience** · to do

Matthew — Decide what a web user sees when they need to program a physical tag. Done when: a documented decision covers (a) desktop QR-to-phone, (b) mobile-web direct app-open, (c) app-store fallback preserving intent, (d) the return path after programming — ready to hand to engineering. File: apps/web-mobile/features/nfc/components/NfcExplainerSection.tsx, apps/web-mobile/features/nfc/constants.ts.

Where it sits: TacTile › Launch TacTile › Web › Web → app handoff

## Unlocks 5

- Build the desktop handoff
- Build the mobile-web handoff
- Handle the not-installed case gracefully
- Build the return path after programming
- Approve: Web → app handoff

## The brief on file

Product decision needed before tasks 6-9 (desktop handoff, mobile-web handoff, not-installed fallback, return path) can be built. Current state, confirmed by audit: apps/web-mobile already has an honest "can't do this here" explainer at features/nfc/components/NfcExplainerSection.tsx — it correctly tells the user browsers can't write NFC chips and the native app handles it. But the CTA underneath is just two flat buttons linking to APP_STORE_URL / PLAY_STORE_URL (features/nfc/constants.ts) — generic store search links, not deep links, no destination pre-loaded, no return path, and the App Store URL is literally a placeholder (per the code comment: "TacTile has no published App Store listing yet"). Lay out and decide: (1) Desktop — a QR code that opens the app on the user's phone with the specific destination pre-loaded (requires Universal Links/App Links + routing layer, both separate tasks). (2) Mobile web — attempt a direct app-open (custom scheme or universal link) instead of just linking to the store badge. (3) Not-installed fallback — when the app-open attempt fails, fall back to the correct store, but preserve which destination/tag the user was trying to program so it survives install + first-launch. (4) Return path — what the web app shows after the tag is successfully programmed in the native app (confirmation state, does the web page auto-refresh, does the app deep-link back to web, etc). Every open question must be resolved before this goes to engineering — a brief with open questions stays a draft.

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

Web → app handoff

Design the handoff experience