OVERVIEW

MTG Response Assistant

Making complex gameplay interactions easier to understand.

A UX/HCI project exploring how a mobile companion interface can help Magic: The Gathering players understand priority, navigate the stack, and communicate decisions during gameplay.

IMAGE PLACEHOLDER

High-fidelity prototype overview

Your authentic MTG Response Assistant screens will be featured here.

Role

UX Researcher & Designer

Focus

Interaction Design, Gameplay Usability, Information Architecture

Tools

Figma

Deliverable

Interactive Mobile Prototype

View Interactive Prototype

High-fidelity prototype completed · Three-participant usability evaluation · Participant-informed revisions ready for follow-up testing.

01 / Problem

02 / User Research

03 / Design Opportunity

04 / Concept Exploration

05 / Concept Testing

06 / Wireframes

07 / High-Fidelity Prototype

08 / Usability Testing

01 PROBLEM

When complex rules interrupt the experience

Magic: The Gathering has sophisticated rules governing spells, abilities, the stack, and priority. Keeping track of these mechanics can place significant demands on attention and working memory, particularly for newer players.

Unclear response opportunities

Players may not recognize when they have priority or when they are allowed to respond to a spell.

Difficulty understanding the stack

Players must mentally track multiple spells and abilities, including their order of resolution.

Communication ambiguity

An exchange such as “Okay” can mean different things, leaving it unclear whether a player is passing priority.

THE DESIGN QUESTION

How might we help Magic players recognize response opportunities, understand spell resolution, and communicate gameplay decisions more clearly?

02 USER RESEARCH

Understanding player challenges

I conducted six user interviews to explore how players experience and navigate complex Magic interactions.

The interviews explored priority and response windows, tracking spells and abilities on the stack, communicating intentions, moments of uncertainty, and existing strategies for managing complicated interactions.

Visibility

Players benefit from clear indicators of what is currently happening.

Mental workload

Tracking multiple interactions requires attention and working memory.

Communication

Clear, explicit actions can reduce misunderstandings during gameplay.

These are qualitative themes from the interviews—not statistical findings or measured usability outcomes.

IMAGE PLACEHOLDER

Interview notes & thematic synthesis

Space for original interview notes, an affinity diagram, or other research artifacts.

03 DESIGN OPPORTUNITY

From player frustrations to design opportunities

The research pointed toward a lightweight companion tool: one that clarifies interactions without replacing the physical card game.

Make priority visible

Clearly identify whose turn it is and which player currently has priority.

Visualize resolution order

Represent the stack so players can understand which spell resolves first.

Make decisions explicit

Provide clear choices for responding, passing priority, and understanding what changes.

04 CONCEPT EXPLORATION

Exploring different approaches

I developed three initial design concepts to explore alternative ways of guiding players through complicated interactions and reducing confusion.

IMAGE PLACEHOLDER

Concept 01

Original concept sketch or wireframe.

IMAGE PLACEHOLDER

Concept 02

Original concept sketch or wireframe.

IMAGE PLACEHOLDER

Concept 03

Original concept sketch or wireframe.

The selected direction was a communication and resolution assistant that brings explicit player actions, priority indicators, and a visual stack together.

05 CONCEPT TESTING

Choosing a direction

Initial concept testing informed the selection of the Response Assistant approach. The chosen direction focuses on clear response windows, explicit Respond and Pass Priority actions, visual stack updates, player-by-player status, and understandable resolution outcomes.

DESIGN RATIONALE

Rather than replacing the tabletop experience, the solution provides contextual guidance at moments when players need clarity.

IMAGE PLACEHOLDER

Concept testing evidence

Space for original feedback, comparison images, or testing documentation.

Detailed concept-testing evidence has not yet been added to this page. No numerical results or participant quotations are reported here.

06 WIREFRAMES

Turning the interaction into a flow

The early wireframes explored a six-screen scenario: an opponent casts Lightning Bolt, and the player responds with Counterspell. This sequence helped establish the information hierarchy and overall flow before visual refinement.

Original six-screen MTG Response Assistant wireframes showing spell cast, response window, choose response, stack updated, waiting for players, and resolution.

Original low-fidelity exploration: spell cast, response window, choosing a response, stack updates, player waiting states, and resolution. Select the image to view it full size.

07 HIGH FIDELITY

Making the invisible visible

I created a high-fidelity mobile prototype with a dark interface, purple interaction highlights, differentiated stack cards, and explicit player-status indicators. These treatments are part of the app prototype; the case study retains the portfolio’s visual language.

01 — Opponent Cast

MTG Response Assistant: Opponent Cast

02 — Response Window Open

MTG Response Assistant: Response Window Open

03 — Choose Response

MTG Response Assistant: Choose Response

04 — Stack Updated

MTG Response Assistant: Stack Updated

05 — Waiting for Players

MTG Response Assistant: Waiting for Players

06 — Resolution

MTG Response Assistant: Resolution

Priority indicators

Distinguish turn ownership from priority so users know whose action is needed.

Visual stack

Counterspell appears above Lightning Bolt with a clear resolution-order indicator.

Explicit interactions

Respond and Pass Priority are separate, clearly labeled actions.

Waiting states

Player status communicates who has passed priority and who can act next.

Resolution feedback

In the demonstrated scenario, Counterspell counters Lightning Bolt, preventing its damage and leaving the stack empty.

LOW TO HIGH FIDELITY / RESPONSE WINDOW

IMAGE PLACEHOLDER

Before / Low fidelity

Original response-window wireframe.

IMAGE PLACEHOLDER

After / High fidelity

Final response-window screen.

08 DESIGN DECISIONS

Designing for clarity

