auxio

baka-dubbs said:

I think people are missing the point of a "Hot Take".  A hot take sets out to be "deliberatively provocative or sensational".  IE, the whole thing is to get fanboys arguing one way or the other, which apparently mission accomplished...

Sad how shallow the world has become, isn't it? Where is the space to have in depth debate with well thought out and researched ideas these days anyways?

avon b7 said:

Personally I much prefer Android but Android comes in infinitely more flavors than iOS so it's impossible to have used them all to any real degree. The same applies to iOS and the changes from one versión to another.

I'd say that over recent years, iOS has taken a huge amount of influence from Android. Although it is a two way street, it definitely looks like Apple is loosening it's grip on key areas like personalisation.

For me, as someone who constantly has to dip into iOS to resolve issues, it can be very frustrating to see how some things seem so kludgy there. 

That could be due to my wife's particular situation/configuration or how certain apps 'behave' but it doesn't feel intuitive to me. 

From an application developer perspective (both Android and iOS), Android's technology stack is a mess compared to iOS. They put Kotlin on top of Java, which is basically just syntax sugar coating (Java was already a pretty high level language). Java has zero direct interoperability with native programming languages like C/C++, so if you do need to do more advanced things, or make things work cross-platform, it takes 2-3x more effort. And don't even get started on how awful Android Studio is ("Repair IDE" is one of the menu items in it, no joke).

Not surprising most people just create web apps in JavaScript on Android. Which is likely Google's plan anyways since it's easier for them to gather rich data on customers via the web than monitoring via Android itself (where figuring out what people are doing is more complex).

Apple's equivalent technologies (Objective-C and Swift) are very cleanly designed and intuitive, and integrate easily with cross-platform code, which isn't surprising since they were designed in-house rather than via clone and own (Java) and a 3rd party (Jetbrains created Kotlin).

I think most consumer problems with iOS stem from the fact that Google invests heavily in Chromium/web technologies, at the expense of their native technologies. Whereas Apple is the reverse. So if you spend your whole life in web apps and/or a browser then the experience is going to be better. Also, most web apps completely disregard any sort of platform UI standards. So again, if you're used to the wild west of web app/page interfaces, the native platform interfaces are going to seem less intuitive.

As someone who tries to avoid using web apps as much as possible because I find them slower to use, less intuitive, and battery killers, I find iOS very intuitive to configure and navigate.

maltz said:

dominikhoffmann said:

With Apple’s loyal following, I would think that an army of willing editors could easily be found who conscientiously would make edits. This could propel Apple Maps ahead and would likely help especially in markets outside of the U.S., on which Apple places a lower priority (case in point: today’s news that Apple Pay is rolling out in Morocco, nine years after its inception).

Apple's following may be loyal, but its user base - especially its Maps user base - is dwarfed by Waze/Google's.  I've also found that even in moderately-sized US metro areas (500k+) new, major roads were on Google/Waze the day they opened, but took weeks-to-months to appear in Apple Maps.  I've also found new-ish subdivisions that have been there 1-2 years, where the streets are there, but the numbering is all wrong.  If you're not in a major US city, Apple Maps is still fairly terrible, in my experience, even today.

Haven't had any problems up here in Canada, which typically lags behind US for updates, navigating newer areas in the past 5 or so years. Only thing I've found living in a downtown core is that it typically doesn't do a great job on traffic conditions. It shows blue almost everywhere, even when there's heavy traffic. But then I've tried comparing routes with Google Maps and it doesn't fare any better. Just have to accept the reality that there's traffic everywhere, and simply avoid areas with construction (both do a good job marking those).

Read: "We can't get as much data from you if you use iOS due to Apple's stance on privacy, and that means we don't make as much money, therefore Android is better"

Wake me up when you can come up with an argument for how yet another social media clone technology makes the world a better place.

Biggest sell for me was not having Google slurp up every bit of information about where I am, where I'm going, how long I stay in certain places, etc, etc. But I agree that Apple took about 5 years to iron out most of the kinks with Maps. Which isn't typical for Apple, but then they weren't great at cloud services in general at the time.