material-components / material-components/material-components-android
[Performance] Include a baseline profile
Nobody has claimed this yet.
- 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.**
Baseline profiles can significantly decrease jank, which is especially important for UI components that are included at the app level (vs in the framework).
**Describe the solution you'd like**
Add a baseline profile to this library so critical paths can be precompiled (AOT) during install
**Describe alternatives you've considered**
N/A
**Additional context**
https://developer.android.com/topic/performance/baselineprofiles/overview
We also happily accept [pull requests](https://github.com/material-components/material-components-android/pulls).
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 linked Android baseline profiles overview, then inspect this library's Android build configuration and module structure to determine where a profile belongs. Done means the library includes a baseline profile that covers its critical paths and can be used for AOT precompilation during installation; no specific files or tests are named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- mobile, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100