Often, when writing Compose code, we need to interact with code that does not support Compose. One sample of those it could be the Google Maps SDK, which does not provide out-of-the-box support for Compose. The Android Maps Compose library was written to overcome this limitation. In this session, we will explain some of the techniques used to develop android-maps-compose, and provide a Compose interface for a library that did not originally support it. You'll learn how we leveraged interoperability techniques, such as the Android View bridge, to wrap non-Compose components, manage their lifecycles safely within Compose, and expose idiomatic, composable APIs to end users. Whether you're looking to wrap legacy UI code or offer a modern Compose interface on top of a traditional Android library, this talk will provide you with practical tools, design patterns, and architectural considerations to help you “composify” just about anything.
Kikoso Google Developer Expert
Ideally the audience should have experience with Android Maps already, and Compose, to understand the techniques applied.
Challenges and Lessons from Flutter to Native – The Journey from a 1.6 to 4.0 Rating
Ryo Kitamura, kentaro fujii
#Development Process
What We’ve Done to (Plan to) Migrate from Navigation 2 to 3
yokomii
#Jetpack
Let’s Build an Editor for Vertical Text with Android 16 and Jetpack Compose
rokuroku
#Android Platform
© 2014- DroidKaigi Committee