A conversation with Bixby is like a choreographed back-and-forth between Requests made by the user and Moments introduced by Bixby. All these interactions together are defined as a conversation model, which helps Bixby give users the best experience possible. The conversation model binds capsule models together in a way that reflects an actual conversation with an end-user. It also defines the pattern you, the developer, should follow when designing your capsule's user experience.
Users can make a request by voice or typing.
Additionally, if the users are in a Moment, they can follow up by tapping on a conversation driver or layout on the screen.
In the realm of Bixby conversations, a response is referred to as a “Moment”. A Moment is composed of three parts:
When a user makes a request, Bixby is designed to get the user to a result as quickly as possible. However, along the way it might seek input and confirm choices when required. As a quick outline, Bixby’s conversation model is composed of three moments:
In an Input Moment, Bixby collects and clarifies all the information needed to complete a user’s request. Once all of the necessary information is provided, the conversation moves to the next step.
In a Confirmation Moment, Bixby asks the user to review critical information before taking an important action. This Moment is an opportunity for the user to review all the choices and decisions they have made (or Bixby assumed based on selection or preference learning), before an action or transaction is completed.
In a Result Moment, Bixby completes an action or presents information that delivers on the user’s goal. A Result Moment can be in the form of a list of results, single result or the receipt of a transaction.
Users are in one Moment at any time
Unlike messaging and email, there is no need for the user to go back through a conversation history with Bixby. That’s why we forward the user’s goal, one Moment at a time, letting both Bixby and the user dance in the conversation.
Conversation model defines how Moments occur
The conversation model defines how all the Moments can occur with in a conversation for a particular capsule. Moments never appear out of order.
Bixby rewards specificity
The beauty of a conversation is that these moments are strung together depending on what the user asks Bixby to do. The more specific a user is, the further along they go in a conversation.
Every Moment is an opportunity to build a relationship
Getting to know a user might take time, but each interaction you have with Bixby informs a larger narrative that helps users do things more easily and quickly as Bixby learns.
Following are some archetypal conversations from a design standpoint:
When a user makes a request looking for very specific information, these can be resolved quickly with a simple answer presented in the form of a Result Moment.
User: "What’s the weather in San Francisco?"
Bixby: It’s sunny and 72ºF.
Often users make requests which are open-ended. You could present choices in a Result Moment or quickly clarify the user’s intention with an Input Moment.
User: "Find me some restaurants nearby"
Bixby: Here are some good restaurants in San Francisco, CA
User: "Tell me more about Liholiho Yacht Club"
Bixby: Liholiho Yacht Club is rated four and half stars and is 5 miles away
For a more complex example, see the Simple Search Walkthrough Sample Capsule.
Getting things done
Bixby is designed to handle complex, multi-step requests that are about getting things done. This may involve seeking clarification with an Input Moment and confirming all the choices the user has made with a Confirmation Moment before finally completing the request.
User: "Reserve a table for 7pm at the Liholiho Yacht Club"
Bixby: How many people are in your party?
Bixby: Ready to make a reservation? (Screen confirms all the information)
Bixby: You are all set for dinner at Liholiho Yacht Club
For a more complex example, see the Basic Cart Transactional Sample Capsule Walkthrough.