I'll probably never get over the fact that Google pushed Jetpack Compose on us and now I have to be constantly concerned with the performance of the UI layer.
Just ridiculous.
youtu.be/c3gdS42TJmI

An important software developer's skill is being able to tell which errors need to be handled, and which don't.
Utility apps and avionics have vastly different reliability requirements and, as a result, call for vastly different error handling strategies.

This aged like a fine wine.
So, is Kotlin Multiplatform the future?

Very interesting analysis of the effect of AI on selected source code metrics.
TL; DR; looks like we produce much more low-quality code now.

Large-scale research by GitClear shows significant changes in the code patterns committed in recent years after AI-assisted became a thing. There are several interesting insights.

Arpad Toth Guy Griv I think that most of the hate towards RecyclerView comes from the architectural mistake of baking ViewHolder pattern into its API.
A striking example of a harmful preliminary optimization that plagued the entire ecosystem for years.

Android devs, would you consider this use of ExoPlayer in Compose safe?

Did Google Play change the rules and will now suspend apps after several (3) rejections?
If you've encountered Google Play rejections lately, please share your experience in this discussion that attempts to gather real-world feedback 🙏
reddit.com/r/androiddev/c…

I'm not good at resumes and rarely give advice in this context, but this is a good example of many common mistakes, so I provided some feedback:
reddit.com/r/android_devs…

New post about the challenges of Bottom Bar Navigation implementation using Jetpack Compose and Compose Navigation.

techyourchance.com/bottom-bar-nav…

I thought that Google will lose interest in Kotlin Multiplatform after they won in the Oracle's lawsuit. However, the recent announcements of KMP support in ViewModel and Room suggest that I might've been wrong.
Is KMP the future of mobile development?

A student asked whether my recommendation to avoid the Repository pattern should also apply to e.g. Room DAO objects becaues they can contain many different methods to perform CRUD operations.
My answer 👇