Overall, my experience has been pretty smooth. Just look at how little platform specific code is found in the streetcomplete repo and how straightforward these connect with the common code.

Or maybe I have been using it too long so that I don't notice the awkward bits anymore.

Any specific parts you are after?

I've been building https://maplibre.org/maplibre-compose/ in my spare time for the past two years and helped with this port; happy to answer any questions you have about KMP or CMP

Generally, I'm very happy with the platform and it's only gotten better over the past couple years I've been deep in it.

Yes, to be more specific, every tool like this has benefits offered and then taxes to be considered. For example, what's the tax for:

- Maintaining a significant new moving part in the dev process. KMP updates, management, integration, futures awareness, this all takes non-zero time.

- If an iOS dev wants to work on a KMP project what's the ramp up time? How much less efficiently can they contribute compared to a pure native app?

- How much time is spent on problems, bugs, issues, related to KMP. This is guaranteed non-zero for any tool.

- Is there less benefit to KMP with coding agents? Previously with two native apps, a bug fix had to be done twice. Currently, say a fix in done on Android, it's quite easy to say "propose an equivalent fix for the iOS repo". I do not claim this removes all benefits of a single code base, just that some things are not as bad now.