Uh oh! We couldn’t find any match.

Please try other search keywords.

Bixby Developer Center

Guides

Designing Your Capsule

A conversation with Bixby is like a choreographed back-and-forth between Requests made by the user and Moments introduced by Bixby.

Requests

Users can make a request by voice or typing.

Requests

Additionally, if the users are in a Moment, they can follow up by tapping on a conversation driver or layout on the screen.

Moments

In the realm of Bixby conversations, a response is referred to as a “Moment”. A Moment is composed of three parts:

  1. Bixby Dialog
    Bixby’s dialog is a key aspect of a Moment and sets the context for the rest of the Moment. On a device with a screen, this is displayed in the conversation zone. For more information, see Refining Dialog in the Developer Guide.
  2. Bixby Views
    Views render the content of a Moment. The Bixby platform uses Views to scale your content across devicess. On a device with a screen, Views are displayed in the content zone.
  3. Bixby Follow-Ups
    Depending on the type of Moment, you can include an Action Button or a Conversation Driver to help move the conversation forward. On a device with a screen, Action Buttons and Conversation Drivers are displayed in the action zone.
    Follow up

Three Types of Moments

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.

Moments types

Designing with Moments

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.

Some Archetypal Conversations

Following are some archetypal conversations from a design standpoint:

Simple answers

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.

For example:

User: "What’s the weather in San Francisco?"
Bixby: It’s sunny and 72ºF.

Simple answer example

Exploring choices

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.

For example:

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

Exploring choices

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.

For example:

User: "Reserve a table for 7pm at the Liholiho Yacht Club"
Bixby: How many people are in your party?
User: "Three"
Bixby: Ready to make a reservation? (Screen confirms all the information)
User: "Yes"
Bixby: You are all set for dinner at Liholiho Yacht Club

Getting things done!

For a more complex example, see the Basic Cart Transactional Sample Capsule Walkthrough.