Skip to content

docs: Material 3 Expressive + advanced Nav 3 patterns - #17

Merged
aldefy merged 2 commits into
masterfrom
feat/m3-expressive-nav3-advanced
Jul 8, 2026
Merged

docs: Material 3 Expressive + advanced Nav 3 patterns#17
aldefy merged 2 commits into
masterfrom
feat/m3-expressive-nav3-advanced

Conversation

@aldefy

@aldefy aldefy commented Jul 8, 2026

Copy link
Copy Markdown
Owner

Why

Two coverage gaps, confirmed by surveying the reference files (and echoed by
r/androiddev demand for M3 Expressive examples):

  1. M3 Expressive was nearly absenttheming-material3.md had zero
    Expressive content; material3-motion.md mentioned MotionScheme.expressive()
    only in passing.
  2. Advanced Nav 3 was missing — migration basics were solid, but the hard
    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 @ExperimentalMaterial3ExpressiveApi opt-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 under
    the expressive scheme, why the components need MaterialExpressiveTheme, a
    review flag for wobbling fades.
  • navigation-migration.md## Advanced Nav 3 patterns: returning
    results, auth-gated navigation, animated/shared-element transitions in
    NavDisplay, adaptive list-detail (NavigableListDetailPaneScaffold), and
    per-tab back stacks.
  • SKILL.md → routing rows + trigger keywords so M3 Expressive / advanced
    Nav 3 queries land on the right file.

Accuracy

Every new API verified against current androidx docs via context7. Because the
expressive component APIs are @ExperimentalMaterial3ExpressiveApi and their
exact parameter lists shift across compose-bom alphas, each signature is shown
as 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 (NavDisplay shared-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.

@aldefy
aldefy merged commit 4979f7c into master Jul 8, 2026
1 check passed
@aldefy
aldefy deleted the feat/m3-expressive-nav3-advanced branch July 8, 2026 07:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant