Designing interaction for Interaction of Things. Differences between designing for digital and designing for Internet of Things. Useful methods. Challenges posed by a mix of digital and physical.
Användbarhetsboken/The usability book • Worked in Internet of Things projects for smart offices and heart monitoring • Writing a book on Internet of Things
system • Input directly from physical reality (GPS-position of bus) • Acts directly on physical reality (once we have self driving buses) • Interface adapted the situation
reality themselves • …and output—systems will act on physical reality themselves • Essential parts of UX ”hidden” in the model (if the model is not correct, it cripples user experience) • More information & interaction • …in the most appropriate form, when needed, using the most efficient channel
Google • Marketing • It is assumed that collecting a lot of data atomagically will produce knowledge • Optimization of products, workflows and organisations
• Typically asynchronous – results of the analyze is not used in the situation • Marketing (learn about the user) • Optimization • Monitoring & Maintanance (including many health applications) • Typically totally dependent of the Internet
to act. The user is the actuator. • Shopping. Your history and how you move in the store effects what offers are shown on in store screens—and on the web
A symbol of the future • Attracts early adapters, for whom the technology is the value • Early success can be a trap • Early adapters likes to configure & are willing to invest time • Mainstream consumers are not
get an idea like this, if you start with user needs • Possibility-driven design • When technology develops rapidly, user needs can not be the creative driver
same time? • Social context—other people can often see you when using a thing • Shared usage—things are often used by several persons • A swarm of things—your thing is not the only one wanting the users attention
of a larger context or service • Medical • iBeacons (in-store offerings on the phone) • Service design & touchpoint maps are methods to cover the full context
Internet of Things-thing • You can see if there is any coffee, before you go to the kitchen • But—new coffee is mostly made by someone who comes to the kitchen and discover that there is none • Result: Empty most of the time • We’re not designing things, we’re designing systems
dependencies (specially for consumer products) • Christmas • Production slots • Features (described in documentation, retailer info, marketing material etc.) • Continuous development hard • Distinct product generations (the marketing logic of something new and shiny)
• We all carry a remotely readable barcode: our phone • Used when identity of the user is needed • Example: The heater in your house starts working when you are on your way home
many things every day • Solution: Zero interface. No interaction, it just works • Sometimes the user is not even aware • (Topp, here in Malmö, is an active proponent of this ideal) • But, to be quiet is to be forgotten • Will brand managers accept that their products do not attract attention? (Anti-virus do not need to, but do)
Works well if you have only a few things. • But, does not scale With many things, will you remember them? • Will gestures be a common interface? • My guess: No.
appears to be alive • Soldiers in Iraq did not only name their robots, they formed emotional bounds to them. There were incidents when soldiers risked their lives to save their robot.
The computer/smart phone way: Throw away hardware after 2-4 years • Can smart recycling make this viable? • The set top box way: Loose coupling. Switch box every other year, keep screen
(physical) designer’s culture: • No errors • Late changes or recalls is extremely expensive • The digital designer’s culture: • Time to market • No need to be perfect, better get experience and fix it in next version.
with Sara. Your refrigerator has checked with Saras refrigerator for allergies and preferences, and ordered the ingredients for a romantic dinner. Your car informs the house that you will arrive in 30 minutes, and the oven…
with Sara. Your refrigerator has checked with Saras refrigerator for allergies and preferences, and ordered the ingredients for a romantic dinner. Your car informs the house that you will arrive in 30 minutes, and the oven… Will not happen
When is it ok to spy on the user? • Internet of Things will observe our lives in greater detail then Stasi ever did. Do we always have to know this much about our users? • Is a blockchain (Bitcoin) model a feasible way to build Internet of Things?
Licensed by Google creative commons. Muscles Natalie Prigozhina. Creative Commons Attribution License Telephone Smartphone Italia. Cative Commons Processor/Model Diagrams …a team Image with many things: Mark Moz. Creative Commons Big Data – User StormSignal. Creative Commons Zoltar – Engages the user MagicNumberSix Super Powers Xurble Creative Commons Attribution 2.0 Agile philosophy kk+ Creative Commons 2.0 (by-nc-sa) Sea turtle Brocken Inaglory CC BY-SA 3.0 One thing Shindigz Party Creative Commons