TIDAL App with Jetpack Compose
summary
TIDAL’s homepage is rewritten using Jetpack Compose and a clean repository architecture in three months, shrinking roughly 29 modules to three types (horizontal, vertical, grid). Implementation uses design-system components, previews, snapshot and end-to-end tests, feature flags, and baseline profiles to cut JIT and frame drops. Workarounds include replacing Subcompose for initials, opting into Material3 behavior for collapsing app bar, and handling missing autosize text and nested lazy lists. Early metrics show ~90% user satisfaction and faster time-to-play.
AI-written summary · about
chapters (21)
- 0:00TIDAL’s Jetpack Compose journey
- 1:29Rebuilt homepage from scratch
- 4:43Jetpack Compose vs incremental improvements
- 6:29Old architecture limitations
- 9:17New clean architecture with Compose
- 10:21Jetpack Compose productivity boost
- 11:48Faster iteration with Compose previews
- 13:55Reusable Compose components
- 14:15Legacy API compatibility challenges
- 16:20Cross-platform alignment with iOS
- 17:44Performance issues and optimization steps
- 19:51Fixing UI lags with baseline profiles
- 21:16Testing Jetpack Compose UI
- 24:30Snapshot testing design system
- 25:54Maintaining Compose code best practices
- 27:19Adopting Compose in teams
- 28:40UX improvements with Compose
- 30:23Device support and responsiveness
- 32:11Development speed and future plans
- 33:13Feature flags and performance
- 34:39Closing remarks and resources
related talks
34mRetrofitting Legacy Code with Jetpack Compose at Scale
42mBranching out to Jetpack Compose
43mBranching out to Jetpack Compose
01h 08mAdopting Jetpack Compose @ Scale
39mA Design System, it Composes!
01h 12mJetpack Compose — live coding declarative UI
41mCompose by Example
35mNext Generation Android UI with Jetpack Compose