iOS/iPadOS Application/Extension Clarification

Dave--thanks again for the quick reply...

I can't seem to find a clear explanation of why I should install the iOS Safari extension instead of (or in addition to) using the system's auto-fill capability. Can someone enlighten me?
As you mentioned, there are two different ways to save and fill password in Safari on iOS. Password AutoFill is specifically handled by iOS and 1Password only provides the data for the experience. It allows you to fill your username and password into any iOS app but not other things like credit cards or addresses. You can read more about Password AutoFill here: Use 1Password to fill and save in apps and browsers on your iPhone and iPad

If you're using Safari then I recommend that you use our 1Password for Safari extension. 1Password for Safari features greatly improved filling capabilities and offers an experience that is similar to what you're already used to with 1Password for the browser on the desktop. Not only does it use 1Password's powerful filling brain to better detect fields on websites but it also includes support for things like masked email aliases, on-page password suggestions, the filling and saving of credit cards and addresses, and more.

Here is a guide on how to enable 1Password for Safari on devices running iOS and iPadOS 15 or later: Get to know 1Password for Safari on your iPhone or iPad

This explanation is a little clearer to me than the situation on macOS ;-)

Since my particular usage is very focused on passwords (and not on masked email or credit cards), and since that although the iOS Safari extension is quite capable in a lot of areas, its unfortunate limitation of accessing only your entire 1P database or a single vault--and not collections--it seems like I don't need the extension at this point.

Also, reading the above-linked support pages carefully seems to imply that the burgeoning passkey support is tied to the iOS side of filling things (system auto-fill).

So...since the magic 'key' icon gives me the ability to create new logins and generate passwords, and since iOS Safari itself will autofill addresses, etc., the extension seems a little superfluous.

I'll disable the extension for now, and give it shot again down the line. My suggestion to the team is to see if there's a better/clearer way to communicate WHY I should enable either iOS AutoFill or the 1P iOS Safari extension, and what trade-offs I make when I choose not to use one (or the other).

Thanks!