Kotlin and Compose WASM for the UI challenged
summary
Claim: Kotlin Multiplatform plus Compose for Web (WASM with JS fallback) lets one write a single UI shared across Android iOS desktop and web, with Material Theme Builder producing accessible components. Tools shown: WASM, WASI, Cloudflare deployment, npm interop and Gradle build. Caveats: web beta status, not recommended for large public sites because binary size can hit ~2 MB for simple apps and Safari history delayed adoption. A demo is prepared but not run; concept works for internal high‑performance apps.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 0:41UI challenges for Java devs
- 1:48Kotlin Multiplatform & Compose for web
- 3:11What is Kotlin Multiplatform
- 4:39Web frontend tech cycles
- 7:11Evolution of web frontends
- 11:05Compose for Java devs
- 12:52Context switching in frontend
- 14:17WebAssembly advantages
- 15:45Compose & WASM synergy
- 16:52Material theme builder
- 18:21Type-safe UI components
- 19:07WebAssembly backend
- 20:11When not to use WASM
- 21:38Kotlin Compose for web beta
- 22:20Why adopt Kotlin & Compose
- 23:23Use cases & limitations
- 24:04Closing & demo
related talks
45mThe Adventures of Kotlin And Compose Through the Multiplatform World
33mBuilding modern web apps with Kotlin and WebAssembly
42mKeynote: Kotlin and the Multiplatform Future
31mIntroducing Kotlin/Wasm
45mAn Android, a Desktop, and a web developer enter in a bar
58mMultiplatform UI: Compose outside Android
41mIt Just Works
44mThe Adventures of Kotlin & Compose Through the Multiplatform World
