Skip to content

Achievement borad User Testing

Kai9613 edited this page Aug 30, 2022 · 3 revisions

Introduction

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.

background

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.

Test plan

Questionnaire

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.

Questionnaire:

Interviews

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.

Process

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

Analysis & Summary

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.

Table of Contents

Home

Game Design

User survey

Sprint 4

Eviction Menu and Win/lose Logic: Polishing tasks (Team 7)

Button Sounds and Ending Menu improve (Team 3)

Sound effect and Fixing the clue bug (Team 6)

Improvement of Enemy and Attack (Team 1)

Add Features When The Player Get Attacked and Overall UI Improvement (Team 8)

Sprint 1

Achievement System (Team 2)

Player Eviction Menu (Team 7)

Countdown Clock (Team 4)

Music (Team3)

Map (Team6)

Sprint 2

Player Eviction Menu (Team 7)

Character Design & Animation (Team 1)

Music (Team 3)

Inventory System and Consumables Items (Team 8)

Scenario design

Achievement System(team 2)

Storyline (Team 5)

Countdown Clock (Team 4)

Sprint 3

Ending Menu (Team 3)

NPC interaction (Team 2)

Win/lose Condition (Based on Eviction Menu) (Team 7)

Player Profile (Team 4)

Game Logo (Team 8)

Clue storage (Team 6)

Enemy Design and Attack (Team 1)

Scenario design for village(Team5)

Game design
Entities and Components

Service Locator

Loading Resources

Logging

Unit Testing

Debug Terminal

Input Handling

UI

Animations

Audio

AI

Physics

Game Screens and Areas

Terrain

Concurrency & Threading

Settings

Troubleshooting

MacOS Setup Guide

Clone this wiki locally