This is part one of testing. I have yet to test it on a site... I may wait to test it on Hive.blog or PeakD.com or maybe i'll try it over on ecency sooner than that.


This is me testing just the SignUp/SignIn experience. 
I get confused and frustrated as it goes on BUT i want to say that with a few quick and easy (mostly wording) changes this could work really nicely. 

But right now the wording choices are going to confuse a LOT of people.

https://youtu.be/lKyE1dxgMqY


# RECAP

Various different ways of saying things
1. Hive Account Name
2. Hive Account Key (posting, active, memo, owner)
3. Store and use your keys securely with HiveSigner
4. Create a HiveSigner password
5. Lock and unlock access to your account
6. Remove Account from HiveSigner
7. Sign Transactions (ADV)
8. Authorities (ADV)
9. Key Type, Account with Authority
10. Secure way to store and sign with your Hive keys. Uses industry standard OAuth2. 
11. If you really still want it: "Transforms web 2.0 apps into web 3.0 decentralized apps." but i don't think that part is needed because there is no follow up as to HOW that happens or why... if there was a link to support that then that's fine.

Other things
1. Don't log me out when i add another account
2. Allow me to easily use my first HiveSigner Password
3. Indicate which keys i have stored for each account
4. Give users an easy way to know which keys do what. 
5. You have a menu on the bottom highlight the page they're on in that menu
6. You reference the same page as "signer" in one menu and "sign transactions" in another
7. The opening screen for hivesigner.com has text that isn't really that useful.