nus-pe-bot
commented
2 years ago Team's Response
Result:
Rejected.
Rationale:
Splitting friend and game is by intended design to separate the friend and game commands into distinct and easy to reference sections for the user since everything regarding 'friends' and 'games' in one place.
The suggested intermixing the friend and game commands is likely to cause more confusion to the user.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: I understand the rationale given, but my argument specifically refers to the duplicate / similar commands for both 'friends' and 'games'. The separation for these similar commands made it difficult to navigate through the document as I experienced it during testing. While I do agree with the separation for distinct features (such as linking), I still believe generic commands such as add should be organised successively. It was appalling that the command 'linking a game to a friend' had to be displayed before I even knew how to add a game.
As I read through the guide in order, it does not seem intuitive to read this feature (link a game to a friend) before knowing how to add a game into the games list. As a result, it is hard to follow the guide and I have to repeatedly jump between pages (without easier navigation to go back to the hyperlinked table of content). The similar features (e.g., add a friend and add a game) could have been parked under the same category. :)