Team and Roles
3D Graphics Team created the environment, models, and 3D icon renders.
My Role (UX/UI Designer) was about the entire UI and UX, while collaborating closely with the Game Designer to maintain the desired flow, look and feel.
Developers implemented the designs, with ongoing feedback and collaboration from me.
QA Testers checked the implemented designs and provided feedback on the UX flow and UI.
The Process
Defining requirements, Research and Planning
I began by thoroughly reading and analyzing the Game Design Document (GDD). Collaborating closely with the Game Designer, we brainstormed player interactions with the UI to align with the game's core loop, use cases, and potential challenges.
I conducted desk research and analysis mostly by playtesting games and analyzing gameplay videos of titles like No Man’s Sky, Seeking Dawn VR, Breacher, HUBRIS, and Guardians Frontline. Additionally, I gathered references from the Game UI Database and other UI sources to inform our design approach.
Further, I defined design principles for the entire project, including:
- Font usage guidelines.
- Color coding for fonts and UI elements.
- Layout rules for different UI contexts (e.g., non-diegetic floating screens vs. immersive diegetic elements).
I also selected external UI assets and icons from the Unity Asset Store to save time.
Information architecture design was done separately for each UI context based on GDD and frequent consultations with Game Designer.
Design
Scope
I created user flow designs based on brainstorming sessions with the Game Designer and wrote item descriptions and microcopy for most of the UI text. The graphic assets bought from the Unity Assets Store were adapted to the needs of the project using Photoshop and Figma. I also designed and created several icons, all wireframes, and mockups, while iterating with feedback from the Game Designer.
Time-Efficiency Measures
Designed multiple contexts simultaneously based on priority, such as crafting stations and upgrade stations, which shared a similar style.
Developed the Tablet and Shop UI together, allowing for shared layout designs despite different styles, which streamlined the implementation process.
Prototyping and Dry-Testing
I employed good practices such as using placeholder icons to bring UI mockups to life, providing multiple design options for internal A/B testing, and maintaining detailed project documentation and a database of UI assets. Keeping Archive / Parked Ideas database with old unused ideas for features and solutions that didn’t make the cut, may come in handy in the future, and it is also a good practice I follow. I frequently gathered feedback and iterated on my designs while working on each feature. Before implementation, I always conducted "dry-tests" with the Game Designer to identify and resolve potential issues with user flow.
Implementation and Testing
Although I did not implement the UI in Unity myself, I collaborated closely with developers to ensure the final product matched the original designs. I adapted quickly to various work styles of different team members and resolved technical constraints as they arose, often requiring redesigns to maintain a positive user experience. Playtesting and giving feedback was another big part of my job. I playtested each new build in order to spot any areas that require improvement in terms of user experience. Later, I documented all issues, and proposed new solutions.
Iterations and Launch
As it happens in all agile processes the changes are frequesnt and require elastic, iterative approach. Throughout the development process, I iterated on my designs to adapt to changes in the GDD. I needed to go through the user flow each time a change was necessary, to make sure the UX was not impacted in a bad way. Before the launch, I also assisted in creating marketing content for digital platforms, working alongside the Marketing Specialist.
