Making Large Screens Easier in Compose
summary
The talk examines when stateful UI components can be preferable to state hoisting in Jetpack Compose, showing on complex screens how keeping state inside components can simplify development. It presents a practical method for implementing stateful Compose components in large projects that use an API/Impl architecture, dependency injection, and need fast build times, enabling reusable UI components while fitting into DI and API/Impl constraints.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:29Talk overview
- 3:22Static vs dynamic UI components
- 5:30Video feature requirements
- 6:34Stateful approach
- 9:46Stateful vs stateless
- 12:15Stateful component issues
- 14:21DI issues in UI module
- 17:10UI module solution
- 18:39Utility function
- 23:20Factory in provider
- 25:58ViewModel parameters
- 27:03Summary
- 28:49Closing
- 29:11Q&A
related talks
39mRe-Compose your UI: building an atomic design library
31mDesigning Media Friendly Jetpack Compose Components
21mGaining Composure
42mJetpack Compose: Art of the State
38mDesigning scalable Compose APIs
49mBuilding an Android UI using declarative programming in Jetpack Compose
18mCompose: Implementing responsive UI for larger screens
44mUnleashing the Power of Jetpack Compose: Revolutionizing Android UI Development
