|
|
| (7 intermediate revisions by 3 users not shown) |
| Line 1: |
Line 1: |
| ''' plus talk ''' | | ''' plus talk ''' |
|
| |
| == User experience ==
| |
|
| |
| # How-to improve the user experience of my project so that more people actually use my software?
| |
| In my opinion, there are 3 ways to improve user experience.
| |
|
| |
| #* The work flow should be simple. If the work flow seems to be complicated, user may feel less willing to use it. So in my project, the work flow of backup configurations is
| |
|
| |
| the first time to use this software, user need to enter mailing box address to store archive files
| |
|
| |
| |
| |
| V
| |
|
| |
| select configuration files(if the wanted configuration file is not listed, user can choose to enter the path)
| |
|
| |
| |
| |
| V
| |
|
| |
| select archive programs to make archive file
| |
|
| |
| |
| |
| V
| |
|
| |
| send it to mailing box automatically
| |
|
| |
| |
| |
| V
| |
|
| |
| show response(success or fail with reasons)
| |
|
| |
|
| |
| #* The user can define as many as software performance as possible. But a standard configuration should be provided. Because some lazy and new coming users will not configure the software. For example, in my project, user can choose to backup configuration files some time. Besides, user can choose where to store their archived files on local.
| |
|
| |
| #* Helping docs should be provided. User may feel difficult in some place we can not think of. So we should provide helping docs to help user to overcome problems. For example, in my project, not only helping tips will be provided, API reference for developers will also aviable available
| |
