Portable Ops

Context

“Portable Ops” is an action-packed shooter game crafted and brought to life by my brother and me alone. Available for PC on Steam and soon to hit Xbox (release date to be determined), this adrenaline-fueled adventure puts you in the shoes of a mercenary soldier for hire, navigating the challenges of the modern era. With both single-player and multiplayer modes, you can experience intense combat from either a first-person or third-person perspective, offering endless possibilities for thrilling gameplay.

Role

UI designer

Map designer

Special feature programmer

Video creator

Duration

October 2022 – November 2023

Tools

Unreal Engine 5 figma logo Figma

Adobe Illustrator Adobe Photoshop

Summary

Action shooters are known for their high-speed gameplay, where split-second decisions are crucial amidst constant gunfire and objectives. However, amidst the chaos, players still require essential information to understand the world’s situation. While some details need to be readily accessible, others may not be constantly needed but remain vital for informed gameplay.

How do we achieve the goal of giving enough UI but not so much it becomes clutter to the player?

To find the answer, we started by asking the question:

What UI is important to the player at a specific point in time?

The final solution is shown below – read on for more in depth look at the process.

Final Design

Project Goals

Design a spacious, open view for players while providing essential information.
Enhance team interaction through on-screen notifications.
Display the player’s progress clearly and succinctly to promote replayability.

Project Process

To accomlish our goals, we used an iterative design process.

Planning and Requirements: Initially, the requirements lacked clarity, with certain information presumed necessary but ultimately overlooked by players during gameplay. Consequently, we conducted testing sessions to gauge actual usage during casual play.

Analysis and Design: We devised interfaces we deemed essential or aesthetically appealing, drawing inspiration from established conventions in classic and contemporary shooters.

Implementation: The new interfaces were integrated alongside major updates, allowing for ample feedback periods between iterations.

Testing: Through announced testing sessions on Discord, we assembled small groups comprising individuals who had provided valuable feedback previously, as well as new players for fresh insights. Session recordings facilitated subsequent evaluation and review.

Evaluation and Review: While many iterations yielded positive responses, some changes proved insufficient or went unnoticed, shedding light on players’ focal points during gameplay versus interface feedback. Adopting a strategy of incremental adjustments, we tested various interface setups over weeks, sometimes opting for removal to streamline the experience and prevent information overload—from excess to just the right amount.

User Play Testing the UI

We sought input from players early in the development process. However, since the game hadn’t been released yet, we needed to actively recruit testers. After analyzing Steam charts and conducting third-party genre research, we targeted PC gamers aged 30-50 who play shooter games at least twice a week, have a preference for realism and military themes, and are active in other gaming communities.

To find these players, we searched through existing Call of Duty, America’s Army, and SOCOM gaming groups. After obtaining permission from group leaders, we reached out to offer the opportunity to participate in the Portable Ops beta testing phase.

Recruits were invited to join the Portable Ops Discord Channel, where they received an introduction to the game, and individual and group testing sessions were scheduled. During these sessions, my brother and I observed as the players engaged in matches, providing vocal feedback via Discord. We also recorded numerous sessions for later evaluation, focusing on details and transitional actions.

UI Research

We categorized elements based on two standards: “Immediately” and “Eventually.” This classification distinguishes between information crucial for the current moment or else the player risks losing out, versus information that the player may want to access but has the luxury of time to search for.

Immediately Necessary

Damage Inflicted: Players requested instant feedback regarding the damage dealt to enemies.

Action Required: Players appeared to lose track of crucial issues like running out of ammo. Initially, we aimed for immersive gameplay by providing minimal information. However, this led to the opposite effect, as players struggled to keep track of their ammo and weapon status. To address this, we positioned the information off to the side but ensured it remained constantly visible.

Eventually Necessary

Damage Taken: Players experiencing bleeding out struggled to understand why their health was depleting. Furthermore, once they realized the cause, they often found it challenging to recall how to heal themselves amidst the intensity of combat. Although bleeding wasn’t immediately fatal, its eventual lethality demanded prompt attention. To address this, reminders of bleeding status were displayed only when necessary to heal.

Search Bodies: Players have the option to scavenge bodies for ammo and supplies. Instead of persistently reminding players, the search option and corresponding key prompt are displayed only when directly facing a body. This approach maintains focus on combat during engagements and exposes players to potential attacks while replenishing supplies, adding a tactical dimension to survival.

Objectives: Players required reminders about current objective status, but constant updates were distracting. Displaying objective data only when necessary helped declutter the screen. Eventually, objective status was integrated with the compass, aiding players in orienting themselves and communicating objectives to teammates.

Generative Brainstorm

We utilized online collaboration through Discord sessions to efficiently share our thoughts and suggestions regarding interface changes. Throughout numerous iterations, we primarily focused on implementing subtle adjustments in each version.

User Interface – Streamlining

In the end, we opted for an incredibly streamlined interface that facilitated smoother gameplay immersion for the players. They appreciated feeling a greater sense of purpose in their in-game roles. It was a win-win situation!

Version 3

Final Version

UI / UX Aftermatch – What’s Next?

We observed that after matches, players were often uncertain about their next steps. Questions arose about whether they should search for a new match and what had happened to their unlocks. We aimed to showcase player progression while also emphasizing the significance of their unlocks in a straightforward manner.

To address this, we opted to provide clear explanations of their acquired items rather than leaving players to explore their characters for new additions.

Version 1

Final Version

Impact

After countless iterations and revisions, I’m confident that our ultimate interface effectively communicates crucial information in a seamless and polished manner. The complaints and troubleshooting concerns raised by our playtesters vanished once they were able to easily access the information that had previously been unclear.

A surprising revelation for me was that the majority of players were not interested in intricate details. They simply wanted assurance of their progress and clear instructions on accessing their unlocks. The specifics of how or why seemed irrelevant to them. With this insight, our playtesters began spending the majority of their test game time actually playing!

Design elements in this FPS game

. . .

Mobile Casino style game in Mario Style

. . .

Classic UI for Card collection game

. . .