Deciding whether to take a task

Variants and decision logs for the requests inbox — what a helper needs to see to say yes, and which actions belong on the row. Each set closes with a log of what we considered and how we got there. Earlier lifecycle screens live in Companion MVP — M3 Revision.

The inbox as decided

Every decision made so far, applied: greeting header with the availability switch (8a), four tabs, no SOS in the inbox, Save · Decline · Accept inline on every row (5a), and saved requests reachable as a filter chip rather than a screen of their own (9b), plus the three network states the API build needs (10a–10c). These eight frames are the spec — the rounds below are the record of how we got here, and their older chrome is superseded, not current. Round 11 adds the location model the nearby query needs: home is the anchor, the chip always says so, and live location is a session-only override (11a–11e). Round 12 then bought the list its room back: 12c's 149dp four-line row and 12a's merged chip row are applied in 7a and 10a above — R11's own frames still show the taller pre-R12 chrome, since they were drawn to settle location, not density. 12b's collapsing top bar is the agreed next step, not built.

The header grew. The row is the bigger problem.

On a 360×800dp phone the chrome above the list is ~165dp — status 24, greeting 52, anchor chip 45, filter row 43 — plus 60 for the nav, leaving ~575dp of list. One request row is ~193dp, so the helper sees 2.9 rows, and 2.6 when the widened-radius notice is up. Header trims alone buy a third of a row; the row is where the space is. Three candidates below, each with its measured cost. The frames are 620px crops, not 800dp phones — read the per-row numbers, not the number of rows you can see in the bezel.

A task is an appointment, not a dispatch

The nearby query needs a reference point. Home address, live GPS and a helper-set working area were all on the table, plus five hybrids — and the call turns on one fact: rows carry a start instant hours or days out, so where the helper is standing right now is false precision. 11a is the V1 model: home as the anchor, always stated on screen, with an adaptive radius and a session-only live override. 11f–11h are what happens when the helper taps it. Note these frames predate 12c — the anchor behaviour here is current, the row and header density is not.

Customer identity on the request row

Current rows read "Meera R." — which is the worst of both options: it pays the full cost of disclosure and buys almost none of the protection. Below: why the name is the wrong field to argue about, what should occupy that line instead, and what gets disclosed when. Nothing applied to the current screens.

Request expiry

The current rows all say "Expires in…", which quietly assumes one clock, one rule and one visual treatment. There are three clocks, the rule is lead time rather than task type, and only one band of tasks should show a countdown at all. Notes and candidate treatments below — nothing here is applied to the current screens yet.

The bookmark had no destination

Every row carried a Save button and nothing in the app could reach the result — no tab, no list, no filter. Four options were on the table; 9b is built into the current screens above. The others are recorded here because the case for cutting Save entirely is strong enough to revisit after launch.

Three places a toggle can live

The chip had one real flaw: it sits 8px above a row of actual filter chips, so it reads as a filter, not a control. A switch fixes the affordance — the question is only where it goes and whether the state word survives. All three keep the confirm sheet on the off direction and instant on the on direction.

Empty, lost, blocked, expired

The four states a helper hits in week one. All stock M3: full-width tonal containers for status, standard list rows, one filled button per screen, no new colour beyond the palette.

Triage without opening the task

Accept, decline and save from the list. The question is only whether accept belongs there too — it's the one action with a penalty attached, and the facts that prevent regret live on the detail screen. 5c adds swipe on top of whichever button layout wins.

What a helper needs to say yes

Three ways to answer "is this worth my day?" in the list itself. Same rows, different amount of maths done for the helper. Travel is measured from their registered area for future dates, from their previous drop point when the task is same-day — and the row says which.