CLEU

How does an alarm clock iOS application mature and develop into a tool with a unique-some would say "ahead of it's time"-value proposition? Simple. It becomes a sophisticated hub of integration within the Internet of Things ecosystem.

This is the story of Cleu 3.0.

BACKSTORY

Having evolved through two versions, Cleu was looked at as an aesthetically pleasing application that elevated the alarm clock vertical. But times had changed and the space had become inundated with time-keeping competition.

Concurrently, the Cleu user base was becoming more sophisticated and began dabbling in IoT devices within their homes. After studying this development, it became clear that there was a need for a consolidated solution to device organization, as well as a unique alarm that utilized these connected devices.

PROBLEM

I came onboard to help the Cleu team bring an already well-received iOS application into a new realm of functionality by positioning it as a hub for the connected home. Cleu had already pioneered a gestural based alarm activation mechanism that helped define it's uniqueness. But despite that progressive design feature, it lacked the architectural capabilities to seamlessly scale into the connected environment.

In addition to the IoT pain points that were becoming evident, the redesign timing happened to coincide with the market introduction of the Apple Watch. Having noticed the habits of those around us, using their phones for both timed productivity sessions as well as naps, the Cleu team decided the time was right to introduce a watch extension of the Cleu iOS application.

“Jason has a keen ability to incorporate scalable architecture in his designs. When we introduced IoT connections in Cleu 3.0, Jason worked with the current structure and found a scalable solution going forward. This is not only important in finding product market fit, but critically important as the team and product grow.”

— Uzair Hussain, Founder (CLEU)

iOS APPLICATION: CHALLENGE

Is there a market desire for an Internet of Things enabled controller, posing as an alarm clock?
Is it possible to build connection functionality in a seamless fashion that allow for ease-of-use as well as future scalability?
Could it all be done within a 2 month deadline?

APPROACH

Because Cleu was bringing in legacy alarm clock functionality from the previous two versions, I was focused on the extension of the product as a connected device. I chose to approach this challenge by pursuing a user centered design methodology covering the stages of Discovery, Concepting, and Prototyping & Testing.

DISCOVERY

Audience Definition

Cleu had already amassed 70K downloads by the time work on 3.0 had started. So the first move was an easy one...find out what the users thought. As I interviewed current users, I kept in mind a few proto-personas the team had been discussing. Two personas didn't prove as relevant (currently), but the third was a spot-on match. Meet Early Adopter Erwin.

Competitive Analysis

Every week a new alarm clock was hitting the app store. We tested each one for functionality, creativity and connected ingenuity. Eventually the best rose to the top. As clocks we had our sites set on Sleep Cycle & Rise; for in-house connected controllers it was Nest & Hue; and there was no holding back the ingenuity of the team at IFTTT with their IF & DO Button.

User Scenarios

The average Cleu user was using the application at least twice a day...right before falling asleep (set the alarm) and first thing in the morning (turn the alarm off). Being the first and last points of interaction in a day gave Cleu a unique advantage in being able to provide additional value, especially in conjunction with connected devices like lighting and thermostats.

CONCEPTING

Process Flow

This is the process flow for a first-time user of Cleu. Once connection to a connected device is established, the IoT Devices Log-in path only gets used when new device functionality comes online or the users terminates a connection.

Site Map

At a glance, the architecture of Cleu may appear simplistic. At least that's what I was going for. But inside, I was focused on creating a structure that was not only solid and seamless for our first device integration, but scalable for our next ten, twenty or beyond.

Sketching

Many of my Cleu sketches were focused on working through navigation structure and taxonomy issues. Occasionally I would try my hand at designing various weather conditions.

Wire Frames

The wireframes I provided the dev team acted as a guide pointing in the direction the application was moving. Because we were all working together around the table, conversation and collaboration was the key ingredient.

Screen Flow

As we approached the prototyping phase, I mapped out all the screens in the experience so the team could get an at-a-glance impression of the user journey and easily reference any sticking points.

Design

Cleu 3.0 was meant to feel simple, sleek and subtle. Yet at it's core, facilitate complex environmental interactions. We were going for a Tron meets Jetsons feel. As for the guiding principles of usability, I stuck closely to the examples set forth in the iOS Human Interface Guidelines.

PROTOTYPING & USABILITY TESTING

Prototyping

Prototype screens for Cleu were built in OmniGraffle and stitched together in InVision. I kept with a mid fidelity look knowing that we would be making changes and testing various components during the week of usability testing. The façade and interactions were real enough to capture reactions.

Screen Shot 2016-09-06 at 5.44.42 PM.png

Usability Testing

We fortunately had the ability to test for a week as the dev team began foundational work. I ran a series of sessions on Monday, Wednesday and Friday. During the in-between days, the team went over the notes and made adjustments if we saw fit. By the end of the week we had conducted 13 iterative sessions and felt comfortable moving forward with the design.

iOS OUTCOME

The team hit our deadline and launched the iOS version of Cleu 3.o on April 30, 2015. It was a tense week as the app sat in review, but we were overjoyed when the approval came through. We had successfully built an advanced alarm experience enabling users to control their environment.

Unfortunately, our move into the wearable vertical wasn't as smooth as the IoT journey.

“Best alarm clock in da game”

— Kp Thrilla (App Store Review)

“Wonderful in its simplicity”

— TFStarks (App Store Review)