Button

An overview of how buttons and the button group operate within our mobile experiences.


Overview

Unlike how buttons are ulitized for desktop, buttons for our mobile experiences are applied more rigidly. While in our desktop experiences buttons of all variants are featured prominently in the contents of a given page (within cards, alongside tables etc), when used in our mobile experiences, buttons for the most part, are contained within the navigation structure of an mobile app.

When not contained in the navigation structure, buttons should only be of the tertiary and/or ghost variant.

Aside from the differences in positioning, mobile buttons have been slightly enlarged in order to better facilitate user actions through touch as opposed to mouse clicking.

Button Overview

Usage


Do
Button group replacing bottom navbar.

Buttons, particularly button groups, should be placed within the navigation structure, replacing the bottom navbar when used.

Don't
Button group on the page with bottom navbar also visible.

Horizontal button groups should be avoided due to the difficulties users have when interacting with this limited touch space. Additionally button groups, unless absolutely necessary, should not placed alongside the bottom navbar.

Do
Primary and secondary button group replacing navbar with only ghost button throughout the page.

If buttons are placed in an flow that holds a button group, then only tertiary and/or ghost buttons should be used.

Don't
Primary and secondary button group replacing navbar with more secondary buttons throughout the page.

Avoid the use of secondary and/or primary buttons alongside the button group in the navigation.

Do
Mobile screen with button group and primary button as the last button in the group.

Position the primary call-to-action button closest to the user. This means that the primary button should be at the very bottom of a given button group.

Don't
Mobile screen with button group and secondary button as the last button in the group.

Avoid placing the primary button at the top of a given button group as this was require users to strain when wanting to perform this action.