Native Design

Translating complex workflows to GitHub Mobile

Code review is a complex task. It requires context, focus, and access to history.

The challenge wasn't screen size, it was cognitive load. We had to break down the monolithic desktop review process into a linear, native flow that maintained integrity without overwhelming the user. And to this day, we're definitely still not done improving it.

The "Read-Only" Fallacy

Early assumptions about developers using GitHub Mobile were wrong. Early on we assumed they only wanted to "triage" notifications.

But data, and feedback showed they were eager to review, and merge code. They were reviewing PRs while commuting, while waiting for coffee. The demand for deep work was there, but the tool was fighting them.

Our job was to enable that deep work by designing a system that handled the complexity for them.

Context before action

Creating a PR is usually a form-filling exercise. On small screens, that's tedious.

We inverted the model. Instead of asking for a title and description first, we show the code changes immediately when creating a PR from an existing branch on GitHub Mobile. We anchor the user in the "What" before asking for the "Why".

This subtle reordering reduced abandonment rates because it gave users the context they needed to write a good description.

Orchestrating the queue

A list of Pull Requests causes anxiety. "Which one blocks my team? Which one is waiting on me?"

We redesigned the list view to be state aware. We explicitly highlighted "Review requested", and "Pending review".

It's not just a list, it's a prioritization engine. We moved the cognitive load of decision-making from the user to the system.

Adaptive UI

The interface changes based on your role. If you're the author, we show CI status and merge blockers. If you're a reviewer, we float the "Review" action.

We used sticky headers and adaptive banners to ensure the primary action was always available but never too intrusive.

Dummy image representing PR screen with sticky banner and merge box

Managing state across devices

Reviews are often multi-session tasks. You start on desktop, commute, and finish on GitHub Mobile.

Metric-driven iteration

We validated this with funnel analysis. The new flow increased entry, and review completions on GitHub Mobile because we removed the "fear of missing context", and designed a holistic flow from PR creation to merging. Users trust Mobile enough to hit the green button.

Closing

Complex tools often fail on mobile because we try to shrink the pixel count instead of rethinking the workflow.

If you respect the user's cognitive load, you can build incredibly powerful tools on a small screen.