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.
RECAP
Various different ways of saying things
- Hive Account Name
- Hive Account Key (posting, active, memo, owner)
- Store and use your keys securely with HiveSigner
- Create a HiveSigner password
- Lock and unlock access to your account
- Remove Account from HiveSigner
- Sign Transactions (ADV)
- Authorities (ADV)
- Key Type, Account with Authority
- Secure way to store and sign with your Hive keys. Uses industry standard OAuth2.
- 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
- Don't log me out when i add another account
- Allow me to easily use my first HiveSigner Password
- Indicate which keys i have stored for each account
- Give users an easy way to know which keys do what.
- You have a menu on the bottom highlight the page they're on in that menu
- You reference the same page as "signer" in one menu and "sign transactions" in another
- The opening screen for hivesigner.com has text that isn't really that useful.