Bring Back the Standalone Password Generator in Android – Not Just Hidden in Login Creation

Thank you very much for your reply, Dave.
And thank you as well to AJCxZ0 and Tamara (Crazy4Happy) for sharing your valuable thoughts.

Dave, your points were very logical and easy to understand. I agree that even in cases that may seem irregular at first glance, it’s often possible to handle them through 1Password’s “New Item Creation” UX.
That said, my perspective is closer to what Tamara (Crazy4Happy) mentioned.

In practice, account registrations often don’t succeed on the first attempt. Personally, I always make sure to log in with the newly created credentials after registering. The reason is that some sites don’t clearly state their password requirements—such as length or allowable symbols—and in some cases they don’t even display error messages after input. In those situations, the only way to confirm is to attempt logging in again. (Of course, this is a UX issue on the site’s side, but unfortunately, it’s the reality we face.)

Especially when you make a habit of using long and complex passwords (as I believe many 1Password users do), the likelihood of failed registrations increases. In such cases, the process ends up being trial and error: guessing the requirements and retrying until successful.
Only after the registration finally works and I can log in successfully do I save the item in 1Password.

Because of this workflow, having a function to “simply generate a password” would be extremely helpful.

I understand this may partly come down to personal preference or habit. However, for me, I don’t particularly like the idea of creating a new item in 1Password solely for the purpose of generating a password. Each time I do so, multiple new items get created, and later I have to go back and clean them up—which doesn’t feel very smart or efficient.