I'm finding that while the iPhone's hardware beats most of what Android has to offer, a lot of iOS has weird user design choices (hidden search fields, strange menu placement in apps, random antagonistic design choices), that just seem mildly inconvenient at best.
Also iOS 11 had way more bugs than any Android release I've ever used.
I actually do not understand how Apple dropped the ball so badly. Someone should not be getting a bonus.
I get that people have always complained about older phones being slower on later OS releases, but actually the overal, performance of the phone is fine. For some reason there’s a ton of UI lag on loading screens in the phone app and calculator that’s really frustrating. The phone is only a few years old, but feels like my old 3GS. It’s really annoying to have to pause and wait for the UI to become active in two apps I use extensively, and often want to use in a hurry. This is supposed to be a 64bit desktop class CPU. Games load fast and are snappy as hell. How come loading a dial screen is such a massive undertaking? It’s inexplicable.
Apple skims on RAM/GPU when they upgrade screens or come out with something new. Screen updates sell on hype. People can't wait another cycle for better hardware.
iPhone 3G, iPhone 4, iPad 1, iPad 3, 1st gen Retina MBP, iPhone 6 Plus, iPhone X.
https://www.sonymobile.com/global-en/products/phones/xperia-...
To name one current example, both Android and iOS have the concept of a global password manager for third party apps (and the web-browser). Both Google and Apple offer a password manager that hooks into it. But on Android third party password managers can also utilize the system APIs, whereas on iOS they cannot.
Meaning password managers on iOS are stuck with copy/switch/paste/switch/copy/switch/paste for username and password respectively. On Android you get a popup next to the input box, press it, and it is populated.
This is just one current example but if you look at the history of iOS Apple has been doing this forever. NFC locked to Apple Pay was a previous good example.
Before Apple added the current global autofill APIs on iOS, third party password managers could register a Safari extension. Ignoring how poor the user experience of doing it this way was, it also limited autofill to third party apps based around a Safari webview who chose not to opt out of third party extensions (namely only these apps[0] worked). Very few of the top 250 apps were supported and that remains the case to this day.
Apple added global autofill APIs, but as of today those APIs are only available to Apple. This allows Apple to create a password manager which works across Safari, Safari webview (with or without extensions enabled), and even fully native apps.
If an app isn't listed in [0] it will only work with Apple's password manager or copy/paste. Some apps missing include: Facebook, YouTube, Instagram, Snapchat, Google's app suite (gmail, google maps, etc), Netflix, Spotify, et al.
Calling my post "incorrect" while understanding the difference between the global autofill APIs and Safari extensions is disingenuous and inaccurate.
Well, no. What you said was; "But on Android third party password managers can also utilize the system APIs, whereas on iOS they cannot.", which isn't 'absolutely accurate' at all. The share sheet uses a system API to inject the username/password combination. Your statement is demonstrably inaccurate. It's not as fluid as Android's approach, granted. To make you statement more accurate, you should add '...the same system APIs.", although, I'm not sure that is actually the case.
> If an app isn't listed in [0] it will only work with Apple's password manager or copy/paste. Some apps missing include: Facebook, YouTube, Instagram, Snapchat, Google's app suite (gmail, google maps, etc), Netflix, Spotify, et al.
Ironically, that list totally disproves what you are suggesting, and arguably, the bad actors here are Facebook and Google who own most of the titles listed.
Yes it is.
The global autofill APIs on Android are available to all apps. The global autofill APIs on iOS are available to Apple.
> Your statement is demonstrably inaccurate.
Only if you intentionally strip out context of the statement and paint it as saying something else entirely. Let's look at that line in-context:
> To name one current example, both Android and iOS have the concept of a global password manager for third party apps (and the web-browser). Both Google and Apple offer a password manager that hooks into it. But on Android third party password managers can also utilize the system APIs, whereas on iOS they cannot.
It is pretty obvious IN CONTEXT which "system APIs" I was referring to since the previous two sentences and the entire thrust of the post is about one specific topic. Pulling apart my post to strip out context, and then attacking the context-less parts is just arguing for arguing's sake.
You aren't even making a point about the issue I raised (restricted system APIs), you're just being pedantic.
> Ironically, that list totally disproves what you are suggesting, and arguably, the bad actors here are Facebook and Google who own most of the titles listed.
They aren't "bad actors" because they choose to use native controls instead of a webview.
Odd, 1Password filling usename and password fields in different apps without using webview must have been a figment of my imagination. Thanks for correcting me on that. /s
> They aren't "bad actors" because they choose to use native controls instead of a webview.
Ironically, Google uses a webview to login to all their apps on iOS.
Today, I have moments when I'm just disgusted with Apple, as well as with 3rd party apps on iOS from well funded companies who should be doing better. Though to be fair, most of the time, things do work. It's just that I run into the odd place where...WAT!?
I also really dislike (maybe this is just me) that I can't deal with files as files on an iPhone. I can't just move an mp3 or an ebook to the memory, find it via an app and open it. It feels so locked it.
You can use iPhones with PCs and Android phones with Macs.
Please stop making such inflammatory statements with no substance.