"Designing for the Internet of Things" entries
Productive critique can strengthen relationships and collaboration, improve productivity, and lead to better designs.
Download a free copy of Designing for the Internet of Things, a curated collection of chapters from the O’Reilly Design library. This post is an excerpt from Discussing Design, by Adam Connor and Aaron Irizarry, one of the books included in the curated collection.
There are two sides, or roles, in any critique:
Recipient: The individual(s) receiving the critique (i.e. the creator or presenter of whatever is being analyzed) who will take the perspectives and information raised during the critique, process it, and act upon it in some way.
Giver: The individual(s) giving the critique, who are being asked to think critically about the creation and provide their thoughts and perspectives.
Within both of these roles, there is the discrete aspect of intention: why are we asking for/receiving/giving feedback. Intent is the initiator of the conversation and is often what separates successful critiques and feedback discussions from problematic ones.
For the best discussions, the intent of each participant, regardless of whether they are receiving or giving critique, needs to be appropriate. If we aren’t careful, critique with the wrong, or inappropriate, intent on either side can lead to problems not only in our designs, but also in our ability to work with our teammates. Read more…
Designers need to create a coherent UX across all the devices with which a user interacts.
Editor’s note: This is an excerpt by Claire Rowland from our upcoming book Designing Connected Products. This excerpt is included in our curated collection of chapters from the O’Reilly Design library. Download a free copy of the Designing for the Internet of Things ebook here.
In systems where functionality and interactions are distributed across more than one device, it’s not enough to design individual UIs in isolation. Designers need to create a coherent UX across all the devices with which the user interacts. That means thinking about how UIs work together to create a coherent understanding of the overall system, and how the user may move between using different devices.
Cross-platform UX and usabilityMany of the tools of UX design and HCI originate from a time when an interaction was usually a single user using a single device. This was almost always a desktop computer, which they’d be using to complete a work-like task, giving it more or less their full attention.
The reality of our digital lives moved on from this long ago. Many of us own multiple Internet-capable devices, such as smartphones, tablets, and connected TVs, used for leisure as well as for work. They have different form factors; may be used in different contexts; and some of them come with specific sensing capabilities, such as mobile location.
Cross-platform UX is an area of huge interest to the practitioner community. But academic researchers have given little attention to defining the properties of good cross-platform UX. This has left a gap between practice and theory that needs addressing.
In industry practice, cross-platform UX has often proceeded device by device. Designers begin with a key reference device and subsequent interfaces are treated as adaptations. In the early days of smartphones, this reference device was often the desktop. In recent years, the “mobile first” approach has encouraged us to start with mobile Web or apps as a way to focus on optimizing key functionality and minimize “feature-itis.” Such services usually have overarching design guidelines spanning all platforms to ensure a degree of consistency. The aim is usually on making the different interfaces feel like a family, rather than on making the devices work together as a system. Read more…
Consumers are more aware of connected devices, but they need to be convinced a product will do something valuable for them.
Editor’s note: This is an excerpt by Claire Rowland from our upcoming book Designing Connected Products. This excerpt is included in our curated collection of chapters from the O’Reilly Design library, Designing for the Internet of Things.In 1962, the sociologist Everett Rogers introduced the idea of the technology lifecycle adoption curve, based on studies in agriculture. Rogers proposed that technologies are adopted in successive phases by different audience groups, based on a bell curve. This theory has gained wide traction in the technology industry. Successive thinkers have built upon it, such as the organizational consultant Geoffrey Moore in his book Crossing the Chasm.
In Rogers’ model, the early market for a product is composed of innovators (or technology enthusiasts) and early adopters. These people are inherently interested in the technology and willing to invest a lot of effort in getting the product to work for them. Innovators, especially, might be willing to accept a product with flaws as long as it represents a significant or interesting new idea.
The next two groups — the early and late majority — represent the mainstream market. Early majority users might take a chance on a new product if they have seen it used successfully by others whom they know personally. Late majority users are skeptical and will adopt a product only after seeing that the majority of other people are already doing so. Both groups are primarily interested in what the product can do for them, unwilling to invest significant time or effort in getting it to work, and intolerant of flaws. Different individuals can be in different groups for different types of product. A consumer could be an early adopter of video game consoles, but a late majority customer for microwave ovens. Read more…
The growing complexity of design and architecture will require a new definition of design foundations, practice, and theory.
Editor’s note: This is an excerpt by Matt Nish-Lapidus from our recent book Designing for Emerging Technologies, a collection of works by several authors and edited by Jon Follett. This excerpt is included in our curated collection of chapters from the O’Reilly Design library. Download a free copy of the Designing for the Internet of Things ebook here.Bruce Sterling wrote in Shaping Things that the world is becoming increasingly connected, and the devices by which we are connecting are becoming smarter and more self aware. When every object in our environment contains data collection, communication, and interactive technology, how do we as human beings learn how to navigate all of this new information? We need new tools as designers — and humans — to work with all of this information and the new devices that create, consume, and store it.
Today, there’s a good chance that your car can park itself. Your phone likely knows where you are. You can walk through the interiors of famous buildings on the web. Everything around us is constantly collecting data, running algorithms, calculating outcomes, and accumulating more raw data than we can handle.
We all carry minicomputers in our pockets, often more than one; public and private infrastructure collects terabytes of data every minute; and personal analytics has become so commonplace that it’s more conspicuous to not collect data about yourself than to record every waking moment. In many ways, we’ve moved beyond Malcolm McCullough’s ideas of ubiquitous computing put forth in Digital Ground and into a world in which computing isn’t only ubiquitous and invisible, but pervasive, constant, and deeply embedded in our everyday lives. Read more…