top of page

Player Profile

UX - UI - Live Feature - Design
Company - Gamesys

Brief

The brief was to create an area within the app where the user could access and input personal information (such as their name, email address, cell phone number, and their home address), see all the trophies and achievements they had accumulated while playing. The section also needed to accommodate any other new features that would be important to the user set for later release (Refer a Friend, for instance).

This was the biggest challenge of designing the player profile section; new features had yet to be decided or designed, more fields of data could be added later on (if and when needed), and it had to also encourage and incentivise users to input their data.

New flows had to be worked out for each new section, and Dev teams consulted and informed on the data they would need to store in the backend.

r_ipadMockupPlayerProfile.jpg

Approach

While the project had come on the back of the Cell Phone Confirmation project, which had established much of the framework to where the data would be stored in our back end and where within the app it would be presented to the user, there were still many variables to be worked out.

 

I re-examined the research carried out for the cell phone confirmation project and extracted any user profile sections I could, as well as looking into various other profile sections in apps and competitor games. The layout was wire framed to suggest possible ways in which we could present the info to our users, trying to use a format that felt familiar to how other games our users maybe be used to seeing.

 

Making everything ’fit’ was the biggest challenge of the project, as, by this point, what was to be included in the full player profile was being decided on, so responsive layouts and components were key. 

Mockups

Documentation

Documentation for this project wasn’t as extensive due to a lot of considerations worked in during the Cell Capture Project. However, many ‘if’ statements and variables still had to be visually explained for the various teams working on building and testing the feature (“If this happens, then this is shown here,” for instance).

bottom of page