docs: Material 3 Expressive + advanced Nav 3 patterns - #17
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Two coverage gaps, confirmed by surveying the reference files (and echoed by
r/androiddev demand for M3 Expressive examples):
theming-material3.mdhad zeroExpressive content;
material3-motion.mdmentionedMotionScheme.expressive()only in passing.
problems (results, auth-gating, transitions, adaptive list-detail, multiple
back stacks) weren't covered.
Changes (3 existing files expanded — no new files)
theming-material3.md→## Material 3 Expressive:MaterialExpressiveTheme, the@ExperimentalMaterial3ExpressiveApiopt-in,and the expressive component family (
ButtonGroup,SplitButton,FloatingActionButtonMenu/ToggleFloatingActionButton,LoadingIndicator,HorizontalFloatingToolbar), expressive shape/type, plus an anti-pattern.material3-motion.md→## Expressive motion: spatial-vs-effects underthe expressive scheme, why the components need
MaterialExpressiveTheme, areview flag for wobbling fades.
navigation-migration.md→## Advanced Nav 3 patterns: returningresults, auth-gated navigation, animated/shared-element transitions in
NavDisplay, adaptive list-detail (NavigableListDetailPaneScaffold), andper-tab back stacks.
SKILL.md→ routing rows + trigger keywords so M3 Expressive / advancedNav 3 queries land on the right file.
Accuracy
Every new API verified against current androidx docs via context7. Because the
expressive component APIs are
@ExperimentalMaterial3ExpressiveApiand theirexact parameter lists shift across
compose-bomalphas, each signature is shownas shape with an explicit "verify against your BOM" note — the verified opt-in
annotation and concepts are stated as fact; unverifiable exact params are not
asserted. Nav 3 advanced APIs (
NavDisplayshared-transition scope,NavigableListDetailPaneScaffold,LocalNavAnimatedContentScope) are verified.Verification
check-description-length.sh→ 843/1024 (frontmatter untouched).validate-plugin-manifest.sh→ valid.Content-only; independent of the verify-claims CI work (PR #16). Minor version
bump at release time.