Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy.

Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our Privacy Policy and User Agreement for details.

4.
http://www.digitaltrends.com/home/heck-internet-things-dont-yet/
- …
Visions of IoT often look like this

5.
…but the reality is often new ways to fail
‘It’s a bit glitchy but it’s OK, you just have to be in the
room at the same time’.
Actual review of the Wink hub

6.
State of play
•Technology is still maturing
•Lots of products of dubious value
(especially in consumer realm)
•Interoperability is poor
•Software and physical things are very
different in terms of product
development and user expectations
•We’re still ﬁguring out business
models, security and privacy
“We are experiencing some
minor difﬁculties with a 3rd
party server.”
petnet.com

16.
Myth 2:
Zero UI is feasible and
desirable
“Ubiquitous systems must contain
provisions for immediate and transparent
querying of their ownership, use, and
capabilities. Everyware must, in other
words, be self-disclosing. Whether such
disclosures are made graphically, or
otherwise, they ensure that you are
empowered to make informed decisions as
to the level of exposure you wish to
entertain.”
Adam Greenﬁeld (2006)

19.
The process is very
different from
digital
seymourpowell.com
Practical and technical things
considered at the same time as
aesthetics and ‘superﬁcial’ things like
branding, visual impact etc.
Extra considerations for connected
things: not blocking radio signals,
ﬁtting in electronics, adequate power

24.
Continuity
- The ﬂow of interactions and
data in a coherent sequence
across devices
- Continuity helps the user feel
as if they are interacting with
the service, not a bunch of
separate devices
Image: Kei Noguchi via CC licence

43.
•If APIs are too coarse you can’t get
the detail
•If they’re too granular, you’ll have to
make lots of calls and do front end
processing: this can be slow and risk
inconsistencies
•If they’re the wrong structure this
can also slow things down
You can’t create
the right UX
without the right
APIs
“Uh, that new
homescreen of yours
is about 150 API calls
on our current
platform”

44.
•App
•Cloud service
•Device ﬁrmware/software
•You need to know who to talk to
about the functionality you want to
build
UX decisions can
impact code all over
the system
Room:“kitchen”
Device:“oven”

46.
1. Data about device capabilities
To be smart we need:
•I’m a lightbulb
•I can be on or off
•I can be x% dimmed
•I can support x colours
•My brightness is measured in
lumens
•I have been on for 600 seconds
•I have used 10 Watt hours since
my last reset

47.
2. Data about the context of speciﬁc devices
•I’m in the living room
•I’m being used in the ﬂoor lamp