# Bottom Sheet

A bottom sheet is a mobile-oriented surface that rises from the bottom edge to present contextual content or actions while retaining some sense of the underlying view.

- Type: artifact
- Domain: Experience & interface
- Level: Foundational
- Last reviewed: 2026-09-24
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/bottom-sheet/>)

## What it means

A bottom sheet is a sheet presentation anchored to the lower edge of a screen. It may be modal, blocking interaction outside it, or non-modal, allowing continued interaction with the underlying content. Some sheets support several stable heights, often called detents.

## Why it matters

Bottom sheets place contextual choices near thumb reach and preserve spatial continuity better than an unrelated page. Their behavior must still make modality, resizing, dismissal, scrolling, and focus predictable.

## When to use it

Use a bottom sheet for a bounded mobile task, compact set of contextual actions, or supplementary details that benefit from keeping the current view visible. Use a full page for dense, lengthy, or deeply navigational content, and an alert for a brief critical decision.

## How it works

1. Choose modal or non-modal behavior from whether users must finish the sheet before returning to the parent view.
2. Select an initial height that reveals the purpose and important action without hiding essential context.
3. Provide clear controls for dismissal and, when supported, accessible resizing between defined heights.
4. Coordinate sheet dragging with internal scrolling so gestures have predictable effects.
5. Test focus, screen-reader order, large text, keyboard appearance, rotation, and small screens.

## A practical example

A map app opens a non-modal bottom sheet for a selected restaurant. The collapsed height shows its name and status; expanding reveals details and actions while the map remains usable. A checkout task instead opens a modal sheet because its state must be resolved first.

## Where it breaks

The pattern is platform-sensitive and can hide content, conflict with scrolling gestures, or become a full-screen page in practice. A visible drag handle alone may not provide an operable resize mechanism for assistive-technology users.

## Common mistakes

- Leaving users unsure whether the underlying view is interactive.
- Using a sheet for content too long or complex for the available space.
- Relying only on swipe gestures for dismissal or resizing.
- Letting the on-screen keyboard cover the active field or primary action.

## Sources

1. [Sheets](<https://developer.apple.com/design/human-interface-guidelines/sheets>) — Apple · Institutional guideline
2. [Modality](<https://developer.apple.com/design/human-interface-guidelines/modality>) — Apple · Institutional guideline

## Related topics

- [Modal Dialog](<https://wiki.soroush.uk/topic/modal-dialog/>)
- [Progressive Disclosure](<https://wiki.soroush.uk/topic/progressive-disclosure/>)
- [Responsive Design](<https://wiki.soroush.uk/topic/responsive-design/>)
