Skip to main content

Device-Agnostic Experiences

Recently I have seen some writers talk about what is new in interaction design. There are many suggestions, such as storytelling. voice-first design, frameless experiences, augmented reality, emotional design, transparency design, systems design. Most of these are quite obvious and we will probably see more of them these coming years.

I just want to comment on one trend that I have seen mentioned here and there. The basic idea is that any design should seamlessly function on any device or system. This sounds all good to a user who can move freely between technologies and devices and still use the same functionality, only with different interaction modalities. We have seen this idea being implemented for many years already, for instance, in how websites have been designed to also work on smartphones.

Even though the idea is easy to support it leads to some serious design challenges that are not always addressed. I will mention two issues.

First, the idea is based on the assumption that any functionality is possible to perform given any technology, for instance, that voice interaction is just another form of interaction but can perform what direct manipulation can do. This is maybe possible, but it can lead to increasingly complex interactions that make no sense to a user. Each device (technology) supports and lends itself to certain actions and interactions and not to others.

Secondly, to be device-agnostic easily leads to complexity on the level of systems. What devices should be included in the "agnostic" design? And which ones do not have to be included? We live with a large number of devices, from traditional computers to cars, appliances, home equipment, tools, games, TV, etc. What functionality needs to be available on what devices? It is not only a question of what agnostic design that can be done, but also which ones are appropriate. When does it lead to crowded and cluttered interactive devices?

This is of course an old challenge that designers have struggled with for a long time. There has always been a conflict between those who argue for specialized devices with particular focus and functionality and those who argue for general devices that combine a broad spectrum of functionality. We can see that fight in the HiFi industry, in kitchen appliances, woodworking tools, etc. 

So, the question is not if device-agnostic design is good or bad, but when is it appropriate and when is it not. Maybe some functionality should be left to one, and only one, device, while others can be spread across a spectrum of devices.

Comments