Skip to content

Inventory Design User Testing

mackenziekerr1 edited this page Oct 3, 2022 · 8 revisions

Wireframe Iterations

Multiple distinct wireframes were designed for the inventory interface in order to gather feedback from users to inform our final wireframe choice. The four variations can be seen as follows:

  1. inventory-wireframev1
  2. inventory-wireframev2
  3. inventory-wireframev3
  4. uni 2024

AB Testing

AB Testing was used as the preferred method of user testing as we wanted to gather feedback on the immediate perception of the inventory layout based on the following criteria: which wireframe most suitably shows the player's ability to utilise defence & attack items, as well as place buildings & restore health? Thus, AB testing by presenting the two wireframes side by side in various combinations was the most effective method of testing. Using the corresponding numbers above, the results of testing are as shown below: Screen Shot 2022-10-03 at 11 28 34 am Screen Shot 2022-10-03 at 11 28 44 am Screen Shot 2022-10-03 at 11 28 54 am Screen Shot 2022-10-03 at 11 29 06 am Screen Shot 2022-10-03 at 11 29 15 am Screen Shot 2022-10-03 at 11 29 24 am

Design Iterations

Table of Contents

Home

How to Play

Introduction

Game Features

Main Character

Enemies
The Final Boss

Landscape Objects

Shop
Inventory
Achievements
Camera

Crystal

Infrastructure

Audio

User Interfaces Across All Pages
Juicy UI
User Interfaces Buildings
Guidebook
[Resource Management](Resource-Management)
Map
Day and Night Cycle
Unified Grid System (UGS)
Polishing

Game Engine

Getting Started

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