The interface decisions focus on helping players recognize the current state, choose an action, and understand what happens next.

Visual hierarchy

The active response window receives greater emphasis than secondary information.

IMAGE PLACEHOLDER

Visual hierarchy / detail crop

Enlarged detail from your authentic interface.

Progressive disclosure

Available actions depend on the current stage of gameplay, rather than appearing all at once.

IMAGE PLACEHOLDER

Progressive disclosure / detail crop

Enlarged detail from your authentic interface.

Consistent feedback

The interface communicates changes in priority, stack state, and spell resolution.

IMAGE PLACEHOLDER

Consistent feedback / detail crop

Enlarged detail from your authentic interface.

Educational explanations

Short contextual descriptions explain what actions mean and why outcomes occur.

IMAGE PLACEHOLDER

Educational explanations / detail crop

Enlarged detail from your authentic interface.

09 / USABILITY TESTING

Testing the Experience

Evaluating whether players could navigate complex spell interactions with confidence.

After completing the initial six-screen high-fidelity prototype, I tested the interaction flow with three participants. I collected qualitative feedback on response windows, the stack, passing priority, resolution feedback, and general usability.

The scenario

“You’re playing Magic: The Gathering, and your opponent casts Lightning Bolt. You have Counterspell available and want to stop Lightning Bolt from dealing damage.”

  1. Navigate until an opportunity to respond appears.

  2. Use Counterspell to prevent Lightning Bolt from dealing damage.

  3. Follow the interaction until both spells leave the stack.

Research Findings

01 / Gameplay explanations worked

Participants understood when they could respond and why Counterspell stopped Lightning Bolt. One participant singled out the smaller explanatory text as helpful.

Design implication

Keep short, contextual explanations instead of relying on game terminology alone.

02 / Controls needed reliable behavior

One participant found simulation buttons with small clickable regions and encountered unintended navigation on the stack screen.

Design implication

Make touch targets match the visible controls and limit navigation to intended interactions.

03 / Card information needed to stay accessible

Two participants independently asked for easier access to card information. One missed Lightning Bolt’s description after the opening screen; another suggested card imagery and lookup.

Design implication

Keep relevant descriptions available throughout the flow without crowding the main interface.

04 / Stack and priority needed clearer cues

One participant paused to identify which spell resolved first. Another wanted priority order explained more clearly, particularly for multiplayer Commander.

Design implication

Label resolution order explicitly and distinguish the active turn from the player with priority.

Testing Limitations

This was a small qualitative evaluation with three participants, based primarily on written responses. I did not record formal task-completion times or performance metrics.

10 / DESIGN ITERATIONS

Turning Feedback into Design Improvements

Refining the experience through participant-informed changes.

I prioritized reliable controls, easier access to card information, clearer stack order, and more visible priority. These revisions respond to the first round of testing; follow-up participant testing has not yet been conducted.

VIEW REVISED FIGMA DESIGNS

Revised designs are on the “04 - Iterations” page. Select a screenshot to inspect the full-resolution export.

01 / Improving Interaction Reliability

Problem: A participant encountered small clickable regions and unexpected navigation.

What I changed: I repaired prototype connections, removed unintended screen-wide navigation, expanded clickable regions, and kept simulation controls within mobile screen boundaries.

Why: Controls should behave as their appearance suggests, reducing errors and hesitation.

BEFORE

MTG Response Assistant: Stack Updated

AFTER

Additional response — guided scenario

Clickable behavior must be inspected in Figma; a static image alone cannot demonstrate it.

02 / Making Card Information Accessible

Problem: Players wanted to check unfamiliar cards without losing their place.

What I changed: I added “View card details” controls, a dedicated reference screen for Counterspell and Lightning Bolt, and 44-pixel-high card-detail touch targets.

Why: Progressive disclosure keeps extra information available without overwhelming the main flow.

BEFORE

MTG Response Assistant: Stack Updated

AFTER

Revised stack with card-detail controls

Card details stay accessible throughout the interaction.

OPTIONAL CARD REFERENCE

MTG Response Assistant — revised optional card-reference screen

03 / Clarifying Resolution Order

Problem: One participant needed a moment to work out which spell resolved first.

What I changed: I added numbered resolution indicators, clearer labels, and explicit explanations of what resolves first and what happens to a countered spell.

Why: Players should recognize resolution order without inferring it from position alone.

BEFORE

MTG Response Assistant: Stack Updated

AFTER

Revised Screen 4 — clear resolution order

Numbered indicators and explicit labels clarify what happens next.

04 / Making Priority More Visible

Problem: A participant asked for clearer priority order, especially in multiplayer interactions.

What I changed: I distinguished whose turn it is from who currently has priority, clarified passing priority, and revised the waiting-for-opponent display.

Why: Visible system status shows players when they can act and whose decision is needed next.

BEFORE

MTG Response Assistant: Waiting for Players

AFTER

Revised Screen 5 — priority order

Turn and priority indicators explain who can act.

11 / REFLECTION

What I Learned

This project reinforced that an interface needs to communicate clearly and behave reliably. The contextual explanations and separate stack view supported comprehension, but understandable information was not enough when touch targets were inconsistent or card details were hard to access.

I focused the revisions on visible system states, accessible card information, and less ambiguity around actions and resolution order. Keeping the scope narrow helped: this is a response assistant for one spell interaction, not a complete Magic rules engine.

Next Steps

The revised prototype is ready for another round of evaluation. I’d test whether players interpret the priority indicators more quickly, can find card details easily, and understand the flow in multiplayer Commander scenarios.

Possible future additions include actual Magic card imagery, Scryfall-based card lookup, and more complex multi-spell interactions. These are opportunities for future work, not completed features.