Blog

A simple OOBE for Digital Turbine

Project Overview

Digital Turbine, whose platform offers app delivery and discovery for Android operating systems, was planning to test a new delivery experience to Samsung, LG, Motorola and other device manufacturers. This particular experience was for new device owners and aimed to offer a seamless experience to download popular apps during, and immediately after, setup.

For this product, the client needed four flows:

  • Integrated within the phone setup experience
  • Integrated at the end of the phone setup experience
  • Accessed through a push notification
  • Accessed through an icon from the app tray
We explored several ways to treat the app grid and selection styles.

Process

For this project, there wasn't much to discovery or research to do. The integrated experiences needed to pretty closely resemble the Material Design language. The post-setup experience however could deviate a little more, but still needed to retain some Material Design elements.

When conceptualizing the post-setup experience this experience I put myself in the user's shoes and thought about my own experiences setting up new devices. Not even necessarily phones, but computers, consoles, etc.

I settled on the idea of a 'boilerplate' or a 'package' of apps. When setting up a new computer for example, there's always a host of apps that I need to download right away.

So this design was less about how this experience looked, but what it communicated. I wanted to tell the user "Hey, come get all of the best apps right here, in one place." and by showcasing some heavy hitters on the launch screen, it would get them clicking through. The supporting copy reinforced that there was still choice.

App icon.


Once on the list of apps, we needed to make it easy, so simple checkboxes for the apps they wanted and following that a simple confirmation screen, the illustrated what was happening in the background.

In addition to the UI/UX and Visual Design, I need to create a user flow map for handoff to the developer.

The client wanted all of the flows in one PDF not only for the developer but for review with the rest of thee team. I designed it in a way that viewing it you could see the entirety of the app and all four flows.

One of the things I needed to communicate was when pages should automatically switch, versus being triggered by a tap. I also needed to tell the developer that certain screens needed options in the Admin panel.

User flow diagram for the product team and developer.

More Blog Posts

How I designed a popular posts plugin for WordPress
15 min read

Did my own bias play too big a part of this project?

Read More →
Tutorial
Building a Pinterest-Style Portfolio in Webflow
15 min read

In this video I'll show you how to build a masonry style portfolio layout (Pinterest Grid) in Webflow

Read More →
Thoughts
Shit I Wish Someone Told Me When I Was in Design School
15 min read

Things young designers need to know

Read More →