Player and Avatar: Video Game Interactions For Web UX Designers

Technology users tend to form surprisingly social and personal relationships with their technologies, and with good reason. Gamers and their avatars are one specific example of the social relationship between a user and an interface, whether on a game as simple as Mario Brothers or as complex as Second Life. As UX designers, we can benefit by understanding the (potential) sociality of the user-interface dynamic.

Interfaces are an increasingly present part of modern digital life, and they govern how users interact with and use their various technologies. And, as we havepreviously discussed, users have an ability to form surprisingly social relationships with their technologies. Both Nick and Jamie (the authors of this piece) have long been interested in these relationships, and as researchers at West Virginia University, we were seeking out a place to focus our research. We chose video games.

To consider the role constraints and affordances play in human-technology relationships (as discussed in our last piece), we decided to hone in more specifically on video games and the avatars within.

In gaming, players are often asked to create an avatar—a visual representation of themselves in the game world. The natural assumption is that players are motivated to create an avatar that represents some aspect of their personality (with some embellishment).

Image of the authors as their World of Warcraft avatars. They're both pandas. And awesome.

As a rookie player, Nick sees his World of Warcraft avatar as a basic tool for playing video games: panda smash bad guys. Jaime, a veteran player, carefully crafts her avatar as unique and separate personality: panda on a mission.

Social scientists long assumed that players would psychologically merge with their avatars, allowing a player to feel like she is a part of the game world. The interfaces of most popular games encourage this, providing players with numerous options to customize the look and feel of the avatar, and often providing the player with near-complete control of the avatar’s actions. For these reasons, video games are considered by some to be one of the best examples of effective UX design. For our research, we also wonder if video games might also represent one of the best environments for better understanding the complicated social interactions between users and technologies.

Player-Avatar Relationships, Explained

Over the past few years, our research team has interviewed and surveyed over 3,000 video game players across a number of different studies focused at understanding the different types of relationships that players have with avatars, from the non-customizable to the fully user-created. We’ve found four basic relationship types:

  • Avatar as Object, in which one tends to see an avatar as a tool or a game piece in order to focus on winning or accomplishing in-game achievements. A good example of this would be a case where someone is playing Tetris. In this game, the player controls a series of falling colorful shapes, arranging them so that they fit together. These shapes are little more than two-dimensional collections of pixels, rather than authentic extensions and representations of the player’s persona.
  • Avatar as Me, in which one tends to see an avatar as an extension or representation of oneself, usually to connect with friends or strangers in a game. Consider game play in Second Life, in which many players go through painstaking measures to perfectly create a highly personal (and even, idealized) representation in the digital world.
  • Avatar as Symbiote, in which one tends to see themselves and their avatar as part of each other, often in an effort to work through personal challenges or solve problems. For instance, some people play characters in World of Warcraft to deal with identity and mental health concerns.
  • Avatar as Other, in which one tends to see their avatar as a separate social agent and a partner in play, usually to become more immersed in the game world. In the indie game Super Meat Boy, the player controls Meat Boy (a cube-shaped lump of flesh) and tries to help him rescue his girlfriend, Bandage Girl. Despite controlling the avatar, his cubic, monster-like appearance, abilities that go beyond human skills, and the portrayal of his own emotions and motivations may lead players to see him as a being in his own right.

Meat Boy, a cube-shaped lump of flesh, still feels human.

The ordering of these four types is important, as it relates to how social the player-avatar relationship (or human-technology relationship, broadly) is perceived by the human user. “Object” relationships are decidedly non-social, with very little emotional investment and a high sense of control. Conversely, “Other” relationships very much resemble fully social relationships, with a high level of emotional investment and a sense that the avatar (or technology) is its own being; these relationships are also marked by a perception that the avatar (technology) is in control of the interaction. This “Other” orientation is especially interesting, because it closely resembles what family psychologist Murray Bowen referred to as self-differentiation—the practice of seeing others as distinct from one’s self that is crucial to the development of empathy and close social bonds. In our last article, the archetypes of the Gatekeeper, Editor, and Vender are just a few of the “Other” relationships that might exist – each being an example of an interface that has taken on a persona of its own, for a very unique application.

