Command

PePersonal JEJust Electrolyte RTRelease Timer TtTacTile CSClearSource AtAthletic

TacTile›Launch TacTile›Android›Android QA — Sign-off·94 in this wave

Approve: Android QA sign-offTo do · blocker Decide how QA runs against a prod-only database before Kaitlynn's phone passTo do · blocker QA: Destination creation — all 14 typesBlocked QA: Destination launchpad and editingTo do QA: Delete account and sign outDone QA: Auth and onboarding — all six stepsBlocked QA: New destination category gridDone QA: Category source pickersDone QA: Website destinationDone QA: Link Hub destinationDone QA: Payment destinationDone QA: Menu destinationDone QA: Gallery destinationDone QA: Video destinationDone QA: Audio destinationDone QA: Note destinationDone QA: Document destinationDone QA: Wifi destinationDone QA: Bluetooth destinationDone QA: Form destinationBlocked QA: Action destinations — all 8 sub-typesBlocked QA: Shop cart and checkoutDone QA: DashboardDone QA: CanvasDone QA: Assets — all four tabsDone QA: Group and family launchpadsDone QA: Analytics — all six subpagesDone QA: QR generation and design editorDone QA: NFC encoder and launchpadTo do QA: Settings — all seven screensDone QA: AI agent and approvals inboxBlocked QA: ConnectCard and vCard buildersDone QA: ShopDone QA: Canvas node tap and launchpad (confirmed silent dead end)Done QA: Canvas search overlayDone QA: Assets — Triggers tabTo do QA: Assets — Destinations tabDone QA: Assets — Groups tabTo do QA: Assets — Families tabDone QA: Group launchpad screenTo do QA: Family launchpad screenBlocked QA: Analytics — Deep DiveDone QA: Analytics — CompareDone QA: Analytics — Real-timeDone QA: Analytics — GoalsDone QA: Analytics — DashboardsDone QA: Analytics — MapDone QA: Analytics — pickers and sheetsDone QA: QR logo cropperDone QA: QR code list reachability (confirm currently unreachable)Done QA: Trigger launchpad (Manage QR / Manage NFC Tag)To do QA: Settings root listDone QA: Profile settingsDone QA: Appearance settingsDone QA: Notifications settingsDone QA: Help CenterDone QA: Contact supportDone QA: Custom domain settingsDone QA: Profile photo crop screenDone QA: Agent sessions sheetDone QA: Shop home and product detailDone FIX: Payment destination — Just testing the QADone FIX: Form destination [Android] — same issue with the menu (safari can't open... message)Done FIX: Action destinations — all 8 sub-types [Android] — for facetime, when i enter the phone number or apple ID field, the…Done FIX: Destination creation — all 14 types [Android] — link and payments creation looks good. previewer for payments doesn't…Done FIX: Destination launchpad and editing [Android] — the launchpads need work to visually match branding better and just…To do FIX: Auth and onboarding — all six steps [Android] — i can't test thisBlocked FIX: Gallery destination [Android] — when i am selecting images to add, the blue button at the bottom of the…Done FIX: Audio destination [Android] — when i hit the record audio button, it needs to open the device's…Done FIX: Analytics — Real-time [Android] — the main widget on the real-time dashboard does not match the UI. it…Done FIX: Help Center [Android] — the annimation that happens when a question is expanded looks bad.…Done FIX: Assets — Families tab [Android] — visually each family needs to be in a card to match the styling of…Done FIX: Analytics — all six subpages [Android] — map is totally messed up. when i select map from the list of dashboard…Done FIX: Contact support [Android] — when i hit the compose email button it opens the email but it should…Done FIX: Analytics — Map [Android] — seems totally broken. the map takes over the whole screen right now and…Done FIX: Assets — Triggers tab [Android] — the trigger groups listed at the top of the list of triggers still need…Done FIX: Help Center [Android] — the fix worked. now hide the troubleshooting section. hide the…Done FIX: Audio destination [Android] — still won't let me record auidoDone FIX: AI agent and approvals inbox [Android] — after asking it to make a red qr code then asking it to connect it to a…Done FIX: Assets — Groups tab [Android] — there is no group tab, since groups are listed at the top of the…To do FIX: Trigger launchpad (Manage QR / Manage NFC Tag) [Android] — looks pretty good for now i guess. however when i hit edit for any…To do FIX: Group launchpad screen [Android] — there currently is no group launchpad. that needs to be created.To do FIX: Family launchpad screen [Android] — remove the schedule section from family launchpad. there is no timeline…Done FIX: AI agent and approvals inbox [Android] — seems like nothing happens when i hit reject, tweak, or approve. no…Done Android Preview fires a real webhook — make destination preview side-effect-freeDone FIX: Destination creation — all 14 types [Android] — gallery looks good. the venmo payment preview looks ok but when i hit…Done FIX: Family launchpad screen [Android] — i need to be able to close the keyboard by sliding it down and tapping…Done FIX: Assets — Triggers tab [Android] — looks good. there needs to be a manage group page like there is for a…To do QA: Android analytics 24h chart groups scans by the hourBlocked QA: Android goal editor offers a Daily repeatBlocked QA: Android Free account sees upgrade cards on every Analytics pageBlocked QA: Android AI Insights asks a Plus account to upgrade to ProBlocked QA: Android AI agent draws a failed step with a red mark, not a green checkBlocked QA: Android Program NFC still recognises a normal TacTile stickerBlocked

