I worked with a team at Google that was developing an immersive tablet exploration-focused experience for young people. The goal was a mobile app for parents to allow them to see and manage their children's activity within the primary app. My role in the project spanned from designing the onboarding flows through to a few of the minor interactions within the app. The Google team had a rough idea for some functionality, however the only initial requirement was a $1.00 fee.
On first open, I designed simple four-step warm welcome flow that was intended to inform parents about what they were signing up for, what Google Kids was, and brief them on the steps needed to do so.
After logging themselves in through a Google SSO account portal, a parent or guardian had the option to add other account managers to the app. Any additional people would receive an email invite to download the app and sign up.
It made the most sense from an engineering and resource stand point to run the $1.00 fee payment flow within a wrapper/service that already existed. Hitting the "provide consent" button would launch within Google Wallet, similar to buying something on eBay, which would then redirect back to the Parent App.
Here are three rounds of iteration I did within the add a child flow. Initially I was putting several items on a single screen, but it started to feel clunky and time consuming.
I also was indicating progress in an unusual way—within the top header. Simplifying the flow down to just a single step or two and having a lightweight progress indicator was a much more extensible way to go should a new step be added in later.
I decided to show a series of "alerts" in a modal on first load after setting up an account—meaning this modal wouldn't be triggered ever again. These were more or less a simple onboarding flow, but I used this as a way to get someone to customize their child's access settings, alerts, and a nudge to download new child-friendly apps in the Play Store.
Here are three different states of the My Children screen where a parent can add additional people and access their usage data and permissions settings. Had I had more time I would have liked to make the default empty state more compelling and useful.
My solution for the child dashboard screen is particularly successful. It surfaces high level, overall data at the top in a swiping gesture, but showcased any number of devices that the account was signed into—which I felt was a pretty common use-case.
The device settings flow seemed complicated to me at first but using tabs helped me break down the information that I wanted to display. It also allowed for good future-proofing should/when more features would be added.
I also had the opportunity to help with some of the screens of the primary app that was being developed. I put together this concept for a special keyboard that only allowed a child to search certain, auto-suggested keywords after pressing any letter.