How easy is it to draw on GoogleMaps using Compose?

What are we allowed to draw on a Google Map using Jetpack Compose?
How easy is it to draw Markers?
And what about customising them? ✅
Clustering? ✅
Lines? ✅
Paths? ✅
Anything else? ✅
In this talk, I show how to, and how easy it is, from easy to quite hard, to draw above a Google Map instance using Jetpack Compose.

Engineering a Design System

Our designers decided to use a design system.
What is a design system? How can it help speed up the design and the development of a mobile application?
We have to align the entire application to that design system, build re-usable components which will speed the development time up without creating too many issues, avoiding code repetition and creating something that our designers can check and interact with before the features using the designs are shipped.
A design system uses components, and that's where we started from. We decided to mimic the idea of `widgets` from Flutter. We had to engineer our system in a way that allowed us to create small enough (but not too atomic) components, re-usable, avoiding making them too big and complex (hard to read and understand, hard to refactor, etc..).
The decisions, how we made them (team effort - with all the suggestions, opinions and conversations we had to come to a solution) and how we are now using them to speed up the development of our app.
What problem we faced, how we solved them, how this impacted our development speed and approach over the weeks (and how it will impact us in the future).

How we 🛠 engineered our 🧑🏼‍🎨 design system

MVI with Jetpack Compose

A little intro on how Jetpack Compose will help us get the best out of MVI architecture in the Android world.

A brief intro to MVI, a little intro on Jetpack Compose and an overview on how we could merge them all together to benefit from the best of both of them

White labelling with Jetpack Compose

Whitelabelling an Android app is not easy. Your skeleton should be easily and quickly customisable to align with your client(s) needs.
Jetpack compose introduced a new way of defining our UI. We don't have classes anymore, we can't rely on inheritance anymore, so we can't have customisation based on child classes.
Jetpack compose also introduced a new way to inject things in UI (`Local[AAA].current`).
I'll show how you can create a specific product for a specific client in no time thanks to a specific system allowing you to inject customisation(s) in Jetpack Compose.

White labelling has never been so easy thanks to Jetpack Compose. No technical requirement, apart from a base knowledge of Jetpack Compose. Target audience: everyone interested in customisation of products built with Jetpack Compose UI. Preferred duration: 40 minutes.