Interface Lab
Back to knowledge
Interaction Responsive Motion

Mobile Bottom Action Bar

Mobile Bottom Action Bar turns a frequent interface judgment into an executable constraint before generation.

Design Principle

Critical mobile actions should be thumb-reachable without covering content, errors, or system navigation.

Principle

Critical mobile actions should be thumb-reachable without covering content, errors, or system navigation.

Design action

Pin primary action, secondary action, or price summary to the bottom safe area; add bottom padding and handle keyboard-open states.

Examples

Positive example: Mobile checkout, detail purchase, form submit, filter apply, and multi-step flows. Counterexample: The sticky bottom bar covers the last form error.

Apply when

Mobile checkout, detail purchase, form submit, filter apply, and multi-step flows. Users need to judge state, scope, risk, or next action quickly.

Source notes

Source note: Synthesized from Apple HIG, Material Design, GOV.UK/Polaris/Atlassian component practices, and interaction accessibility principles. Apple HIG Motion: https://developer.apple.com/design/human-interface-guidelines/motion Material Design Motion: https://m3.material.io/styles/motion/overview/how-it-works GOV.UK Design System Patterns: https://design-system.service.gov.uk/patterns/ Shopify Polaris Patterns: https://polaris-react.shopify.com/patterns Atlassian Empty State: https://atlassian.design/components/empty-state

Agent Directive

Pin primary action, secondary action, or price summary to the bottom safe area; add bottom padding and handle keyboard-open states.