Components
Material 3 component guides backed by the same m3-ui implementation and canonical token graph.
Component guides
These pages document the public React API through the Material contract: family, variants, states, accessibility, Compose mapping, and intentional web adaptations.
For a single data-driven view of those contracts, sources, mappings, and web adaptations, see the Parity catalog.
Actions
- Button — five Material button variants plus expressive sizes and interaction states.
- Toggle button — controlled filled, elevated, tonal, and outlined pressable toggles with expressive sizes.
- Icon button — action and toggle families across audited variants, sizes, widths, and shapes.
- FAB — icon-only and extended floating actions, audited sizes/elevation, and explicit cross-source compatibility variants.
- Floating action button menu — controlled expandable FAB actions with focus transfer, staggered reveal, and toggle-FAB geometry.
- Chip — assist, suggestion, filter, and input chip families with action versus selection semantics kept distinct.
Input and surfaces
- Text field — filled, outlined, secure, and multiline fields with supporting content, validation, and native input behavior.
- Surface — passive or explicitly interactive Material containers with tonal/shadow elevation and role-aware state semantics.
- Card — filled, elevated, and outlined surfaces with an explicit semantic-role boundary for interactive cards.
- Dialog — Material modal composition, scrim, actions, theme portals, and focus semantics.
- Scrim — passive or dismissible obscuring layers that leave modal lifecycle and stacking to their owner.
- Bottom sheets — local non-modal and true modal sheets sharing one Material anchor-state contract.
- Lists and list items — passive, action, single-radio, and multiple-checkbox rows with one-, two-, or three-line Material geometry.
- Menus — anchored menus, sections, items, and a read-only exposed-menu form with React Aria focus semantics.
- Badges — dot/content badge geometry plus explicit application-owned accessible status wording.
- Dividers — horizontal and vertical semantic separators with token-backed Material defaults.
App bars and toolbars
- Top app bar — small, centered, medium, large, and flexible variants with explicit scroll-state inputs.
- Bottom app bar — regular/flexible action bars, optional FAB composition, and app-owned exit-always state.
- Floating toolbar — horizontal/vertical expressive toolbars with standard/vibrant roles, explicit expansion, FAB placement, and RTL-aware exit translation.
- App bar row — inline-axis action layout with local width measurement and accessible overflow.
- App bar column — block-axis action layout with local height measurement and accessible overflow.
Selection controls
- Checkbox — checked, unchecked, indeterminate, disabled, and interaction states.
- Radio button — single-selection groups, labels, validation, and keyboard semantics.
- Switch — on/off state, optional thumb content, disabled treatment, and theme focus indication.
- Slider — single and range values, audited sizes, accessible thumbs, and explicit web adaptations for ticks and value indicators.
Pickers
- Date pickers — single/range calendar selection, native date-input mode, timezone-free ISO state, and explicit dialog composition.
- Time pickers — dial and keyboard input sharing normalized time state, 12/24-hour presentation, and component-local orientation switching.
Grouped controls
- Tabs — primary/secondary tab lists, fixed or scrollable presentation, and application-owned panel content.
- Segmented buttons — single-choice radio semantics and multi-choice checkbox semantics kept distinct.
- Split button — independent leading/trailing actions with disclosure or toggle state while menu content remains application-owned.
- Button group — standard action groups with local overflow plus connected single/multiple selection groups.
Browsing and feedback
- Carousels — multi-browse, uncontained, and centered-hero arrangements with focal geometry and explicit state.
- Search bar — collapsed search input with docked or full-screen expanded surfaces and an application-owned data boundary.
- Progress indicators — standard and M3 Expressive wavy progress with determinate, indeterminate, and explicit Web compatibility behavior.
- Loading indicator — expressive Material shape morphing in contained and uncontained forms.
- Snackbar — transient-message surface, live-region semantics, actions, and an explicit host/timeout boundary.
- Tooltips — plain tooltip semantics kept distinct from interactive rich-tooltip dialog semantics.
Compose Material utilities
These APIs are part of AndroidX Compose Material3 even when they do not have a dedicated component family page on m3.material.io. Their parity cards therefore link directly to the authoritative Android Developers API reference.
- Pull to refresh — top-boundary pull gestures with app-controlled refresh lifecycle and an overridable indicator slot.
- Swipe to dismiss — logical start/end dismissal anchors, foreground interaction preservation, and RTL-aware pointer settling.
- Scroll field — wheel, drag, click, and keyboard selection exposed as an accessible spinbutton value.
- Vertical drag handle — Material resize affordance and interaction feedback with resize state/semantics owned by the surrounding composition.
- Non-interactive scrollbar — visual-only scroll position feedback that observes native or adapted scrollers without becoming another control.
Documentation rule
A component page should describe behavior that exists in @m3-ui/ui; it must not become a second implementation of the component. Live previews use the public package, and Material measurements remain sourced from canonical generated tokens rather than documentation CSS literals.
Cross-source compatibility APIs are labeled as such instead of being presented as Compose-only Material contracts.
Layout boundary
Component documentation does not define adaptive window classes, pane directives, navigation switching, or scaffold behavior. Layout documentation will consume the dedicated @m3-ui/ui/layout subsystem instead of creating a docs-only responsive model.