Thanks for the invitation, it was a pleasure to give my conference at the Paug meetup, discuss with the android engineers from paris and troll a little 🤏

For me, it is always stressful at the beginning because you think you don't have enough to say and at the end because you have too many things to say.. 😅

Pose toi plutôt la question : Pourquoi rester sur X ? :)

On est heureux de pouvoir soutenir les projets open source que nous utilisons !

Conclusion: Fleet shows potential and could become a strong alternative to AS. For now, we still need to switch between three IDEs: AS for Android-specific tasks, Xcode for iOS-specific tasks, and Fleet for KMP.

This is probably an essential point to work on to improve the developer experience.

Plugins: Currently, plugins aren’t supported, which makes it impossible to work with SQLDelight (from my opinion, a key library in the KMP ecosystem) or to use GitHub Copilot. While JetBrains AI is available, I find it less relevant for my needs compared to Copilot.

Previews are quite basic. I haven’t found a way to inspect outlines for internal components, interact with them, or view animation previews, and I suspect there may be additional limitations.

Less productivity: Fleet makes development feel slower. It does nothing to help create source sets, Kotlin files, and detects automatic imports after copy-paste. It also seems like the autocomplete is much slower.

I was in the room during the demo made by @tornorbye.bsky.social and even if technically, it is very impressible, I've still so many questions.

Mainly: how do we make sure that the results are reproducible from one run to another, using the same model or a new one? And how to debug tests run by AI?