Google One is a rather unusual project in the sense that it started off with this request: create a platform where users pay monthly for a premium Google level of service. We were tasked with this so that we could create tiers of service for Google users who were ready to part with money in order to get a better experience. The project managers communicated with different parts of the company and got us a key feature: Google Drive storage. Secondly, we got Google Hotels discounts and various rewards like Play Store credit. But eventually, the project was supposed to be akin to Amazon Prime, an ever growing set of benefits for the paying member.
Why would a user download this app, and why would they open it? The main reason to download it, would be to purchase Drive / One storage. However, the user could also purchase the storage space on the web. So, we have to assume that they’re using the app to just check storage space. Especially since it is not the app used to upload photos to the cloud: Google Photos is. So, we are left with basically two features: checking how much storage they have left, and checking if there are any nice rewards.
One of the best reasons for a user to visit this app would be to see if they can redeem a reward, like a hotel discount. The thinking went that they could revisit the app and have irregular rewards. And based on the surprise factor of receiving a reward, they may be more likely to open and visit the app. In user testing, this was received well.
Many users will be transitioning from other Google products onto Google One. Like Drive and Photos, there will be opportunities to step into the One space and purchase a subscription. These are some examples of how those moments might like. Here, we might urge a user to purchase storage as they run low.
The tabbed navigation that was in my first design made it into the internal beta (dogfood) version, into production, and is to this day in the Play Store. That has 5 tabs: Home, Storage, Rewards, Support, and Settings. At this point I realized the redundancy of the first two tabs especially, and probably the first 3 tabs could be reduced into one tab. Since the Rewards content wasn’t so overwhelming that it really needed a ton of space, nor was the Storage content. And finally, Home just ended up displaying what was repeated in the next 2 tabs. So, I came up with this 3 tab approach.
To this day, they still use my first 5 tab architecture, but I would probably recommend the 3 tab approach as it is simpler and removes the need for the nav bar to scroll horizontally.
As the platform was evolving in the conceptual phase, we often experimented with concepts such as these. This page displays a search hotels feature which specifically shows the user Google One discounts on hotels. And then, they are shown some other perks as well. These wireframe / UI sketches are included to show some unfinished “process” works, and to further show the exploratory nature of the Google One product idea.
Samsung Milk Video
Product DesignMilk Video: Designing a Video Product To Entertain BillionsView Case Study
Product DesignDataset Studio: Designing an Image Annotation and ML PipelineView Case Study
Interested? Send me an email telling me about your project and your company and I will be in touch with you shortly.Contact Me