material-components / material-components/material-components-android

[Sample] Request: update sample to better demonstrate website material design samples

Open
#4,251 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature request Issue: Catalog
Dominant language
Java
Stars
17.4k
Forks
3.2k
PR merge metrics
No merged PRs in 30d

Description

**Is your feature request related to a problem? Please describe.**
Yes, there is a huge gap between what's shown on the material design guidelines of what's possible and beautiful examples, vs what's shown here (which can be complicated yet still not the same):
https://m2.material.io/components?platform=android
https://github.com/material-components/material-components-android/tree/master/catalog

**Describe the solution you'd like**
For each screenshot and animation on the website, actually show how you did it, meaning have a link on the official website to the sample/file to reach, so that each time we see something nice, we could reach it and learn from it, how it's recommended to use it.
What's the point in demonstrating things of a library, yet not showing the source of how you did it...
I'm sure the same thing is true for the other platforms and frameworks too.

**Describe alternatives you've considered**
Some things can be done easily, and I personally prefer minimal examples first, but here we didn't get minimal ones AND what's shown on the official website.

**Additional context**
Example is of Bottom sheet:
https://m2.material.io/components/sheets-bottom#behavior

Compare this bottom sheet which has a FAB at the top, and gets disappeared when expanding, taking full screen:
[Bottom sheets full screen.zip](https://github.com/user-attachments/files/16478753/Bottom.sheets.full.screen.zip)

With this sample we have:
[scrcpy_2024-08-03_12-37-39.zip](https://github.com/user-attachments/files/16478958/scrcpy_2024-08-03_12-37-39.zip)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by comparing the linked Material Design bottom-sheet example, the existing sample referenced in the issue, and the Material Components catalog. No repository file or test is named, so the implementation entry point must first be identified. Done would require an agreed scope and links from the website to source samples for the showcased screenshots and animations.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, java
Domain
design, documentation, mobile
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.