Autofill on Android Oreo

Thanks. I see what you mean about the prompt to save. I'll pass this on to our team!

It makes no sense to have it show up every single time, especially for a password an app is saving and thus was neither typed in nor pasted in AND that was filled in by 1p the first time. How about a never for this site or an ability to turn off offering tonsave altogether, without having it tied in to having to turn off autofill entirely?

@Sinister: I agree that it would be better if 1Password could perfectly detect this every time. It's something we'll continue to work on.

What king of answer is that? "We'd rather offer it to save something rather than not"?!

It's the truth. Given the current options — offering to save every time or not offering to save at all — the one that does not result in data loss is better, even if it is inconvenient sometimes.

Thats a brush-off answer. "We dont want to improve oir product in this regard even if it makes no sense and we dont want give you ability to turn off something by itself. We'd rather you turn off the whole autofill feature entirely" . You sound like apple.... "we know best, we tell what your defaults should be..." You hadn't given answers like that for the past two years...

Nowhere have I or anyone else at AgileBits said those things. Only you have. I'm not suggesting that you disable it. I'm asking that you bear with us as we continue to work to improve this new feature.

I think you're uniquely qualified to notice the improvements we've been making just these last few months already, some in response to your own requests. I do apologize though if that gave you the impression that we can do (almost) everything else you want in the short term. We'll continue to add new features and improve existing ones, and we're grateful for your feedback; but keep in mind that all of this takes time. :blush:

Thanks. In the meantime, please consider an option to turn that off - then the can choose how the app is used, just like one could turn off autofill.

@Sinister: It's certainly something we can consider. :)

Whenever a NEW password is crated and presumably pasted in, the user would have presumably first created the login in one password - no one would type in a NEW password by hand, without enough entropy, etc., so presumably 1password ALREADY has the password, as is my case in all of the instances. As such, a user could leave autofill on, and turn off remember password, while still having the password created and stored in 1p.

I think you're probably right about this in a lot of cases, but I don't think that's a safe assumption for us to make when designing 1Password. Not everyone has been using 1Password for a long time, and for folks who were using another password manager or none at all previously, they will need 1Password to offer to save. I'm not saying you're suggesting otherwise, but I think we need to keep the big picture in mind with the design. Thanks! :)