Bixby Developer Center


6812 (Card OnClick)

As part of our effort to streamline the behavior of card components and make implementation simpler, the Bixby platform will now render a card as a “card” when it is clickable, and as an “area” when it is not clickable. For example, for capsules that are in the Marketplace, Bixby will automatically render cell-card to look like a cell-area when it is not clickable. No code change is required.

Here are some additional changes to be aware of:

  • You will need to use a card component with a valid on-click when rendering list-of components. With the selection-of component, if you don't have an on-click, Bixby creates an intent for you. We've deprecated the use of has-details for both list-of and selection-of list components.

  • We've introduced a runtime flag, auto-on-click-for-list-of, which is part of runtime-version 7 and, if enabled, preserves the old auto-selection behavior for list-of. For versions before 7, it defaults to true, In runtime 7, it defaults to false, and the absence of the runtime flag enables the always-respect-on-click behavior, which is the new default on-click behavior. You should only add the runtime flag to runtime version 7 if you want to preserve the previous on-click behavior.

  • You can now add a badge, external-link-badge, to a parent component, indicating to users that tapping on the component takes them out of Bixby to an external application. You should add this component to your on-click definition if tapping on this component will navigate the user away from Bixby.

  • With on-click, you can now add a url, which takes the users to the specified URL when they tap on a component.


Make sure that you are following the App Punch-Out policies if your on-click makes users exit Bixby.

Deprecation Stages

Learn more about the deprecation stages.

  • Stage 1: R20F
  • Stage 2: R20I
  • End of Life: None