Connected Devices :: User Narrative & Use Case

User Narrative and typical use case for Timee, the smart alarm clock we are building for Connected Devices.  The clock will take in external factors like calendar appointments, weather and transit information to provide smarter scheduling to the user, helping them to avoid situations where they are running late to appointments.  In a broader sense, we also see the clock potentially functioning as a hub which other smart devices can connect to.  The devices would all function correctly on their own, but as you acquire them you can link them to build more networked interactions between the devices.  Instead of resigning hubs to plain plastic boxes which get stuffed away out of sight, why not disguise them in nicely-designed household objects, with functionality of their own?

 

General unboxing and setup:

On unboxing, the user will take out the physical clock as well as a page containing a couple brief instructions.  It will instruct them to plug the clock in, provide a link to the app store to download the clock app.  The app will walk them through the remaining setup.

 

userScenario-01

 

The first thing the app will do is pair the phone and clock on the users wifi network.  Success will prompt a confirmation on the app as well as on the clock.  The user will then have to complete a few fields, including giving location permission, and link their google calendar account to the app.  When that is done, another round of confirmation on the phone and clock will occur.  This section will be much more challenging in practice than is shown here, and will take the most fine-tuning on our part.userScenario-02

As for a typical use case: most mornings the user will have a standard wakeup time for work, which should go without issue.  But perhaps on this morning, the user has a scheduled morning meeting.  There also happens to be a delay on the L train.  The clock would see the appointment on the calendar, as well as see the MTA delay information, and update the users alarm to go off a half hour early to account for the delays.  There would be a subtle visual signal on the alarm clock itself, notifying the user that they are up early because of a transit issue.  A notification would be waiting on their phone with more detailed information, explaining exactly what the issues are that caused the early alarm.  As part of our broader vision for the alarm as a home hub, we plan to link it to the Philips Hue bulbs.  Since we’re already familiar they should be an easy integration.  We will use them to give the user an added signal layer, reminding them when it is time to leave the house.  When it gets to be 10 minutes prior to the time they need to be out the door, the lights can give a signal (dim, flash — we’re still undecided) that will be hard to miss.

userScenario-03