3 ms·

That’s incorrect. Password managers on iOS are able to use extensions and thus auto-fill. I use 1Password and auto-fill works with many apps, only on the ones t

That’s incorrect. Password managers on iOS are able to use extensions and thus auto-fill. I use 1Password and auto-fill works with many apps, only on the ones that don’t are you stuck with copy & paste.

Someone1234 9y ago
What I said is absolutely accurate and you seem to know enough to know that. 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. [0] https://lastpass.com/support.php?cmd=showfaq&id=8606 https://lastpass.com/support.php?cmd=showfaq&id=8606
- alphabettsy 9y ago
  You said iOS password managers are stuck with copy/paste. That’s inaccurate, proved by your own follow-up with an example from LastPass.
- sbuk 9y ago
  > What I said is absolutely accurate and you seem to know enough to know that. 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.
  - Someone1234 9y ago
    > "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. 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.
    - sbuk 9y ago
      > The global autofill APIs on Android are available to all apps. The global autofill APIs on iOS are available to Apple. 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.

Someone1234 9y ago

What I said is absolutely accurate and you seem to know enough to know that. 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. [0] https://lastpass.com/support.php?cmd=showfaq&id=8606 https://lastpass.com/support.php?cmd=showfaq&id=8606

alphabettsy 9y ago
You said iOS password managers are stuck with copy/paste. That’s inaccurate, proved by your own follow-up with an example from LastPass.
sbuk 9y ago
> What I said is absolutely accurate and you seem to know enough to know that. 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.
- Someone1234 9y ago
  > "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. 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.
  - sbuk 9y ago
    > The global autofill APIs on Android are available to all apps. The global autofill APIs on iOS are available to Apple. 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.