Long-running tasks should move to the phone

What it is

“Complex” here means a task that still needs a few more seconds to finish, not whether the feature also lives on the phone, and not how many branches it has. An invite that was accept/decline becomes a choice among four conflicts; a reply that was a template becomes two paragraphs to edit; navigation that was “next turn” becomes a new destination. Once the remaining time on the wrist is visibly going to blow the budget, the work should continue on the phone. The trigger is remaining duration, not a fixed “jump after three steps” rule, and not a pre-drawn job chart between watch and phone.

Why it happens

People start on the wrist because start-up is cheap: no pocket to dig. As input keeps going, the cost of the raised arm accrues by the second, and the one-time cost of pulling out the phone becomes the better deal. Handoff sits at that crossover: grinding on the wrist is now more expensive than switching devices. If the system offers no transfer, people perform a worse switch themselves—dismiss the watch, unlock the phone, hunt the same object from scratch. That switch throws away the seconds already spent. Duration-triggered handoff admits the crossover will come, and when it does, delivers the person to the place already opened, rather than sending them foraging.

Where it stops holding

Actions that end in one confirm (dismiss an alarm, pause music, mark read) are not long by duration and should not be shipped off merely because a phone version exists. With no paired phone, or with the phone elsewhere, the path does not exist; an overtime task can only fail or degrade—it cannot pretend a jump was sent. When both hands are busy in sport, moving to the phone can be more dangerous than staying on the wrist; defer until a stop rather than immediately prompting “use the phone.” Experts may crush the same task under a few seconds; set the threshold on real users’ time, not on a designer’s demo pace.

Applying it

• Mark the points in a flow where “if we are still here, several more seconds remain,” and offer a move-to-phone action only at those points.
• Label the control with the work that will continue (“edit the reply on iPhone”), not a vague “open the app on your phone.”
• Do not gate on a fixed step or tap count: three fast confirms can stay on the wrist; one tap followed by a long scrub should move.
• Verify by logging seconds from entry to handoff, and whether work actually continues on the phone. If several seconds have already burned before handoff appears, or the phone lands on the home screen, the trigger fired late or at the wrong object.

Related

• Within the group: K4.02.1 Tasks that take more than a few seconds do not belong on the wrist · K4.02.3 Handoff must carry state
• Adjacent: K4.07 Division of Labor and Handoff with the Phone · K8.01 Task Continuity · K8.03 Division of Capability across Devices
• Search terms: handoff · duration-triggered transfer · companion device