Services: that’s really what’s at the heart of the IoT (Internet of Things) device conversation and what makes the user experience (UX) design of IoT different.
Think of your first KISS (Killer Integration Services, Simple) as the beginning of a love affair with ubiquitous connectivity of devices and data exchange through the cloud.
The O'Reilly ebook Experience Design addresses IoT, explains how services are at the heart of the IoT user experience, and outlines other differences too.
Those services are made available via web APIs and developers and designers now need to approach UX by building UI services for task flows and fluid connectivity and not build hard-coded UIs.
Oyster Card for transport in London. No card actually necessary!
This UX Mag article summarizes the basics you need to know about what’s different about UX design for IoT. The London Oyster Travel Card is a great example of the IoT UX: You don’t even need the card to travel, you can use NFC and tap your smartphone at the ticket barrier to get to the trains, for example.
With that data is in the cloud and devices are connected, you’re good to go. Some of those “things” of course, don’t even have a UI!
You can read more about services and how APIs are UX design for IoT, PaaS, and SaaS on the Usable Apps blog.
Devs, it's time to heart APIs if you’re not already Oracle Cloud smitten.