Breaking Apart
the Unified Inbox
A legacy design had survived long past its technical constraints. I proposed and drove the structural separation of Meta's wearable messaging experience into distinct, purposeful apps, and sold it across engineering and leadership.
A unified inbox built for constraints that no longer existed
When I joined the team, the wearables messaging experience lived in a single unified inbox: one view that collapsed WhatsApp, Messenger, and other native messaging apps into a common thread list with no differentiation.
The original rationale was technical: early devices made separate navigation difficult, so a unified view was the pragmatic solution. But by the time I arrived, those constraints had long been resolved. What remained was a design that had outlived its reason for existing, kept alive by institutional familiarity and justifications that had built up around it over time.
People think of each messaging app as a distinct entity, with its own purpose and social norms
People today regularly use 5+ messaging apps. Each one carries a distinct social context: WhatsApp for family and close friends, Messenger for a different social graph, each with its own norms around what gets sent, to whom, and when.
Collapsing those into a single inbox simplified navigation on the surface, but it created a higher cognitive burden. Users weren't just navigating messages; they were constantly re-orienting to which context they were in.
"Navigation may be easier but cognitive load is higher. People actually think of each app as a separate entity with separate and different use cases."
Without a proper notification center, the unified inbox had also been serving as a workaround for awareness: a place to surface incoming messages from multiple platforms. But awareness and unified messaging are different needs. The design had conflated them.
What participants actually told us
Working closely with our researcher, we conducted user studies alongside a literature review of existing findings. The data consistently validated the hypothesis: separation wasn't just acceptable; it was expected.
Separate by social purpose
Participants use each platform for different purposes. Consolidation was wanted for awareness, not unified messaging across apps.
Mixed threads create confusion
Combining conversations from different platforms into one thread created a disjointed narrative, making it harder, not easier, to follow a conversation.
Tabs implied separation
When shown concepts with platform tabs, all participants perceived the accounts as separate, even when they shared a consolidated Meta view.
Mixed threads raised privacy concerns
When threads from different platforms were combined, participants worried that content from one social account was being shared with another. Separation reassured them that each platform stayed in its own context.
Selling a structural change that wasn't on anyone's roadmap
Breaking apart the unified inbox required buy-in across design, product, and engineering, and none of it was easy. This wasn't a feature request; it was a structural proposal that touched every platform team.
Made the legacy visible
I reframed the unified inbox not as an intentional design decision, but as a technical workaround that had outlived its context, shifting the conversation from "why change" to "why not."
Grounded every claim in research
Rather than advocating from intuition, I brought user data to every conversation. Participant findings plus a literature review created a strong, evidence-based case for separation.
Built design proposals to make it concrete
I developed tangible proposals showing how separated apps could work in practice, giving engineering teams something specific to react to rather than a conceptual argument.
Paired separation with a notification center
One key objection was awareness: the unified inbox helped people see all messages in one place. I proposed a dedicated notification center as the answer: consolidation for awareness, separation for action.
Distinct apps. One notification center. Clarity at every layer.
The resulting design separated WhatsApp, Messenger, and other native apps into their own distinct experiences, each with its own identity, purpose, and navigation on the device.
A new notification center addressed the awareness need that the unified inbox had been fulfilling as a side effect. Users could now see incoming messages across platforms in one place, without having all their conversations collapsed into a single context.
The recommendation also surfaced a path forward for consolidation without combination: stacking messages from one person across platforms while preserving app-level icons and context, so users could orient without cognitive overhead.
Shipped. And the foundation of my plan of record.
The proposal gained cross-functional alignment, became my plan of record, and shipped. A structural change to the messaging architecture, driven by a new designer through research and design, made it into the product.
"The hardest design challenge isn't the interface; it's convincing an organization to change course. This project required making the invisible visible: showing that a design which had accumulated years of justification was still just a workaround."