Sprint 1 Save State Design Gameplay screen
- Save State Design Introduction
- Primary User Group
- Justification for existence
- User test to identify location
- Save State Design – Welcome Screen
-
Save State Design Gameplay screen
- Sprint 1 Design Gameplay screen <--You're Here
- Sprint 2 Design Gameplay screen
- Final Design Style
- User testing session - final design
- Appendix
During the first sprint we derived inspiration from existing icons that mimic technology. As seen in Figure 8, load and save icons which relate to technology typically look like arrows pointing either up or down mimicking upload / download state. From the technical point of view, we wanted to emphasize the data movement as if the user clicks “save” and the data is “downloaded” and once he or she clicks “load” the data is uploaded to the server.
Figure 8: Save and Load icons in the gameplay that are associated with the download and upload state
To confirm design with the users we conducted a survey [Appendix - Sprint 1 Save State Design Gameplay screen]. The purpose of the test was to confirm whether the icons are perceived according to its intended use. As seen in Figure 9, in the survey we presented a screenshot of the gameplay icons which we designed in pixilart. Instead of quantifying the results similar to just showing the labels and asking to rate how well they are associated with the context, we asked participants to provide their opinion regarding the meaning of the icons. That way the data became qualitative.
Figure 9: during sprint 1 we designed icons which were literally perceived as download and upload buttons.
The results of the survey indicate that majority of users perceive the buttons too precisely. In other words, because the meaning is correctly associated with the download and upload states, we feared that users may literally perceive them as a feature to “download” something in the game instead of saving the game. Thus, we deployed a second design sprint and conducted additional testing sessions.