There are some questionable complaints in this blog post (I have not encountered the issue with separate layouts for different DPIs, for example), but it’s true

There are some questionable complaints in this blog post (I have not encountered the issue with separate layouts for different DPIs, for example), but it’s true that native Android development is frustrating on a semi-regular basis, with some of the most unexpected and random tasks posing more of a challenge than they have any right to. I frequently find myself wishing I could write Android apps with Swift and UIKit. They have their own warts, but the majority of difficulties you’ll face with them involve more advanced/less used SDKs… its base UI components work very well and mostly act as one would expect them to, especially with the improvements to UICollectionView/UITableView brought in iOS 13. Way fewer surprise NullPointerExceptions too thanks to Swift being a much cleaner break from Objective-C than Kotlin is from Java.