✎ PROBLEM STATEMENT & RESEARCH FOCUS

Analyzing the Steam Interface

Steam is a digital storefront and gaming platform developed by Valve Corporation. It launched in 2003 as a way for Valve to deliver updates to its own games and has since grown into the dominant marketplace for PC games, where players browse, buy, download, review, and discuss titles in one place. Its scale is enormous: in March 2025 the platform passed 40 million users online at the same time for the first time, and it has continued to set new concurrent-user records since.

In terms of design, Steam takes an approach where the game is always at the center. The site uses muted color palettes and a very simple design reminiscent of the early 2000s. In many ways this serves the user by keeping the focus on the product. However, it also makes Steam as a platform feel flat and uninviting. In most instances when a user clicks a button, they experience no interaction at all; they are simply moved on to the next leg of the journey.

This felt like a missed opportunity. As an ecommerce platform operating at this scale, Steam has a lot of room to explore how microinteractions might drive further engagement across its core channels, such as purchasing games, leaving reviews, and discovering new titles. I wanted to know:

✎ PICKING A PIECE OF THE INTERFACE

Why the wishlist tile?

I chose the Steam Wishlist tile specifically for two reasons:

From a business perspective, the wishlist is also one of the most direct links between a player's interest in a game and their decision to buy it. Players can wishlist both released games and upcoming ones, and Steam notifies them when a wishlisted game launches or goes on sale, so the list works as an ongoing bridge from "I want to hear more about this" to "I'm ready to buy." That link shows up in the data: industry analysis from GameDiscoverCo found that games typically sell about 15 copies in their first week for every 100 wishlists. That means wishlists do drive purchases, but most wishlisted interest doesn't convert right away. By bringing more joy into interaction, I saw an opportunity to keep wishlisted games feeling exciting and encourage more of that interest to turn into purchases.

✎ CURRENT STATE AUDIT

What happens when a user wishlists a game?

When a user wishlists a game on Steam, it gets added to their Wishlist tab, which is nested under both the store and their account. Within the wishlist, the user can:

• review the release date
• review the aggregate of the game's ratings
• browse the game's tags to find similar titles
• add the game to their cart directly to purchase it

Within each of these potential interactions, the user is given very little in terms of feedback. Clicking a button typically results in a simple state change, such as visiting a new page, with no transitional animation or hover effect. Beyond the tooltip popup and a slight color change when the user hovers over tags or the Add to Cart button, there is little to encourage exploration, engagement, or purchasing, and very little to indicate that the user is engaging with the platform as a whole (i.e. that their actions are doing something within the system).

Why are microinteractions important?

Nielsen Norman Group defines microinteractions as trigger-feedback pairs: a user action or system change (the trigger) followed by a small, contextual response in the interface (the feedback). Building on Dan Saffer's framework, they describe four jobs microinteractions do well:

Steam's wishlist largely skips the first and third. Visibility of system status is the very first of Nielsen's usability heuristics, and Jakob Nielsen's long-standing response-time research suggests that feedback within about 0.1 seconds is what makes an interface feel like it's reacting instantly to the user. When a click produces no visible response, users are left to wonder whether anything happened at all.

For a store like Steam, that silence is a cost. Every wishlist add, tag click, and cart action is a small signal of intent, and acknowledging it is a chance to build momentum toward a purchase. Within this interaction design, I sought to fill those two gaps: making sure every action on the tile gets an immediate, visible response, and turning that response into a small invitation to keep exploring, all without pulling focus from the games themselves.

To keep the interactions intentional, I structured the project around Dan Saffer’s microinteraction model, as guided by my instructor. For every element on the tile, I documented four things to guide building each interaction.

The result was a full specification covering eight components, from the wishlist card itself down to the modal’s close button. Writing the rules first meant every duration and scale value had a reason behind it, and gave me a checklist to build and test against. I then built the final prototype in HTML, CSS, and JavaScript, piecemeal.

✎ TAKEAWAYS AND FUTURE CONSIDERATIONS

What did Mack learn and what would she do next?

Designing within a rigid system turned out to be the most valuable constraint of the project. With color, layout, and components off the table, every decision had to come down to intent of the animations I was adding to each interaction. I had to think a lot about what would actually drive forward my goals of increasing joy and encouraging users to engage across core channels.