Mike DeLeon · Senior Product Designer

EA connect · New feature, 0→1

Quick Messages for EA connect

Players have sent over 300 million Quick Messages, across more than 25 million users. I led design for the feature from first interviews to shipped product.

300M+messages sent
25M+users
2× fasterinternal design handoff, from an estimated 1 month to 2 weeks per feature
EA connect friends list with the Quick Message menu open, showing preset messages such as Let's play?, Ready? and Want to join us?
Final product: sending a Quick Message from the friends list.
Product
EA connect, the cross-platform social layer inside most new EA titles
Feature
Quick Messages: one-tap preset messages between players
Role
Lead designer. I owned every UX decision, the visual design, interactions and animations
Type
New feature, 0→1

Problem

Players had no quick way to reach each other in EA connect.

Connecting meant sending a friend request first, and after that the main option was voice chat.

Interviews showed that voice chat leaves many players out:

  • VoIP use depends on comfort and on how well players know each other.
  • Women are less likely to use VoIP.
  • Coordinating before and after a session matters as much as talking during it.

The design question: how do we give players who rarely communicate a low-effort way to do it?

Solution

A preset message such as “Let’s play?”, “Ready?” or “Want to join us?” in a couple of button presses.

The recipient sees it as an in-game notification showing which game it came from, and can hold a button to reply, mute the sender or dismiss it.

Sending

Friends list with a player selected and a Quick message button beside Invite to lobby
1 Pick a player
Quick Message menu open beside the selected player, listing six preset messages
2 Choose a message
The player's row showing a green Sent confirmation
3 Sent

Receiving

A Quick Message arriving as an in-game notification in Battlefield 2042, labelled Sent from Battlefield 2042 with a Hold to reply action
An in-game notification showing which game it came from, with hold-to-reply.
The notification expanded in game, offering Add as EA friend, two preset replies, Mute player and Dismiss
Holding the button expands it: reply, add as friend, mute or dismiss.
The notification showing the received message and the player's reply
The reply appears in the same notification.

Three decisions shaped it:

  1. Presets over typing.

    Interviews pointed to short status-style messages (“Be right there”) as the gap between silence and voice chat. Presets also suit a controller, where typing is slow.

  2. Testing the selection pattern by genre.

    I prototyped a radial wheel and a dropdown and tested both with shooter and sports players. Shooter players preferred the wheel 60/40, citing familiarity from other shooters. Sports players split 50/50, and those who preferred the dropdown said the wheel felt out of place in a sports game and took longer to understand.

    Prototype of a radial wheel for choosing a Quick Message
    Radial wheel
    Prototype of a dropdown list for choosing a Quick Message
    Dropdown list
  3. A new handoff format.

    I replaced long Google Docs specs with annotated design files and embedded prototypes, so engineers could see the exact interactions and animations I intended.

    Annotated handoff file showing the Flows section and the Sending from Friends screen
    The annotated handoff file, with flows, components and embedded prototypes.

Also shipped

All Quick Messages screen with a three-column grid of preset messages
All Quick Messages: the full library, one press past the six defaults.
Quick Message menu on a party invite offering Be right there, Another time and After this match
Replies fit the context: a party invite offers “Be right there”, “Another time” or “After this match”.
Inbox tab showing a received message with reply options Send invite, Yeah and Need a minute
Inbox: past messages, with suggested replies such as “Send invite”.
Settings screen for choosing six default Quick Messages for Recently Met players
Settings: players choose their six default messages.

Impact

  • 300 million+ messages sent by 25 million+ users.
  • Handoff time roughly halved. Estimated handoff on an average feature went from 1 month to 2 weeks.
  • The handoff format became the team standard. Every feature since has used it. Engineers said it was easier to navigate, and that embedded prototypes helped them get the execution right.
· Drag to pan