[1] It is evident by the fact that Google is still trying to fix the fundamentals like permissions, updates etc. Android is essentially what you get when you try to cram an OS primarily used on servers and high end workstations on a mobile phone and pair it with a programming environment which is also used primarily used on servers by implementing a quick and dirty runtime from scratch.
I'd ask you to cite some examples of why Android is a "low bar to clear", but I doubt I'd get back anything of substance.
>Android was, and remains, a Frankenstein’s monster[1] which was hastily cobbled together at Google to capitalise on the new marked created by the iPhone before MS could lock them out of it.
Could you point to the Android github examples that support your claims that Android is a Frankenstein’s monster which was hastily cobbled together? You see, that's the nice thing about being an open source OS - you can actually see the source code and call out people for making ridiculous comments about things they have no idea of what they're talking about.
>In fact, if MS had brought WP 8 sometime in 2010, the story would be a lot different.
No it wouldn't have. It would have played out exactly the way it did.
Starting with Eclipse, then rebooting the whole development environment just because some management guys happened to be InteliJ users.
Several years later there are still Eclipse based tools, like the graphical manifest editor, that haven't been replicated in Studio.
NDK is treated as a 20% project, done by an handfull of engineers.
Devs were left in the cold when the migration away from Eclipse was decided. It was only due to the coincidence of Clion being developed, that Studio eventually got C++ support.
The amount of cruft on NDK build tools is a joke, already with 4 official variations.
The decision to use Gradle has made "how to optimize builds" a recorrent topic in any major Android conference.
Google teams like Android development build tools so much that they rather use blaze, throwing yet another build tool into the mix.
There isn't a single release of Android Studio or the Support Library, that isn't followed by bug related complaints on online forums, despite being several weeks, months, in testing phase.
Their initial emulator implementations was so lousy, that it required the public shame of Genymotion and Microsoft doing a better job for Google actually improving theirs.
There was so much more to rant about, but this is already quite long.
The pain of Windows phone development was significantly worse especially when you consider they kept on changing it every year because of their inferior development environment and tooling.
>Starting with Eclipse, then rebooting the whole development environment just because some management guys happened to be InteliJ users.
Google switched IDE's. Microsoft changed their development environment and tooling each time they decided to osbourne their still born OS.
>NDK is treated as a 20% project, done by an handfull of engineers.
Well, at least they stuck with it instead of chucking it to the curb each year and starting over.
>Devs were left in the cold when the migration away from Eclipse was decided. It was only due to the coincidence of Clion being developed, that Studio eventually got C++ support.
Isn't being left in the cold an annual event for Windows phone developers?
>The decision to use Gradle has made "how to optimize builds" a recorrent topic in any major Android conference.
This is in contrast to the Windows phone .build conference where there were no sessions because no one was building Windows phone apps.
>Google teams like Android development build tools so much that they rather use blaze, throwing yet another build tool into the mix.
Isn't choice good.
>There isn't a single release of Android Studio or the Support Library, that isn't followed by bug related complaints on online forums, despite being several weeks, months, in testing phase.
Because XCode and Visual Studio are bug free when new versions are released, right? Oh wait.
>Their initial emulator implementations was so lousy, that it required the public shame of Genymotion and Microsoft doing a better job for Google actually improving theirs.
Google has to support 3 platforms unlike Microsoft who couldn't even support 1.
Manufacturers can do mostly what they want without any downsides so at the end you just end up with ROMs similar in quality to WinXP themes. The Android APIs themselves are just layer and layer of hacks and inconsistencies on top of each other which is the main reason why most of the Android apps look so ugly in the first place.
No they can't. They need to pass the CTS and VTS.
>so at the end you just end up with ROMs similar in quality to WinXP themes.
When was the last time you saw an Android phone? 2008? Name those WinXP themed OEM skins.
>The Android APIs themselves are just layer and layer of hacks and inconsistencies on top of each other
Considering all of the bugs and security issues iOS has had I would have to give that award to iOS.
>which is the main reason why most of the Android apps look so ugly in the first place.
Not only do Android apps look better, but they also take up considerably less space than their bloated iOS counterparts.
