Beyond Scaling: Mobile-Native to Desktop-Native

Act 01Context

For a long time, LinkedPhone primarily lived on mobile. That wasn't an accident.

The product was built around a simple belief: small business owners are mobile. They answer calls while driving. Respond to messages between jobs. Run businesses from their pockets.

As adoption grew, another customer started appearing: operations staff, managers, customer support agents, office workers. People who weren't working from their phones. People spending entire days inside LinkedPhone.

If mobile is designed for moments, what should desktop be designed for?

Chapter theme

The goal was never making desktop bigger. It was making desktop native.

"Desktop shouldn't feel like a stretched mobile app. It should feel like a workspace."

Executive Summary

It already had a desktop. It just wasn't one yet.

Challenge

LinkedPhone already had a desktop experience, but it behaved like a companion product. As customers evolved, the existing architecture couldn't support deeper workflows.

Breakthrough

The problem wasn't screen size. It was context. Desktop users needed relationships between information, not bigger versions of the same screens.

Outcome

A reimagined workspace architecture. Navigation, context and information density all evolved together, and the product finally became multi-platform, not just multi-screen.

Transformation at a glance

Mobile thinkingDesigned for moments, one task at a time

Workspace thinkingDesigned for hours, many tasks at once

Context thinkingRelationships between things, not just the things

Work thinkingThe realization that led to the Unified Work Model

Timeline: 2024Desktop expansion era
Platforms: DesktopMobile · Web
Teams: DesignProduct · Founders
Discipline: PlatformSystems · IA
Legacy: FoundationFor the Work Model

Where We Were

A desktop that worked, built from towers.

Many people assume Beyond Scaling was LinkedPhone's first desktop product. It wasn't. A desktop experience already existed, and its architecture was tower-based: opening a chat, a contact, a ticket, or a profile each spawned a new floating tower, like classic Facebook chat windows.

Users loved parts of it. It was unique. Fast. Flexible. But it also introduced complexity that didn't align with the mental models people had built from other work software.

Artifact · Old desktop architecture

Tower after tower

Every item opened as its own floating window: fast and flexible at first, fragmented at scale.

Act 02Problem

The Problem

It wasn't failing. It wasn't scaling either.

As the product evolved, calls expanded, tickets expanded, contacts expanded, AI expanded, team workflows expanded. The tower system started revealing its limits.

The biggest challenge wasn't layout. It was information density: how much a person could understand at once, and how quickly they could move between related things.

Customer impact

Information became fragmented. Context became fragmented. Relationships between things became fragmented.

Business impact

Future product expansion became difficult to imagine on top of an architecture that was already straining.

Internal impact

The desktop architecture wasn't creating leverage anymore. It was creating constraints.

Investigation

The question changed before the answer did.

Initially the question looked simple: how do we redesign desktop? After deeper exploration, it became a different question: how do people work differently on desktop?

Research focused on Zendesk, HubSpot, Notion, Linear, Intercom, Salesforce, and others. The objective was never copying patterns. It was understanding behavior.

Artifact · Competitive landscape

Information density, navigation, context, flexibility

Mapped across six mature desktop products, not to copy them, but to see what behavior they assumed.

Insights

Desktop users weren't mobile users sitting still.

Insight 01

Desktop users aren't mobile users at desks.

Observation: Behavior fundamentally changes on desktop.
Meaning: Desktop deserves its own design philosophy.
Implication: Platform-specific design, not a scaled layout.

Insight 02

More space doesn't solve complexity.

Observation: Many desktop products simply expose more UI.
Meaning: Space alone doesn't create clarity.
Implication: Context becomes the critical variable.

Insight 03

Relationships matter more than entities.

Observation: Users constantly jump between a conversation, a customer, a ticket, a history.
Meaning: The relationships between things are the actual work.
Implication: The interface has to expose connections, not just records.

Insight 04

Context switching is expensive.

Observation: Every jump between towers cost orientation.
Meaning: Navigation cost adds up over an eight-hour day.
Implication: The system should minimize how often people have to reorient.

Act 03 · Turning Point

We thought desktop needed more information.

