Android Scrolling Performance Optimization

My Android codebase is showing painful jank on high-end phones. I’ll hand over the full Git repo together with a short list of flagship devices where the problem is easiest to reproduce. What I need from you is a disciplined, measurement-driven optimisation round focused first on scrolling smoothness, without neglecting startup delay and battery cost once the core issue is uncovered.

You’ll profile with the usual Android Studio tools—CPU/Memory profiler, Profileable build variants, Systrace/Perfetto, and any frame-time overlays you prefer—so that every claim about a fix is backed by numbers. Before touching a single line, capture baseline metrics (FPS, frame-drop %, jank %, time to first frame, and a 15-minute battery drain sample). After you refactor, re-run exactly the same traces and highlight the delta.

Please document the hotspots you find (slow ViewBinding, heavy overdraw, main-thread I/O, shader compilations—whatever they turn out to be) and annotate the pull request with code comments that explain why each change works. A short “guard-rails” section describing patterns to avoid in future commits is also required so the team can keep regressions out of CI.

Deliverables:
• Baseline & post-fix trace files and screenshots
• Git-based patch or pull request with optimisations clearly segmented
• Markdown report summarising findings, metric improvements, and prevention guidelines

Acceptance criteria:
• Scrolling jank below 2 % across the supplied devices, verified with Perfetto
• No regression in startup time (>5 % tolerance) or battery drain (>3 % tolerance)
• All code changes build cleanly on the current CI pipeline

If you’ve tamed RecyclerView or Compose performance issues before and can quantify the win, I’d love to see a brief example when you bid.