microsoft / microsoft/AdaptiveCards
[Android][Performance] Reduce the number of empty views generated
Open
Nobody has claimed this yet.
Area-Performance
Platform-Android
- Dominant language
- C#
- Stars
- 2k
- Forks
- 595
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 1
Description
Platform
- Android
Author or host
dev
Version of SDK
main
Details
Elements such as containers or columns generate a lot of empty views (such as linear layouts) that the rendering performance as well as the debuggability of issues with this elements.
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 Android rendering paths for containers and columns, then inspect how their empty views are generated. Measure the current view count and rendering behavior; done means reducing unnecessary empty views without breaking card rendering or debuggability.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android
- Domain
- mobile, performance
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100