It needed more context.

The objective shifted from showing more, to showing relationships. Desktop isn't a larger screen. It's a different mode of thinking.

Exploration Lab

Three shapes for a desktop, only one held.

Direction A

Scaled Mobile

Failed

Why it looked promising

Fast to build
Familiar to mobile users

Why it failed

Felt stretched, not native
Lost every desktop advantage

Native feel

Context

Direction B

Enterprise Dashboard

Partial

Why it looked promising

Data-dense
Familiar enterprise pattern

Why it fell short

Overwhelming
Heavy for day-to-day use

Native feel

Context

Direction C · The winner

Workspace Architecture

Succeeded

Why it looked promising

Natural, flexible
Room for context, not just content

Why it succeeded

Context rich without being heavy
Became the backbone of desktop

Native feel

Context

The percentages above are illustrative evaluation scores from the exploration process, not measured data.

Breakthrough

Not pages stacked on pages. A place to work.

The breakthrough emerged through a simple structure that eventually became the backbone of the entire desktop experience.

The hero diagram of this chapter

NavigationOrientation: where am I?

WorkspacePrimary work: what am I doing?

ContextUnderstanding: what does this connect to?

Desktop isn't a larger screen. It's a different mode of thinking.

Act 04System

System Architecture

Three layers that scaled naturally.

Navigation

Orientation.

Always visible, always answers "where am I."

Workspace

Primary work.

The surface where the actual task happens.

Context

Understanding.

Customer history, relationships, ownership, always in view.

Design System Impact

Desktop stress-tested every pattern the system had.

Panels

Component

Tables

Component

Context cards

Pattern

Split views

Layout

Desktop navigation

System

Workspace components

System

Product Showcase

A workspace, made visible.

Screen · Navigation system

Always-visible orientation

The narrow rail that always answers "where am I," across every workspace.

Screen · Workspace layer

The main work surface

Conversations, tickets, contacts and calls, each a multi-entity view of the same underlying work.

Screen · Context layer

Customer history, relationships, ownership

Everything needed for resolution, always one glance away, never a separate tower.

Interaction & Motion

Interactions that would never exist on mobile.

Hover states

Interaction

Multi-select

Interaction

Context panels

Layout

Inline actions

Pattern

Keyboard navigation

Interaction

Workspace states

System

Act 05Impact

Validation

Context kept winning, from every direction.

Internal reviews, founder discussions, user testing and early releases all pointed the same way.

Context mattered more than expectedTeams noticed how much faster they worked once relationships were visible, not just records.

Relationships mattered more than entitiesEarly feedback consistently asked for more connections between things, not more things.

Desktop-specific thinking matteredNobody asked for the mobile experience back once they'd used the workspace model.

Ripple Effects

This chapter is where the Work Model began.

While designing context-rich desktop experiences, a deeper realization surfaced: conversations weren't the thing users cared about. Problems were.

Beyond Scaling to Context Architecture to the Unified Work Model to AI workflows and a future CRM. The realization that started here didn't stay contained to desktop.

The evidence vault.

Presentation deck

Embed

Desktop explorations

Figma

Wireframes

Figma

Competitive analysis

Board

Prototype videos

Video

Architecture documents

Doc

Lessons

What we believed. What we learned.

Lesson 01

Desktop users aren't mobile users with larger screens.

They work differently, in longer stretches, across more open threads at once.

Lesson 02

Context is more valuable than information.

Knowing how things relate beats simply knowing more things.

Lesson 03

Relationships matter more than entities.

The connections between records are usually the actual work.

Lesson 04

Good desktop software feels like a workspace.

Not a collection of screens borrowed from somewhere else.

Legacy

This was never really about desktop.

It was about platform maturity. LinkedPhone began as a mobile communication product. Beyond Scaling transformed it into a multi-platform workspace.

The chapter also produced one of the most important realizations in the entire transformation: conversations weren't the thing users cared about. Problems were. That realization eventually became the Unified Work Model.

Closing

The breakthrough wasn't making desktop bigger. It was realizing that work looks different when people finally have room to see the whole picture.