How does the Watch target differ from the Mobile target?

Due to the vastly different ways users engage with Bixby on mobile and watch devices, Bixby behaves differently on each of these devices.

The watch target experience deviates from the mobile target in the following ways:

1. Capsule lock is not enforced for Watch. Prompts should continue to work provided the capsule has adequate voice training. If the utterance does not match the prompt then it would get classified at the top level NL. Additionally, conversation drivers will function as intended only when tapped.
2. Conversation drivers are not displayed in any result views (documentation).
3. The maximum number of vbox elements in a single hbox is 3 instead of the 7 allowed on mobile. This is due to the reduced visual surface area available on the watch versus mobile (documentation).
4. The watch will support Natural language categories in the near future but does not do so currently.
5. Button press and 'wake word' invocation when the screen is on will be hands on (normal) mode as with mobile. However, button press from a paired bluetooth headphone will be considered hands-free (HEF) mode.

NOTE: There is a known issue where users responding to a prompt with an utterance containing a name such as Alex are directed to the Phone functionality rather than staying with their current capsule. This issue is under investigation and will be resolved soon!

To ensure that each experience is properly documented, this article is a living document that will be updated periodically to keep the content current.