-
Notifications
You must be signed in to change notification settings - Fork 1
Sprint3 Team 3: User Testing for ending menu design
In the first two sprints, our team selected and designed background music, including Action Sounds, etc. In Sprint3, our team changed direction and was mainly responsible for designing the interface of winning and losing games. This user test examines and evaluates the design of the end menu to get feedback on aesthetics and functionality in the initial design, as well as add-on designs for the next sprint. The feedback from this user test will be of great value to subsequent development and will help us improve and optimize in the next sprint.
- We created a survey form, posted it to the game discussion group, and received the results from a variety of users, including people :
from other teams in the same studio, classmates, friends, etc.
- These questions are based on the information the player has access to, including their state and performance in the game. Because we have provided various options, the testing commonly used in user testing to understand users' preference. In general, we asked participants whether they preferred which design and why.
- The link to the survey is: https://wj.qq.com/s2/10899272/9142/
As shown in the results, we had a conversation with all the respondents at the same time, and they explained some of the reasons for their choice. Most of the respondents gave the following opinions:
- As for the pop-up mode of the interface, they believe that the full-screen display has a greater visual impact, stronger and more shocking. Since the full-screen display contains more display area, the visual impact is greatly improved
- For the interface display of winning and losing, respondents said that "clean interface and simple information are more attractive and advanced". Therefore, we choose to provide the restart game and return menu to make the interface simple, while the information not displayed can be selected after returning to the menu. We think this satisfies the two main points of brief interface and no missing information
- The color selection is relatively simple, and the use of gradient makes the picture not too simple, with the feeling of the end of the game
- In terms of text content and format, we still use simple style to meet the pixel style, and the interface has a sense of advanced. In terms of graphic selection, we choose the complete and broken hearts to represent the ending of the game, some interviewees said that this is related to the large-scale game "Minecraft", which gives people a good feeling.
We know that the two interfaces have certain repeatability, which gives people little contrast, and the design of the interface at the end of the game is not rich enough.
The next sprint user test will be based on the information gathered from this test and feedback. We have planned future tests and evaluations that may be needed to ensure that the team's work is exactly aligned with what needs to be done in the next sprint:
- Increase the color diversity of meet-and-greet displays
- Add additional text and options as necessary
- We will conduct a satisfaction survey to improve the five aspects of text, color, graphics, content and format
- 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