wordpress-mobile / wordpress-mobile/WordPress-Android
Reduce CardView use to avoid Overdraw
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 3.2k
- Forks
- 1.4k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 69
Description
Expected behavior
Replace the use of cardviews to avoid CPU-related performance problems
Actual behavior
There are several elements such as the website icon that contribute to overdrawing problems due to the use of CardViews.
Steps to reproduce the behavior
Changing the use of CardViews with transparent ConstraintLayouts allows you to achieve the same visual effect with much lower Overdrawing levels.
Tested on [device], Android [version], WPAndroid [version]
Tested on Motorola G6 play. Android 9.
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 CardView usages in the WordPress-Android screens that include elements such as the website icon, then inspect the current overdraw behavior on Android. Done means replacing the relevant CardViews while preserving the visual effect and achieving lower overdraw levels.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100