Suggestions of Jerry (aka J-God) to improve BTS wallet user experiences

[cn-members]

hello everyone,

Recently members of chinese community had a discussion on how to improve user expeirences of BTS wallet, so that we can introduce it to our friends, especially female friends. During this discussion, many people have proposed many good suggestions, especially jerry (aka J-God). So we decided to collect these suggestions and propose it here.

To increase readibility, we summed it up into a mind map (below). Same content  will also be presented in text after this figure. So you can choose either way you like.




Suggestions of Jerry (aka J-God) to improve BTS wallet user experiences

1. While releasing new version of BTS wallets
Current Status:
- Because of the 'special networking environment',
the downloading speed of github could be extremely slow or unstable
- The downoaded files could be broken if the network is untable
Suggestions:
- While new versions of BTS wallet binaries is released,
their SHA checksums should be posted in github site at the same time
- people in china can share with each other
- I3 or some of us can setup mirror sites
- files can be easily downloaded and check the SHA checksum posted in the github, so we can make sure that files are not modified/broken
- While the built-in function of wallet detects a new version of wallet,
it should also provide the link to BTS wallet download page, so we can conviently check the changelog and download new binaries.

2. Windows version BTS wallet
Current Status:
- 32bit and 64bit installers are sepatated, which makes people feel confused.
Suggestions
- a unified installer should be provided for windows,
and the installer can automatically detect the OS is 32bit/64bit.
- If 64bit installer is still unstable, please address this point so that users can make their choice.

3. While installing BTS wallet
Current Status:
- current installer can only specify the path of wallet programs to install
- the path of wallet data can not be specified
- the default path in windows is inside a hidden folder = > inconvenient to use. Furthermore, if the system failed (e.g., c drive partition error, accidentially formated), the wallet data could be lost
Suggestions:
- installer can let users to choose the path of wallet data
- if the installer detected that there are partitions other than c drive,
the default path of wallet data should not be in c drive
- the default wallet data path should not be inside of a hidden folder

4. Layout of GUI wallet
Current Status:
- While entering passwords in lock screen,
the screen does not show that whether the Caps Lock is open
- the internationalization is not complete (chinese interface), only the messages from web wallet is translated
- messages from bitshares core program is not translated
- messages from qt framework is not translated
- e.g., main menu,  status bar in the bottom
- e.g., 'Block are synced' should be shown as '區塊已經同步完成'
- the progress of syncing shown in status bar is not intuitive. Currently, we only get "days left to be synced". Also, the progress of syncing is not shown in lock screen
Suggestions:
- While entering passwords in lock screen,the screen should show that whether the Caps Lock is open
- an .lng file can be posted in a collaboration platform (e.g., google doc),
so that everyone can help translating it
- The progress of syncing should be shown as ETA, and the percentage of syncing can also be provided
- the progress of syncing should be shown in the lock screen

5. the ease of use of BTS wallet
Current Status:
- basically only advanced users know how to use it, newbies would be scared away
- there is no help page while pressing F1
- we can not check the balance of specified public key
- we can not check public keys with top100 balances,
but this site can do this:
(can not list this url due to this account is a newbie account)

Suggestions:
- find a newbie to help troubleshooting, especially female newbie users: 1.) find a newbie who never know about bitcoin, and only have basic knowledge in computer science. 2.) let her use the wallet. 3.) record her complaint and improve base on it
- while F1 is pressed, a simple guide with pictures should be shown
- newly added functions should be labeled in special ways, and a link to its guide should be promoted while using it. e.g., short
- the functionality to lookup the balance of specified public key should be provided in GUI, also the abilty to check the balance to check a bunch of public keys. this will help exchanges to prove that their funds are sufficient
- add the functionality to list top100 public keys with highest balances

6. GUI Security
Suggestions:
- the fields for entering passwords in lock screen should be anti-keylogger
- the commands/operations should be divided into 2 categories: commands that moves funds or operate private keys and etc. For commands that moves funds or operate private keys,
another 'transaction password', which is different from wallet password,
should be entered to execute these commands.
- For transaction password: 1) transaction password has to be different from wallet password. 2)  this can avoid private being buffered in ram continuously, the private key should only be extracted for short term while the transaction password is provided. 3) to maintain convenience, small payouts (the limit can be customized) can be executed without passwords, but the total amount of small transaction per day should be limited (just like VISA)

7. Wallet syncing
Current Status:
- often 'no connection' or only a few connections
- have to find someone to provide node list, but there is no way to easily add a list of nodes in GUI
Suggestions:
- a function to let people who have good node list to easily extract some 'human-friendly code'
- people with poor connection can easily add a list of nodes by entering this 'code'

8. Wallet Backup
Current Status:
- we can only manually export json files
Suggestions:
- should be able to define the path of backup files
- users should be able to make a schedule or a list of conditions to determine when the backup will be made besides automatic backup.
e.g., you can determine everyday or everytime when a transaction is made,
the wallet would be backed up.