Illustration explaining a scale of social to nonsocial relationships in technology. It's very scientific.

The type of relationship that people have with technology (here, avatars) depends on: how much they care for it, how much they see it as “human,” how much they see it as real, and how much control they have over it. For more information, read our latest research on player-avatar relationships.

Relationship Types in Interaction Design

We might ask how the socialness of a user-interface experience comes out of how the interface is designed for the end user. We outlined a few examples in a recent book chapter on social media applications and design, but summarize some connections here.

“Object” Orientations

Designers might aim for simple and lean designs, with few to no social cues built into them. Such interfaces might have very discrete functions and tasks, such as a basic password field or simple database. Simple designs allow users to feel more in control of the user experience. They also help users feel less attached to a given interface, as they’re more likely to be attached only to efficiencies and functions, rather than to the interface as a character-like agent. Object-oriented design places focus on efficiency and functionality, usually for short-term (and even one-time use) interactions.

“Me” Orientations

Designers should consider that the entire experience should be about customization and identification—design with the specific goal of featuring the user. Options for personalization can start at the most basic level (such as screen names and pictures), but can be broadened to include more transparent functions that recognize trends in user behaviors to effectively anticipate, automate, and extend the user intentions and use cases. “Me” interfaces should be perceived as natural extensions of the user’s personality, and might even try to “get to know the user” and customize accordingly.

“Symbiotic” Orientations

Efficient and meaningful use might be the intersection of human and technological abilities where the technology may compensate for the shortcomings of the user (e.g., efficiencies, accuracy, physical endurance), and the user may compensate for shortcomings of the technology (e.g., creativity, semantic interpretation, empathy). For instance, we might consider that a big-data analysis platform that streamlines tasks that human users aren’t very good at (e.g., complex calculations with large data sets) could also incorporate tools for tasks that computers aren’t very good at (contextualizing and interpreting that data in meaningful ways).

“Other” Orientations

This orientation requires a design that gives the interface its own sense of agency and human-likeness by removing a significant amount of human control and augmenting functional attributes with social attributes. In other words, adding human cues like voices, representations of faces and gestures, forms of embodied movement, natural language processing and other forms of artificial intelligence. Such design may move people to have more natural, meaningful, emotional, and cooperative interactions with technologies. Interfaces such as the voice-activated (and oft-sassy) Siri are great examples of technologies that encourage users to form a kinship with the platform (as uncanny as this can be).

What This All Means

Given the amount of time that many of us spend with our digital technologies and how seamlessly we’ve integrated technological interfaces into our daily lives, it’s no surprise that the relationship between user and interface can be surprisingly social. Understanding the potential for such social relationships might help designers better craft experiences and interfaces that can respond in kind. A great example of designing with sociality in mind is Apple’s recent changes to Siri’s responses to questions regarding domestic violence and sexual assault—socially distant “Object” responses such as “I don’t understand” or “I don’t know what you mean” have been replaced with more socially authentic responses, showing compassion and directing users to critical resources.

We should note that the possibility for social relationships should not be interpreted as us suggesting that all user interfaces should be social. Rather, we’ll end with a few questions that UX designers might ask themselves:

  • Would the interface benefit from a social relationship? UX designers should consider whether or not an interface would be easier to engage if it had a more human-like “feel” to it. Voice-recognition and other naturally mapped interfaces might benefit, while text and other cue-lean interfaces might not.
  • Would the task at hand benefit from a social relationship? Designers might consider the nature of the task itself. For example, an interface that requires the user to trust the program with personal details might benefit from a trusting social relationships, but such an association might be a bit too much for searching gas prices or airline prices.
  • Would the end-user benefit from a social relationship? While most of us like to have friends and to engage in conversations, not all users will feel comfortable answering tough personal questions from an apartment that is falling in love with us.