IoT Hub

Mobile App · Internet of Things · Smart Home

How can design help everyday customers manage and secure the extensive amount of IoT devices in their homes?


Research Project | Fall 2018 to Present (Ongoing)

Professor Jason Hong

Client Intel

Teammate Se One Park, Antonio Song

My Role User Research and Testing, Concept Development, Re-design of UI, Partner with Engineers to Design Data Flow in Hub


The Internet of Things is rapidly growing as a market for consumer electronics and the IoT-ecosystem is becoming increasingly complex. However, there are a large host of challenges for making IoT work reliably in the home.

With continuous news on IoT cybercrime and the ever widening IoT eco-system, Intel and CMU CHIMPS Lab initiated this project to explore and design ways to enhance user control on IoT privacy and increase data security and transparency.

This is an ongoing research project mainly focuses on two problem areas:

cloud-computing (1).png


How can we make it easy for everyday users to manage dozens or hundreds of smart devices with different user interface (possibly no interface at all)?


How can we help people with little expertise manage the privacy and security of their devices, especially in the case of multiple users?


Design Proposal

We propose to design, build and evaluate an IoT Hub that offers services and functionality to help managing and securing IoT devices. The IoT Hub will make it easy to add, manage, connect, and secure Internet of Things devices in the context of homes, especially low-end devices that have minimal computational and networking capabilities.

The Hub will act like a smart WiFi router and operating system for connected IoT devices to offer common services such as:

  • access control for family members and guests

  • status and automated software updates

  • tracking battery usage and restricted network communication


Research Process

Background Research

To tackle the privacy issues with existing IoT eco-system and to discover design opportunities in frictionless interactions, I did background research and interviewed engineers regarding the intended back-end implementation of the IoT Hub to understand the technical limitations, specifically about the ways in which smart devices communicate with the network.

Scalability for the device network

The Hub will take simply a basic set of Metadata from each IoT device, as Metadata is lightweight and easy to adopt for both legacy and new IoT devices. Use a simple and minimal set of REST-based protocols to read the Metadata, the Hub can remain lightweight and easily scalable. These metadata include:

  1. Static: such as device manufacturer, serial ID, picture of the device

  2. Dynamic: such as battery life, device on or off

  3. User-set: such as name of device and location

Security for multiple devices and multi-user scenarios

The three features including static Metadata as well as proximity by default are used for security:

  1. Periodic software updates through IoT Hub with update URLs, as most vulnerabilities in devices are due to outdated softwares

  2. Utilizes Manufacturer Usage Description (MUD) as a whitelist with restricted websites an IoT device can access for manufacturers (or other entities) to specify normal behaviors for devices.

  3. Proximity by Default: users have to prove proximity to before they can access the Hub and devices, as unfettered remote access is a major source of security problems for IoT.

User Research

After background research and gathering information from previous designer about reasons behind key design decisions, we conducted card sorting and user interviews to examine previous insights about user behaviors.

During card sorting sessions, participants were provided with 40 smart devices that exist in different physical space in the context of a home (e.g. TV, thermometer, refrigerator, game consoles, etc).

Two questions are the main focus of this phase of the research:

  1. How do people organize and interact with numerous devices in the the context of home?

  2. What are the different access scenarios for families and guests and how can flexibility be achieved without compromising privacy and security?



Differ from previous findings that people associate devices based on their physical location, the card sorting shows that:

  • More people associate the devices based on their functionality, or with a physical space that stands for a type of functionality in the house such as kitchen or bathroom.

  • Users feel ambivalent about giving personal data to sensors and manufacturers


Based on the discoveries, to implement a relatively simple and effective approach that is easy to adopt and extensible, I created a flow chart that illustrates the process from on-boarding to managing devices, and to access control.

Untitled Diagram (1).jpg


Design Rationale

We incorporated Material Design because our client is Intel, and therefore the design needs to resemble an Android application.


We started out by designing the on-boarding experience to add devices and rooms to the IoT Hub, as this was not explored in the previous design. Then, we focused on improving the high fidelity UI design of the screens regarding viewing and managing the devices.

Account Registration with IoT Hub

The welcome screen introduces user to the IoT Hub application, and helps user set up a secure account.

Add devices.gif

Add Rooms

The user can then set up rooms that will be used to locate the smart devices via existing recommendations or adding a new room with customizable name and thumbnails.

Add Room.gif

Connect to Smart Devices

This features shows that the user can go into the specific room setup earlier and detect IoT devices in that location. Because of potential error of proximity, we build in manual editing for user to select from the detected devices about which ones to connect.

Add devices.gif

Device Management and Access Re-design

Home Page (typical).png

Home Screen

The re-design of the home screen features:

  • A clear information hierarchy with sectional organizations for different user actions based on priority.

  • Direct notifications for users about security and device status, which need immediate actions or attention

  • Easy control of simple and most used devices like lamp with a single toggle on the home screen

  • Activity logs allow user to view the activity histories of various devices sorted by function and help identify and locate abnormal activities for security.

Family Added.png
Add airbnb guest.png

Access Group and Adding Member

The access page is designed to accommodate different groups with various levels of access to devices granted by the admin user.

For security and privacy purpose, the default will be that new members have no access to any device. The device permission layer per guest allows admin user to grant access to each added member.

Device Permission

The device permission page is solely for managing device access for individual member. The admin user can grant access by rooms or functions, such flexibility comes in handy particularly for managing airbnb guest.

Interactive Prototype with Invision