Not many Android devs have a confident performance measuring pipeline. They don’t have an accurate way to catch performance regressions.
This is the most usual reason to start over optimizing or optimizing the wrong places.
I highly recommend taking a look at Macrobenchmarks.
Hi, I’m Earl
I’m a Mobile Developer crafting apps for iOS and Android.
I partner with teams to transform concepts into intuitive, high-performing mobile experiences.
Beyond coding, I collaborate closely to iterate and launch products that users love.
Need assistance or Roles DM
1. Create Android app using Jetpack ViewModel, Navigation 3, Room, DataStore for example (all support KMP)
2. Use Compose Multiplatform from the start
3. Enjoy your free iOS app!
4. Profit 😀
Maybe not quite as straightforward as that yet (Nav3 not quite there) but not far off!