Compose UI unlocks rapid development and powerful UIs for Android—but performance can quickly become a stumbling block. Diagnosing jank, picking the right tools, and deciding where to optimize are often harder than writing the UI itself. In this roundtable, we’ll discuss real-world strategies for spotting and fixing performance issues in Compose, from tooling and debugging workflows to design trade-offs and team practices. Bring your stories of sluggish apps, clever optimizations, and lessons learned to help build a shared “runbook” for smoother Compose performance.

Kick-off questions:

> What’s the most common cause of sluggish performance you’ve seen in Compose apps?
> Which tools have you found most reliable (or most frustrating) when diagnosing performance issues?
> How do you balance clean, maintainable Compose code with the need for fine-grained performance tuning?
> Have you had to build your own custom strategies or components to improve Compose performance?
> If you could give just one piece of advice to a team starting with Compose today, what would it be to avoid jank later?