Using Compose Runtime to create a client library
summary
Shows that Compose Runtime (not UI) can power non-Android clients by building a tiny Compose-based PowerPoint generator: compiler-injected Composer writes to the slot table, changes get batched and handed to a custom Applier implementation, and a simple compos node tree (Slide + Text) materializes to a .pptx via Apache POI. Client integration creates FrameClock and Recomposer, sets content, observes Snapshot writes, runs recompose/applyChanges and renders frames in a loop — the demo produces a single slide “hello stranger.”
AI-written summary · about
chapters (9)
- 0:00Introduction to Compose
- 2:58Compose compiler explained
- 5:27Compose runtime fundamentals
- 6:30Composer and slot table
- 11:30Applier and node tree
- 17:35Client integration basics
- 20:02Building PowerPoint client
- 34:30Using the client library
- 35:56Summary and key takeaways
related talks
28mUsing Compose Runtime to create a client library
36mUsing Compose Runtime to create a client library
40mThe Compose Runtime, Demystified
34mBeyond the UI: Compose as a Foundation for Multiplatform Apps
42mCompose: Beyond Android development
30mModern Compose Architecture with Circuit
36mCoupling Compose- Interoperability in a Legacy Codebase
41mCompose by Example