Handoff should fire on task complexity, not a fixed rule

What it is

Whether work should move to the phone depends on how hard the job is in structure, not on a fixed rule—“jump after three taps,” “jump after five seconds,” “jump whenever there is an input field.” Accepting a meeting invite can be three taps and is still a binary confirm; it should stay on the wrist. Adding a stop to a route may be one tap and still needs a spatial pick and conflict handling; it should move. Complexity here means branching, spatial selection, free text, authentication, and multi-object trade-offs—not how many seconds the wrist has already spent. Seconds are a different constraint. Using seconds as the switch will shoo away simple confirms that run a little slow, and leave fast but structurally deep work on the watch.

Why it happens

Fixed rules match surface statistics: tap count, dwell, whether a field exists. Those statistics do not line up with cognitive load. A binary confirm can be three taps in a row (snooze → snooze again → change alarm) without getting deeper. One tap on a map, by contrast, turns a 1D list into a plane; working memory has to hold location, name, and constraints. Short in time, it is already not wrist work. People decide “the watch cannot do this” when they see branches and an input surface, not when an inner timer fires. A system that uses a fixed threshold inserts “use the phone” at the wrong moment: simple confirms are interrupted, deep work stays on the wrist because it has not yet hit three taps. Handoff becomes noise; people learn to ignore the prompt, including when they actually need it.

Where it stops holding

When accessibility, or sport with both hands busy, makes the phone temporarily unreachable, even deep structure should defer rather than pop immediately. After an expert drills a deep path into a shortcut, complexity falls for that person; leaving that path on the wrist is a user setting, not a reason to cancel handoff for everyone. Long read-only content is not structurally deep and still does not belong on the wrist—that is volume, and should not be gated by a complexity switch, or it will fight compression and duration. Offline, handoff cannot be sent; however deep the task, it can only degrade or fail. The prompt should say “cannot move right now,” not pretend a rule already jumped.

Applying it

• Tag each flow with a structural label: binary confirm, 1D choice, spatial pick, free text, authentication, multi-object trade-off. The last four offer a move to the phone by default; the first two stay on the wrist even if they take more than one step.
• Do not use a global “Nth tap / Tth second” as the handoff switch. If a heuristic is needed, it may fire only on flows already tagged as deep.
• Show the handoff prompt on the frame where the person first sees a branch or an input surface, not after they have already started forcing it with the crown.
• Verify with two contrast tasks: many steps, shallow structure (a chain of confirms); few steps, deep structure (one tap into a map pick). A fixed rule will move the first and leave the second. After switching to structure, the direction must reverse. If it does not, step count is still posing as complexity.

Related

• Within the group: K4.07.1 The watch takes glances and light confirms; the phone takes deep work and heavy input · K4.07.3 After handoff the watch must show that it has already transferred · K4.07.4 The standalone function set when the phone is out of range must be defined in advance
• Adjacent: K4.02 Duration of a Single Interaction · K8.01 Task Continuity · K8.03 Division of Capability across Devices
• Search terms: task complexity · adaptive handoff · cross-device trigger