separation of account adding process from creation of Beet wallet

[tbone-bts]

Ideally the user would first create a Beet wallet, and then go about adding accounts:

1. For creating a Beet wallet, I would suggest letting the user enter the wallet name and password on the same screen. Perhaps encourage a backup after the wallet is created. Then you can prompt user to add their first account.

2. For adding accounts, it would be helpful to have an "Add Account" title/header at the top. Also, I think you can let the user enter the blockchain and other info on the same screen.

By the way, is it really necessary (or even useful) to enter account name? Is it not the case that only the private keys are necessary (aside from bitshares cloud wallet) and the account name could then be be looked up?

[sschiessl-bcp]

One could let the user create the wallet and then enter the dashboard in an "empty state".

That empty state displays where/how the user can add accounts (could be a visualization of where to click to find the function), then the user already has to use the normal add account button for the first account and has "learned" the process implicitly