Bixby Developer Center


User Experience Policies

As a developer, strive to ensure that users have a predictable experience in Bixby, no matter which capsule they are using. Refer to the design principles behind Bixby while developing your capsule. Also, the Designing Conversations topic describes how each conversation between Bixby and users should flow, including how to write dialog and the components to use in various views. The Designing With Bixby Views guide discusses the components that you should use within views. This topic specifically defines the key policies that govern a consistent user experience.

App Punch Out Policies

In general, users should stay in the Bixby interface as much as possible. This gives you several benefits:

  • Capsules can work across multiple devices seamlessly if you stay within the Bixby interface and leverage Bixby Views.
  • You don't have to keep versions in sync between devices. Deep links within apps introduce dependencies between Bixby and specific app versions, but you can avoid this by staying in the Bixby interface.
  • Hands/Eyes Free experiences are smoother through Bixby, since users won't have to rely on screen UI for interactions or display.
  • The conversation context is known and clear, which allows for building a richer and smarter user experience with deep NL integration and learning.
  • Follow-ups are easily supported and based on a result that is within the scope of the Bixby conversation.
  • You can contain your work within Bixby Developer Studio. You won't have to span between both the server side and Android APK side.

In general, you need to consider two types of situations for punching out: as a direct request from the user and as a tap on the Bixby UI.

When You Should Punch Out

If your user makes a direct request in these situations, or if the user taps on a result-view component, you can punch out of Bixby to an application with the app-launch component in a result-view. If the utterance requires more information (for example, Which John do you want to call? or On which service should I play this video?), you should handle this in Bixby before launching the appropriate application.

You can use app-launch in the following situations:

  • The user asks to launch an app with a direct command.
    • "Open the Facebook app"
    • "Launch the YouTube app"
  • The user requires a response from a deeply dependent hardware or device sensor feature.
    • "Take a picture"
    • "Call dad's cell number"
    • "Get me directions to 60 S Market street in San Jose, California"
  • The user asks to play immersive content beyond a thumbnail video snippet.
    • "Play Grace and Frankie on Netflix"
    • "Launch Clash of Clans"
  • The user wants more details for a piece of content that is summarized in the Bixby UI (Open app for more information)
    • View an expanded weather forecast with radar
    • View the biography of a musical artist

When You Should Stay Within Bixby's Interface

For situations not specifically listed in When You Should Punch Out, you should model and train Bixby to stay within its interface. Additionally, if you need to disambiguate any situation in the previous section, you should gracefully handle this in Bixby before punching out to the app. For example, if users ask "Call John" and there are multiple Johns in their contacts list, you should create an input-view to list the contacts, asking Which John? for users to select.

Do not use app-launch in the following situations:

  • To complete a situation that does not fall into the previous section that could be completed in Bixby's interface.
  • As an alternative to creating a Bixby Views file, if you can't recreate your UI with Bixby Views. In this situation, you should work with our team to help use Bixby Views with your capsule or to file a feature that you might need.

If you need to direct a user to another location and your situation does not follow the app launch policies listed above, you should consider using an attribution-link instead.