Access Standalone Password Generator
Hello
Is it currently possible to access the password generator tool without:
- Logging into 1Password
- Creating a new login just to access the generator
- Having to deal with the fiddly menu in the Chrome extension that disappears too often (not your fault).
Basically what i'm looking for is to have quick access to the password generator tool without the password storing aspect of the app getting in the way.
This is useful if for example i am creating user accounts for a client, ftp credentials, database credentials, anything else not web based where i just need a good strong password and do not want to store it in my own 1P Vault.
Implementation Suggestions:
- Put a button on the login screen that opens the generator. There is plenty of space: http://puu.sh/kNb5X/ee30257c2c.png
- Access the generator from a menu option in the app.
- Allow me to create multiple passwords and export them to a text file.
This would be a fantastic feature for me personally and is so obnoxiously easy to implement as it largely reuses existing code. Of corse many password generators exist bot online and in the app store however i'm already using 1P. There is no down side to making it further integrated into my life and workflow.
Comments
-
Hello @OnePassMan,
So it's not exactly a massive improvement over creating a Login item but a Password item or a Server item (depending on the purpose the password) may at least seem a bit more appropriate. Of course if you really don't want to keep the password afterwards then that's no real difference. I'm surprised though, I can't think of any time I've created a password that I haven't needed to keep. Obviously our requirements and needs differ
The one concern I have is we often get people upset that they think we're not storing passwords and currently we do! If we have a Password Generator that saves to your vault and some standalone version that doesn't I fear there could be genuine confusion. I understand your desire and I can't argue with your logic that you have 1Password and want to use it for all your password needs. Maybe if it were labeled as some kind of batch generation (with a batch being as small as 1) where the batch isn't saved in your vault that would help lessen any possible risk. The other criteria we need to meet though is one of demand. Given there are, I believe, legitimate concerns over possible confusion we'd probably want to make sure there is a reasonable demand for such a feature. Every feature request has to go through this sort of evaluation as we have many more good ideas (many from our valued users) than developer time so it's always a competition to see which wins.
So none of this is to say that it may not happen, just that I think we would need to be cautious not from the code aspect but the interface and ensuring our users, who span quite a wide range of IT comfort zones, don't run any risk of password loss. Hopefully you can see why we'd need to be tentative here.
0
