Stay organized with collections
Save and categorize content based on your preferences.
Material 3 Expressive leans into shape language in a much more expansive and
meaningful way by utilizing flexible container shapes to apply rounding and
sharpening of corner radii to support shape morphing lists and button states.
The design system also introduces edge-hugging buttons as an ownable and iconic
design pattern for round devices on Wear OS.
Maintain UI element scaling
When designing layouts on a round screen, scrolling and non-scrolling
views each have unique requirements to maintain UI element scaling and preserve
a balanced layout and composition.
Scrolling views
For scrolling views, use percentages to define all top, bottom, and side
margins to avoid clipping and provide proportional scaling of elements.
All top, bottom, and side margins should be defined in percentages to avoid
clipping and provide proportional scaling of elements.
Non-scrolling views
For non-scrolling views, use percentages and vertical constraints for all
margins. That way, the main content in the middle can stretch to fill the
available area.
All margins should be defined in percentages and vertical constraints should be
defined such that the main content in the middle can stretch to fill the
available area.
Tiers of quality guidelines
Our quality guidelines are organized into three tiers. Enable the best possible
experience for your users by meeting guidelines in all three tiers.
Ready for all screen sizes
Ensure your app is delivering a quality experience across all screen sizes.
Create layouts that fully use the available app space.
Responsive and optimized
Deliver more content to users on devices which allow for it, and utilize
responsive layouts that automatically adapt to different screen sizes.
Adaptive and differentiated
Make the most of additional real estate by utilizing breakpoints to offer
powerful new experiences on larger screens which are not possible on devices
with smaller screens.
Content and code samples on this page are subject to the licenses described in the Content License. Java and OpenJDK are trademarks or registered trademarks of Oracle and/or its affiliates.
Last updated 2025-07-22 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-07-22 UTC."],[],[],null,["# Design quality tiers\n\nMaterial 3 Expressive leans into shape language in a much more expansive and\nmeaningful way by utilizing flexible container shapes to apply rounding and\nsharpening of corner radii to support shape morphing lists and button states.\nThe design system also introduces edge-hugging buttons as an ownable and iconic\ndesign pattern for round devices on Wear OS.\n\nMaintain UI element scaling\n---------------------------\n\nWhen designing layouts on a round screen, scrolling and non-scrolling\nviews each have unique requirements to maintain UI element scaling and preserve\na balanced layout and composition.\n\n\n**Scrolling views**\n\nFor scrolling views, use percentages to define all top, bottom, and side\nmargins to avoid clipping and provide proportional scaling of elements.\n\nAll top, bottom, and side margins should be defined in percentages to avoid\nclipping and provide proportional scaling of elements. \n**Non-scrolling views**\n\nFor non-scrolling views, use percentages and vertical constraints for all\nmargins. That way, the main content in the middle can stretch to fill the\navailable area.\n\nAll margins should be defined in percentages and vertical constraints should be\ndefined such that the main content in the middle can stretch to fill the\navailable area.\n\n\u003cbr /\u003e\n\nTiers of quality guidelines\n---------------------------\n\nOur quality guidelines are organized into three tiers. Enable the best possible\nexperience for your users by meeting guidelines in all three tiers.\n\n\n**Ready for all screen sizes**\n\nEnsure your app is delivering a quality experience across all screen sizes.\nCreate layouts that fully use the available app space. \n\n**Responsive and optimized**\n\nDeliver more content to users on devices which allow for it, and utilize\nresponsive layouts that automatically adapt to different screen sizes. \n\n**Adaptive and differentiated**\n\nMake the most of additional real estate by utilizing breakpoints to offer\npowerful new experiences on larger screens which are not possible on devices\nwith smaller screens.\n\n\u003cbr /\u003e\n\n| **Caution:** A larger display size should *never* display less information than ones that are smaller than it, this is especially relevant for custom behaviors added in at the breakpoint. A common example of this is when components or text sizes are increased past the breakpoint and end up showing less are the larger screens. Screens should always show \"more value\" and never \"less value\" with increasing size."]]
