Work/Microsoft

  • Android Native Patterns
  • Mobile-first Strategy
  • Material Design
  • Cross-platform UX
  • Design Systems
  • Information Architecture
Role
Product Designer
Team
Microsoft OneDrive, Redmond
Timeline
Jun 2014 — Jun 2015
Platform
Android
01 / 07

Web and Android convergence wireframes. One concept model for files, shares and accounts, expressed natively on each platform.

Satya Nadella took the CEO seat in early 2014 and reset the company around a single thesis: mobile-first, cloud-first. OneDrive moved from a Windows accessory to a flagship Microsoft pillar. It became the surface that carried identity, documents and consumer storage across every device a customer touched.

On Android, the gap was visible. The app carried Windows IA, Windows iconography and Windows interaction grammar onto KitKat and soon Lollipop. It read as foreign. It behaved that way.

The brief wasn’t a refresh. The application needed an end-to-end redesign against Android’s own conventions, ahead of Material, at a fidelity that could earn its place on a Samsung home screen.

  1. 01

    A platform-native posture

    Stop porting Windows. Re-ground every primary concept (file, folder, account, share, search) in Android conventions and the emerging Material spec.

  2. 02

    A unified concept model

    Align the org on a single mental model for how users perceive files, shares and accounts across web, phone and tablet. Design downstream from that model.

  3. 03

    Two release cadences

    A surgical KitKat alignment release to prove the thesis with shipped code, followed by the full Lollipop rebuild once the Material spec landed.

  4. 04

    Phone and tablet as one system

    A single IA and interaction language that scaled responsively across handset and tablet, not two parallel products.

The strategy started as a single diagram, internally called the “unified theory of stuff.” A user’s files, the people they shared with, and the accounts they signed into were treated as one connected system rather than three.

Every downstream IA decision laddered back to it: what lived in the drawer, what surfaced in the action bar, how multi-account behaved, how sharing collapsed across personal and business contexts.

Two coordinated releases. The first proved the bet with shipped code on the existing platform. The second tore the app down and rebuilt it against the Material spec while Google was still finalizing it.

The KitKat alignment release

A surgical pass against the existing app. Re-grounded the action bar and overflow, swapped Windows iconography for Android conventions of the day, and re-anchored the nav drawer so OneDrive read as an Android citizen on a stock Nexus. The point wasn't any single screen. It was every system surface speaking the platform's language at once.

01 / 05
01 / 04

A Material rebuild ahead of the spec

The Lollipop release rebuilt the app against Material while Google was still finalizing the guidance. The objective wasn't to apply Material to OneDrive. It was to design OneDrive as if it had always been Material, and to ship at a fidelity that earned the claim on a Samsung home screen.

One interaction language across phone and tablet

The tablet wasn't a stretched phone or a parallel app. The same IA, drawer, list and grid grammar, and action-bar behaviors scaled responsively into multi-pane layouts. Selection, sharing and search worked identically on both form factors.

01 / 04

~16M

Android users on the rebuilt app

2

platform generations: KitKat and Lollipop

Galaxy S6

preloaded as a Samsung first-party partner

1

IA and interaction language across phone and tablet

Convincing a Windows-anchored organization to ship a product that didn’t look or behave like Windows was the actual work. Every system surface was a negotiation against muscle memory.

The unified model carried the program. Once the team agreed on how files, shares and accounts related independent of platform, the Android calls stopped being aesthetic debates and became questions of platform fidelity.

In hindsight, this work was the early shape of what Microsoft would become later in the decade. An organization willing to be a great citizen on someone else’s platform.

Previously

← Previous case study

Next

End of case studies