Skip to content
Back to blogs

IoT user experience

TL;DR: IoT user experience connects physical actions with software feedback. Show what the system knows, when information was captured and what the person can do next. Include disconnected, delayed and recovery states in the design.
A macro photograph of the chips and connections on a physical circuit board

Photography by Yogesh Phuyal / Unsplash

In this article

Introduction

IoT user experience is the design of how people interact with connected devices and the software around them. A physical action, a device response and a screen update may happen at different times. The interface needs to explain those states without implying certainty it does not have.

Connect action and feedback

A button press does not always confirm that a device completed an action. Separate the requested action, the device’s reported state and what the interface can currently verify.

For a dashboard, the age of a reading can matter as much as the value. For a connected game, the timing of feedback changes how people understand the next move. Design around the operating task.

Make device states clear

Use status labels that match the implementation. Explain whether information is current, delayed or unavailable, and keep recovery actions understandable.

  • Environment: where the device is used and what else is happening around it.
  • State: whether the device, connection and software are ready for the next action.
  • Information: what a value represents and whether it is current for the task.
  • Feedback: how people recognise the response to a physical action.
  • Recovery: what someone can do when the expected response does not arrive.

Design for the setting

Consider the device, interface and physical environment together. Input from operators and hardware engineers helps the team identify interruptions and constraints that a screen prototype may miss.

Begin with the setting

Understand where the product will be used and what people need to do around it. Light, noise, movement, connectivity and the distance from a display can affect how an interaction works. Observe the setting where possible and ask the people doing the work how the current process operates.

Include interruptions in the scenario. A person may leave the screen, change tasks or return after another operator has used the system. Decide what they need to see to understand the current situation. The starting point should be the work itself rather than a dashboard layout chosen in isolation.

Separate the states people need to understand

A device being connected does not necessarily mean a requested action has completed. A value being visible does not necessarily mean it has just been captured. Work with the technical team to identify the states the interface can describe accurately, then choose language that explains them without implying more certainty than the system has.

Show the context required for a useful decision. Depending on the task, that may include a timestamp, an identified device, a pending action or a clear status. Avoid overwhelming the person with internal details that do not help them operate the product. Keep the distinction between observation and action understandable.

Design feedback and recovery together

After a physical action, someone needs a clear indication of what the system registered and what happens next. Review the timing and wording of that feedback with realistic interactions. A useful response should help the person continue without needing to infer the state from an unrelated visual effect.

Plan what happens if the expected response does not arrive. Explain the known situation and provide the appropriate next action, such as checking a connection or reviewing a pending request. Recovery should follow the actual system’s capabilities and the operator’s responsibilities, with specialist decisions left to the people qualified to make them.

Connect system state with useful interface feedback
SituationWhat the person needs to understandDesign question
Action requestedWhether the request was registeredCan the interface distinguish pending from completed?
Information displayedWhich device and point in time it describesIs the information current enough for this task?
Connection interruptedWhat is known and what is unavailableWhat can the person appropriately do next?
Returning to the productThe current state and relevant changesCan someone resume without reconstructing the whole history?

Review a connected task

Walk through a task with realistic device behaviour, including delays and lost connections. Check the information, controls and recovery route at each stage.

  1. Describe the physical task. Record who uses the product, where it is used and what the person is trying to accomplish. Include any other people who act on the information.
  2. Map the information exchange. Follow the input through the device and software to the feedback shown. Identify what the system can know at each point.
  3. List important states. Document ordinary, pending, unavailable and interrupted situations. Agree on which distinctions matter to the operator’s next decision.
  4. Review labels and context. Check whether values, device names, timestamps and actions are understandable together. Remove unnecessary internal terminology while preserving information needed for the task.
  5. Test the return and recovery journeys. Try interrupted interactions and a return after time away. Confirm that the interface explains the state and the appropriate way to continue.

Avoid misleading feedback

Avoid presenting a request as a completed physical action or an old reading as a live one. Review every state against what the connected system can actually confirm.

  • Showing a last-known value without enough context for someone to understand its relevance.
  • Treating connected, ready, requested and completed as interchangeable statuses.
  • Designing a dashboard without observing the setting or the people responsible for operating it.
  • Leaving interruptions and recovery to generic messages that do not explain the actual state.
  • Promising a real-time response or a specific capability without checking the implementation and operating conditions.

Frequently asked questions

How is IoT user experience different from ordinary app design?

An IoT experience connects the interface with a physical device and the environment around it. Device state, connection state and information freshness can affect what the person should understand. App design principles still apply, with those additional relationships considered in the task.

What should a connected-product dashboard show?

Show the information and controls needed for the operator’s decisions. That may include identified devices, useful statuses and context about when information was captured. The exact content should follow the task and what the system can confirm.

How should an interface handle a lost connection?

Explain what is known, what is unavailable and the appropriate next action for the person using the product. The wording and controls must match the actual implementation. Review the recovery journey with the technical and operational teams.

Can IoT interface design be done before the hardware is ready?

Early task mapping and prototypes can help clarify requirements. The team still needs to review the experience against real device behaviour and operating conditions. Keep assumptions visible so an early prototype is not mistaken for verified system behaviour.

What affects the scope of a connected-product project?

The task, devices, integrations, environment and operational requirements all shape the work. Interface design needs input from the people responsible for the hardware and software. Share those constraints early so the first release can be planned around a clear use case.

Conclusion

A useful connected experience explains the relationship between the device, the information and the next action. Plan for interruptions alongside normal use. Our IoT services and Vulkan Darts project provide related examples.

Sources and further reading

All articles

Let’s make a start

Tell us what
you have in mind.

Choose a service to start the conversation.

Continue with AI development & generative AI