-
Notifications
You must be signed in to change notification settings - Fork 1
Achievement borad User Testing
The Achievements panel feature allows users to view relevant achievements earned in the game on the current page before starting the game or after the end. Visual and functional effects will be tested usability through user questionnaires, for example. The results of user testing will provide guidance for improvements in the next phase.
The basic functionality and design of the achievement panel was initially completed in Sprint 1. However, the details of the achievements collected by the user are not explicitly displayed. The content of the change depends on the relevant implementation of item collection. Therefore, the main purpose of the test is to test the user's interactive use of the achievement panel has been related to the design of the interview and comments. Users will fill out a form after browsing our prototype design to help us improve our functionality.
This time, we mainly conducted online questionnaires and interviews based on zoom to ask them for satisfaction, which is a qualitative test, so the number of samples is about 10-15 people.
The candidates for the online interview are the participants in the questionnaire, and we randomly select 3 people to conduct one-on-one communication and obtain feedback from users on our design through interview.
After completing the questionnaire design, the group members randomly distributed it to the participants to obtain sample sizes for data analysis. The interview process is based on zoom
In the process of testing, we learned part of the user's usage habits through observation and interviews, for the entrance they will habitually look for a certain position on the home page, and our button position is hidden deeply, there are certain obstacles for the user's use, and the function of the panel that launches the achievement button. We have a back button in the lower left corner, although it is very obvious, but the user's subconscious behavior will look for the close button in the upper left corner or the upper right corner. The design content of this piece goes against the normal way of design.
Also, for users to view achievements, the current idea is that more relevant information will appear in each achievement that the user needs to hover over it. However, the interview learned that the behavior of entering the achievement panel itself was already very troublesome, and they wanted to be able to see all my achievements and progress more intuitively, so they did not want to have a hover operation. In addition, the hovering information panel will always obscure other content. Because it will make the user feel uncomfortable.
- Uniform Pixel Grid Resolution
- Storyline
- Instruction
- NPC info
- NPC Communication Script
- Inventory-System-and-Consumables
- Storyline User Test
- Traitor Clues
- Game Characters
- Player Profile User Test
- Player Eviction Menu Sprint1: User survey (Team 7)
- Player Eviction Menu Sprint2: User survey (Team 7)
- Sprint3 - Win/lose Condition: User survey (Team 7)
- Sprint4 - Polishing-tasks: User survey (Team 7)
- Transition Animation/Special Effects/Sound Effects: Feature Overviews
- Transition Animation and Effects: Design Process & Guideline
- Sprint 4 User Testing
- Transition Animation & Effect: Code Guideline-Sprint4
- Sound effect when players complete npc tasks and hover over npc cards
- Fixing the clue bug
- Music Test
- Player Eviction Menu: Design Process & Guideline
- Player Eviction Menu (Feature Overviews)
- Player Eviction Menu: Code Guideline - Sprint1
- Sprint 1 User Testing
- Detailed Eviction Card: Design Process & Guideline
- Detailed Eviction Card: Feature Overviews
- Sprint 2 User Testing
- Player Eviction Menu: Code Guideline - Sprint2
- Sprint 2 Inventory System and Consumables Items User Testing
- Sprint 2 Inventory System and Consumables Items Functionality
- NPC interaction testing plan sprint3
- NPC interaction testing results sprint3
- NPC Dialogue Scripts
- Code Guideline
- Win/lose Condition: Design Process & Guideline
- Win/lose Condition: Feature Overviews
- Sprint 3 User Testing
- Win/lose condition: Code Guideline - Sprint3
- Enemy List
- User Testing 1: Enemy Image Filter
- User Testing 2: Enemy Animation and AI
- User Testing 3: Basic Attack