material-components / material-components/material-components-android
Material TV Components
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 17.4k
- Forks
- 3.2k
- PR merge metrics
- No merged PRs in 30d
Description
Jetpack Compose has a material library specifically for TV with Components that do not exist in standard xml based layouts
There is a Jetpack Compose library that has a lot of nice new TV UI components but are sadly missing and/or very difficult to create something similar when using standard xml based layouts in the material components library.
Specific examples of missing components are Immersive Lists, Featured Carousel and Navigation Drawer
Please add parity between the compose and xml libraries, in this case for TV components but parity all around would be great too
**Describe alternatives you've considered**
Immersive List could be recreated with several components but the implementation to talk between components would be complex.
For Featured Carousel there is a carousel component but there does not seem to be a way to show it like in the compose library.
Navigation Drawer exists but like the carousel there is no way to create one like in the jetpack library where there is a navigation rail that expands to a drawer.
**Additional context**
Components referenced by the documentation found here [here](https://developer.android.com/design/ui/tv/guides/components)
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 with the Android TV components documentation linked in the issue and compare the Compose components with the existing XML-based Material Components library. The requested scope includes Immersive Lists, Featured Carousel, and an expandable Navigation Drawer, but the issue also asks for broader parity; done would require an agreed component scope and matching XML implementations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- design, mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100