Wave

Android QA — Sign-off

Page-by-page human sign-off on PHONE ONLY. Owner Kaitlynn, gate Matthew. Tablet verification is a separate later wave (Android QA — Tablet), because phone must prove the backend and feature logic before any tablet effort. All 16 checks were rewritten to phone-only on 2026-07-26.

TacTile › Launch TacTile › Android › Android QA — Sign-off

68/94 done26 open2 open blockers

Selected taskclear

QA: Android Program NFC still recognises a normal TacTile sticker

BlockedOwner · Kaitlynnt_0929db96

Check that, after the Android NFC link-check was tightened to tactile.to addresses, a normal working TacTile sticker still opens its page when tapped and is still recognised as a TacTile tag by the Program NFC scanner.

No dependencies in this wave — nothing gates it, and nothing waits on it.

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

**QA: Android Program NFC still recognises a normal TacTile sticker** · blocked

Check that, after the Android NFC link-check was tightened to tactile.to addresses, a normal working TacTile sticker still opens its page when tapped and is still recognised as a TacTile tag by the Program NFC scanner.

Where it sits: TacTile › Launch TacTile › Android › Android QA — Sign-off

## The brief on file

[FOR KAITLYNN]
TEST ON: your Android phone, in a TacTile test app Matthew has sent you that was made after the NFC link-check fix. If you are not sure it is the newest, tap Skip for now and write 'no build yet'. You also need a TacTile NFC sticker or card that already works, for example the one you programmed in the "NFC encoder and launchpad" check. No sticker? Tap Skip for now and write 'no tag'.

WHAT THIS IS: The Android app decides whether an NFC tag is a TacTile tag by looking at the web address stored on it. We tightened that rule so only addresses on tactile.to count. A normal TacTile sticker must still be recognised, both when you simply tap the phone on it and when you scan it inside the app. This check confirms nothing broke for a normal sticker.

WHERE: Part 1 is on the phone's home screen with the TacTile app closed. Part 2 is in the app: Dashboard, tap "Program NFC" (or Assets tab, tap the "Create" pill, then "Program NFC").

DO:
1. Close the TacTile app. Wake the phone and hold the back of it against the sticker. See what opens.
2. Open TacTile and go to "Program NFC". Tap "Scan NFC tag" and hold the phone against the same sticker.
3. Read what the screen says. Then go back out without changing anything.

PASS IF:
- Step 1: the sticker's page opens (in the TacTile app or your browser), the same as it did before.
- Step 3: the screen recognises it as a TacTile tag, for example "Already a TacTile tag" (or the tag's own manage screen if you are signed in as its owner). It must not say "This tag holds third-party data".

NOT PART OF THIS CHECK: tags that carry a link to some other company's website, tags written with a customer's own web address instead of tactile.to (the app now treats those as "not a TacTile tag" on purpose, until Matthew decides how custom addresses should work), writing to a blank tag (that is the "NFC encoder and launchpad" check) and the iPhone app.

IF SOMETHING LOOKS WRONG: Type which step and what the screen said. For example: "step 3 said 'This tag holds third-party data' for a sticker I made in the app".

STUCK OR CAN'T FINISH? Tap "Skip for now" and type what stopped you (for example "no tag"). Even a few words helps.
[/FOR KAITLYNN]

(The block above is all Kaitlynn sees under "What am I checking?".)

STOP CONDITION (engineering): blocked until the PR is merged and an Android test build containing it is on Kaitlynn's phone. The host anchoring is commit 22492b02 on draft PR #765 (https://github.com/TacTile-dev/TacTile/pull/765, branch r32/native-agent-ndef), which Matthew has not merged. Android client change only: no API deploy is needed. Do not flip this card to todo before the build is on her phone. When it is: (1) confirm she has a working TacTile sticker whose address is on tactile.to (SELECT-only check, or ask her; if she has none, the missing input is a sticker programmed by her in the NFC encoder check t_a474cc8a); (2) flip with python3 ~/TacTile-dev/tools/hubnote.py status THIS_ID todo. Depends on t_191475f3 (done; PR #765, tests, mutations and both reviewer verdicts are in its note). Known limits, so a pass is read correctly: Part 1 is a regression guard only, because OS tap dispatch is decided by the app manifest (tactile.to/auth/callback, tactile-connect.com/auth/callback, tactile.to/app/*), which this PR does not touch; Part 2 exercises the changed code (NdefUriDecoder.extractHash, used by NfcScanAnalysis and the encoder diagnose screen); a tag written with a custom domain now reads as third-party data in the in-app scanner until the custom-domain product call on t_191475f3 is made; no emulator or production sign-in was used to verify, only JVM tests (NdefUriDecoderTest 11/11) and the iOS xcodebuild matrix.

## 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 QA — Sign-off

QA: Android Program NFC still recognises a normal TacTile sticker