What’s different about UX
for the internet of things?
Claire Rowland - @clurr Image: Disney Movie Year
- Independent UX and product
- Lead author: “Designing
Connected Products: UX design
for the consumer internet of
things” (due May 2015)
My grandfather could probably have told you how many electric
motors he owned. There was one in the car, one in the fridge, one
in his drill and so on.
My father, when I was a child, might have struggled to list all the
motors he owned (how many, exactly, are in a car?) but could have
told you how many devices were in the house that had a chip in.
Today, I have no idea how many devices I own with a chip, but I
could tell you how many have a network connection. And I doubt
my children will know that, in their turn.
Visions of IoT often look like this
…but the reality can be more like this
‘It’s a bit glitchy but it’s OK, you just have to be in
the room at the same time’.
Actual review of a connected home system
Connectedness requires users to think
about system models
Which bit does what? Where does code run? What fails/still works if connectivity is lost?
You can explain the system model...
BERG Cloud bridge: transparent network comms
Or you can make
Users will get more
familiar with connected
products… but not for a
Interusability: coherent UX across the
Cross-Platform Service User Experience: A Field Study and an Initial Framework. Minna Wäljas, Katarina Segerståhl, Kaisa
Väänänen-Vainio-Mattila, Harri Oinas-Kukkonen MobileHCI'10
Functionality should be distributed to suit the context of use
Create device-appropriate interfaces that feel like a family
Dealing with latency, reliability and intermittent connections
BERG Cloudwash prototype
…has my action been executed or is it still in progress?
Has it worked? Why/why not? How will I know if it fails?