After handoff the watch must show that it has already transferred

What it is

Once work has moved to the phone, the watch must not remain in a tappable “tap here to continue” state. It must become a statement that transfer already happened: which job is now on the phone, and that those wrist buttons no longer act. Otherwise people will tap the watch again while taking out the phone, fire a second command, or assume the first never left. This entry is only about how the watch declares state after transfer. It is not about whether to transfer, and not about whether state fields were carried.

Why it happens

Handoff moves control from the wrist into a pocket, but the wrist stays in sight and in feel. The default model is “the device I am looking at is still live”: if the button is there, it still presses. Unchanged UI treats a second tap as a new confirm, a new send, a new payment. Two commands meet on the phone: a duplicated draft at best, a duplicated submit at worst. Delay makes it worse. The phone has not lit yet, the watch has been idle for a few seconds, and people tap again to “hurry it.” Transferred state turns the watch from a controller into a progress plaque: the object name stays, actions are withdrawn or disabled, progress shows if it can be had, otherwise the line is plainly “continue on the phone.” Visible ownership of control matters more than animation. People need to know which hand to look at.

Where it stops holding

A failed transfer (phone lock policy, app missing, network down) must not show transferred. It must show why it failed and restore watch actions, or people are sent to a phone UI that does not exist and can tap neither side. Local confirms that finish immediately (snooze, pause) were never handed off and should not wear transferred state. On a shared demo unit, or when a clerk hands over a watch, “transferred to so-and-so’s phone” leaks the object; the plaque must be able to omit the name. If the watch still offers an emergency undo (cancel a payment just sent), undo is a new light action, not the original editor reopened.

Applying it

• The moment transfer is sent, disable the primary watch button and change the title to the object name plus “continue on the phone.” Do not leave the original Send / Pay / Done.
• After the phone lights and takes over, the watch may show one step of progress. Before it lights, do not pretend completion; only declare “handed to the phone.”
• A second tap on a disabled button must not send another command. At most one light pulse meaning “already over there.”
• Verify by deliberately tapping the watch after transfer is sent, and see whether a second object or a duplicate submit appears on the phone. If it does, transferred state did not take control back. Then fail the path: with the phone gone, does the watch still say “transferred”? If so, the state is lying.

Related

• Within the group: K4.07.1 The watch takes glances and light confirms; the phone takes deep work and heavy input · K4.07.2 Handoff should fire on task complexity, not a fixed rule · K4.07.4 The standalone function set when the phone is out of range must be defined in advance
• Adjacent: K8.01 Task Continuity · B3.01 System Status Visibility · K4.02 Duration of a Single Interaction
• Search terms: handoff status · duplicate action · control ownership