1. Discover and Research - Design Task
The goal is to create a personalized feature in the onboarding experience which requires collecting the child's first name and year of birth
Objectives:
-Have as many parents complete the personalized information
-Minimize friction and drop off
-Provide assurance to the parents as to why we are collecting this data and give them the option to read privacy policy
2. Define - User Journey
I conducted a thorough analysis by downloading the game and mapping the current user First-Time User Experience (FTUE). This process enabled me to clearly pinpoint where the parent's experience transitions to that of the player. The segmentation assists in finding the specific app area intended for parents verses player, ensuring a targeted and tailored experience.
Furthermore, I captured screenshots of the game interface and identified potential areas of enhancement. Alongside this, I compiled a comprehensive list detailing the objectives of parents as well as potential pain points they might encounter. One noteworthy observation is the app's request for the 'parents' age. It struck me that this terminology might not be all-encompassing, considering scenarios where legal guardians or other family members are involved. As an example, if an aunt downloads the game for her niece, she could encounter uncertainty regarding whose birth year to input. In such cases context clues about the significance of obtaining the parent's age would be immensely helpful. However, the current version of the app lacks any explanatory context about why the parent's age is necessary for starting up the application. It remains unclear whether the purpose is to verify the presence of an adult or to collect data about the age demographics of app users. Addressing this aspect can enhance inclusivity across diverse family structures and alleviate potential confusion.
My insight suggests that this specific screen presents a strategic opportunity for incorporating the new personalized feature, wherein the player's name and birth year are required.
As a Parent I...
...want to get the set up done as quickly as possible
...I want this game to keep my child entertained
...want to see the value in this app before I commit to paying for anything
...I do not use apps often so I want to be able to easily understand how this app works
...Do not want to see my child upset or frustrated
Plain points/Drop off
...why do I have to give my birth year? I dont want to give that information
...I am not the childs parent but I am their legal guardian, do I put my date of birth?
...my child cannot read, they keep asking me what the text says (the sound is not on)
3. Ideation - Brainstorm
This screen is where we can enhance the experience. It's also one of the first thing parents will see after the company logo. Our goal here is to guide them through this process quickly while showcasing the essence of what the Sago Mini School app offers.
I've also written short descriptions for each design concept, highlighting how they fulfill our objectives.
Objectives:
Minimize Friction - Have as many parents complete the personalized information
Privacy concerns - minimize friction and drop off
Completing the personalization screen - provide assurance to the parents as to why we are collecting this data and give them the option to read privacy policy
Concept 1
Minimize Friction
-Streamlining the onboarding procedure, I propose gathering all necessary information within a single screen for user convenience.
-To preempt any potential confusion or distrust, it's important to include a concise explanation regarding the purpose of collecting this information.
-In the case of the player's birth year, we can significantly expedite the process by replacing manual keyboard entry with a drop-down menu. Users can swiftly select their birth year from the menu, sorting with the most recent year, thus expediting the overall onboarding process.
Privacy concerns
-There is a link to Sago Mini’s privacy and policy document for concerned parents
Completing the personalization screen
-Upon filling out this data, parents will have the option to progress to the next screen or opt to close it for completion at a later time.
-The button associated with this action will remain disabled in cases where the required information has not been entered.
Concept 2A
Minimize Friction
-Implementing a user-friendly approach, we could offer a convenient drop-down menu for parents/guardians to select the player's birthday, streamlining the input process.
-A notable observation within the application was the absence of a confirmation or editing feature after entering the parent's birth year, it would immedietly move onto the next page. Addressing this, I introduced an "edit" option to provide users the flexibility to fix any potential typos or errors in their input.
Privacy concerns
-There is a link to Sago Mini’s privacy and policy document for concerned parents
Completing the personalization screen
-The underlying concept of this idea is to provide parents/guardians with a preview of the personalized experience that awaits them. Upon entering the child's name, a charming array of icons corresponding to each letter could emerge—think 'cat’ or ‘cupcake’ for the letter C. Particularly, if the child is present beside the parent during this setup phase, it creates a delightful opportunity for shared excitement. The child's joy in seeing engaging visuals on the screen can mirror the parent's satisfaction in witnessing their happiness.z
Concept 2B
This concept is the same as above, but the input fields have been placed on the left and right for easier reach and access on a mobile device
4. Prototype - Low fidelity mock ups
I've included the final low-fidelity mock-up, which then informed the high-fidelity design, taking into account spacing and padding on a mobile screen. I worked to maintain consistency by employing a font, style, and graphics that resonate with Sago Mini's distinctive brand.
During my gameplay observation, I took note of Sago Mini's design elements: rounded corners, a bubbly sans-serif font, and a concise colour palette. I also drew inspiration from the game's character and art style to create the cupcake and cat illustration.
Minimize Friction
The final design is a fusion of elements from both concept 1 and concept 2. I find it crucial to infuse a sense of personalization right from the get-go. To achieve this, altering the text from 'Who will be playing this game?' to 'Nice to meet you!' after entering the name is a prime example of how we can make the parent and player (if involved in setup) feel acknowledged by the game and see value in putting the personal information into the input screen. The addition of art and animation also adds to the feeling of satisfaction when completing the input fields
-The continue button is disabled until the guardian/parent has completed the required information
-The skip button is right next to the continue button for ease of access for parents who choose not to disclose the players information that that time.
-Additionally, I've opted to position the input screens on the right side for mobile users, ensuring effortless access and thumb-friendly interaction.
Privacy concerns
-There is a link to Sago Mini’s privacy and policy document for concerned parents
-There is an explanation above the privacy policy explaining why we are asking for the personal information of the player, this will hopefully give more context to why this information is needed and reassure the guardian/parent
Completing the personalization screen
-The objective here is to swiftly collect this information from parents. Placing it on the first screen enables them to input the details promptly, without any setup-related factors causing unnecessary delays or frustration.
-Removing the close button ensures that this step becomes an integral part of the setup process, emphasizing its mandatory nature.
5. High fidelity mock ups
