Akshay Chordiya

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?

Forms are at the core of many user experiences—from onboarding to payments—but building scalable, and reusable form UIs comes with unique challenges. In this talk, I’ll take you behind the scenes of our journey from repeatedly rebuilding similar form screens, it's business layer to building a reusable form architecture that balances dynamic UI rendering, validation, and state management effectively. Through real-world implementation details, we’ll discuss: • Our Journey with Forms & Why We Built This •⁠ How we built a Dynamic Form System with Compose •⁠ ⁠State Management & UDF in Forms: Balancing immutability, Compose state holders, and Flow for efficient reactivity. •⁠ Validation & Navigation: Ensuring a seamless user experience with dynamic validation & navigation. •⁠ ⁠Extensibility & Reusability: How to allow different teams to swap out repositories while using shared UI & logic to build their form UI •⁠ ⁠Lessons Learned: Performance optimisations, API design pitfalls, and Compose-specific challenges. By the end of this talk, you’ll have a blueprint for designing a scalable, reusable form system—one that makes it easier to build forms that are composable, testable, and adaptable to different use cases. 🚀