App Hang / ANR Rate per screen or activity
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 21h 10m
- Merged PRs (30d)
- 635
Description
### Problem Statement
As an overal rate is helpful, it would be more helpful if it would be possible to have rates per screen to figure out bottlenecks in specific parts of the application.
Customer is planning to implement these dashboards in Q1-2026.
"What can we expect about the delivery timeline for this feature?"
### Solution Brainstorm
_No response_
### Product Area
Unknown
Contributor guide
Research direction
No files, tests, or entry points are named. Start by locating the existing overall App Hang/ANR rate implementation and dashboard data, then determine how screen or activity dimensions are represented. Done means defining and delivering per-screen or per-activity rates, with the expected delivery timeline clarified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android
- Domain
- mobile-dev, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100