| | 130 | (from Dan:) |
| | 131 | |
| | 132 | * We need a focus on "reading" a book rather than "viewing" the book - if Sophie 2 is to succeed in an academic environment, people will need to be able to spend a lot of time in Sophie Reader reading and commenting on books and user experience in the Reader is very important to this. |
| | 133 | * To the glossary, I'd add "timeline" and "page template" as these seem to be the two concepts that confuse people. |
| | 134 | * Does multilingual support fit in here? |
| | 135 | * Tooltips: are these tooltips or balloon help (as exists in Sophie 1)? If balloon help we might want the option to turn them off for more advanced users. |
| | 136 | * The "skilled user" concept might need to be thought about - one thing we found with Sophie 1 was that users who were "skilled" by a regular definition (experience with Adobe applications, for example) were more confused by the interface than those who didn't know very much about making things on a computer because the halo/HUD interface was very different to anything they were used to. Maybe this changes in Sophie 2 as the interface becomes more normal? |
| | 137 | * Reporting issues: I think we need to make this easier for users - often developers didn't get enough information about what actually went wrong in a book in the Sophie 1 bug-reporting system. (There are also privacy concerns here.) |
| | 138 | |
| | 139 | |
