MRoC - UI/UX

In this project, I worked closely with game designers and producers to identify and capture the MVP for the game’s core loop.

My responsibilities are:
· Creating UXDD that captures the high level MVP UI/UX work and user flow for pre-production
· Support the gameplay designers with UI/UX solutions for game modes
· Provide feedback and assist UX team members in UI/UX design and flow.

Tools: Unity, Photoshop, Illustrator, Adobe XD, Adobe Animate

  • Role Lead UI/UX Designer
  • Date 2019- 2020

Platform: MOBILE

https://marvelrealmofchampions.com/

STORE DESIGN

Create multiple different template to support the following:

  • Free offers to encourage users to visit the store more frequently
  • Purchase limit & offer limit
  • Sales (timed)
  • Bundles with breakdown of all the items
  • CTA when the user has insufficient funds to make the purchase
  • Drop rate communication

Identifying the user flow for accessing the Store.
The goal is to make the store as accessible in places that players likely need to spend.
EG: Upgrading a character, player may run out of currency to successfully upgrade. By providing quick access to the store, we reduced player friction to spend

Worked alongside gameplay designers to create, iterate and explore ways to communicate character abilities and mode objectives without overwhelming players.

These are some of the explorations and solutions

Hud communication: The intention is to keep the hud layout consistent across all modes.Although the objectives are different for Baron War and Baron Defense mode, the core information of the hud did not change drastically.

Damage types: The intention is to group damage types and health numbers by color, size and animation. It is also important that players understand if the damage is done to them or by them. In a chaotic match, it can be confusing as to who is dealing the damage- therefore, we wanted the damage number to only apply to the player and those that are targeted to reduce unnecessary noise.

Health bar: Providing guidelines for how the heath bar and status effects should be displayed. Identifying which character (player or NPC) requires a persistent health bar and those that don't.
Lower NPCs do not require a persistent health bar and will only show up when the player deals damage to them. This is because they are not the main objectives and by making the health bar contextual, we can reduce the amount of information the players see.

Status Effects: Customization lets the player build champions that cater to their playstyle. During combat it is important to communicate the buff/debuff the champion has for the player to make informed decisions when encountering them. Feedback when a player applies a debuff on their opponent or a buff on their ally should be communicated clearly.

CUSTOMIZATION WIREFRAMES AND USER FLOW

This was designed during the early stage of production, the current playable feature had since changed. However, I'd like to walk through some of the steps and considerations that went into designing this feature.

Prior to jumping into creating wireframes and flow, we first identify who our user groups are. There are two main user groups we want this feature to focus on (image below)

Once we identify the user groups, we create a User Journey to map out the experience - site map and final wireframes & flow