4 ms·

I developed on Android in ~'11 and it was a mess then. Again in ~'17 and it was... also a mess. There seems to be something fundamentally wrong with it that re

I developed on Android in ~'11 and it was a mess then. Again in ~'17 and it was... also a mess. There seems to be something fundamentally wrong with it that resists change. Plus in some cases Google simply doesn't seem to give a shit about the platform, letting it lag behind JS versions of their service SDKs for fairly basic functionality, or announcing big UI overhauls but then severely half-assing the developer-facing side of those features.

pas 5y ago
Well, it's a walled garden. Half of it locked down in the name of security. (While "free VPN"[0] apps steal your data while you play 30 seconds of some "game".) The other half is for performance and "consistent user experience" reasons. Oh, the remaining is just the battery saver killing everything for good measure. The docs are shit. The IDE is okay, but the build system, tooling, emulator and everything provided by Google (Flutter stuff! Flutter web!) always turns out to be just a bunch of interdependent unfinished binary blobs with a laughably DIY "installer". Sure, devs get used to it fast and can be productive in no time. But it's ridiculous how much hoops they invent out of sheer corporate-ness. (Importing projects? Nah, it never works on the first time. Upgrading projects? That basically only works if you recently sacrificed someone's firstborn. Adding some 3rd party library and getting the build system and the IDE work without spending hours fighting them? I hope you started this journey with two kidneys.) [0] I just made it up, but wouldn't be surprised if someone does that