material-components / material-components/material-components-android
[Material Motion] Add predictive back support for MaterialContainerTransform
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 17.4k
- Forks
- 3.2k
- PR merge metrics
- No merged PRs in 30d
Description
Predictive Back is fully supported in AndroidX Transitions and [Fragments](https://developer.android.com/guide/navigation/custom-back/support-animations#fragments). The default MaterialContainerTransform transition should support predictive back.
Ideally, the transition would follow the Predictive Back [design spec](https://developer.android.com/design/ui/mobile/guides/patterns/predictive-back).
Related: https://github.com/material-components/material-components-android/issues/3619
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the MaterialContainerTransform entry point and reviewing AndroidX Transitions and Fragments predictive-back support. Compare the requested behavior with the linked predictive-back design specification and related issue 3619. Done means the default transition supports predictive back and follows the referenced design guidance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- mobile-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100