It is. It's really, really bad. Their platform overall is also a lot less... well, good, frankly. You end up bringing in third party libraries a lot for basic s

It is. It's really, really bad. Their platform overall is also a lot less... well, good, frankly. You end up bringing in third party libraries a lot for basic stuff if you don't want life to be a living hell of re-discovering reasons people don't use some of the built-in stuff, or stumbling over years-old hundred-comment bug reports that remain unresolved (you'll still hit some of those, just less frequently). Support for major Google features and initiatives often sucks—Material generally, and as of a couple years ago their Maps library was worse than the JS version in some important ways, such that you'd end up calling out to javascript if you needed something as little-used as, say, address components (rather than one big address string). Yes, seriously. This is a pattern for them. I don't get it, but that's the way it is. Android's not built on a great foundation, and sees a surprising amount of neglect and half-assery in its ongoing development.