Proposals of new ideas from user tests

kwokwilliam commented 6 years ago

Feel free to comment on ideas

[ ] Add message that tells users they can use the keyboard to navigate instructions
[ ] Add hover message of what the prev/next page is titled when the user hovers over the left/right buttons for instructions
[ ] Have show answer button be 'harder' to find? (User seemed to click that instead of Try Again, but that might just be the test?)
[ ] Make instructions more into a list sort of format? It's easier to read a bulleted list as opposed to large paragraphs of text
[ ] Add way to go back and forth between reading/writing easily. User wasn't aware of the navigation bar way of clicking around, I know an idea for something like this was still being decided.
[ ] Answer for table could be more at the top where the table is. (Might be hard to do given the current code structure)
[ ] Pop up boxes like for feedback should probably make the screen scroll towards it, because sometimes it jumps past the bottom.
[ ] Example of scratch pad usage, maybe incorporated with the variable swap instructions
[ ] Maybe place tooltips for what the concepts are, like an example of what the code looks like or a 1-2 sentence description.

harshitha-akkaraju commented 6 years ago

Potential improvements from 2nd user test

[ ] Change the section headings on the worldview (code constructs, templates) so they give a sense of what the topics will cover. Or add tool tips with further description for each heading.
[ ] Do not display the left and right arrows on the Instruction view if there are no more instructions.
[ ] Purpose of the scratch pad wasn't on code questions / memory table questions wasn't clear. Should communicate this during on boarding, or come up with an alternate design.
[ ] Implement logging at a more granular level. For example, the order in which they answer a table question.

harshitha-akkaraju commented 6 years ago

Potential improvements from 3rd user test:

[ ] An on boarding tutorial is much needed! Especially to convey the difference between learn to read code and learn to write code.
[ ] Would be good to figure out a better organizational structure for the instruction view. When to split into multiple pages v. when not to.

codeandcognition / koconut