Sophie Lancaster

Client work is hidden!

Please email me for the password.

Back to all projects

lululemon

lululemon native Android app case study cover

Designing lululemon’s native Android app.

  • Role: UX/UI Designer

  • Team: Embedded with lululemon’s Android, iOS, design systems, and accessibility teams

  • Timeline: Six month staff augmentation engagement

  • Client: lululemon

  • Scope: Wireframes, detailed design, edge cases, design system contribution, visual QA, UAT, post-launch roadmap, handoff documentation

The Challenge

At the start of this project lululemon had no Android app in market at all, while the iOS app was mid-rebrand into a new internal design language. With the brand losing ground to competitors, an original three-year Android timeline was compressed into six months — and one internal lulu designer was carrying it.

The core challenge: How do you stand up an entire native app, every flow and every state, when the design language you’re translating from is still being written?

My Role & Ownership

I was staffed directly into the client’s team rather than delivering from the outside:

  • Owned Membership, Bag, Account / Login, and For You / Shop end-to-end

  • Contributed to Checkout, Post Purchase, CDP filters, PDP store inventory, purchase history, and region selection

  • Owned visual QA and UAT for Membership and Account, logging defects directly with the development team

  • Onboarded an incoming designer onto the team’s files and tooling

Context & Constraints

This engagement was defined by speed and absence of precedent:

  • No Android app, no Android design system, and no established patterns to inherit.

  • The iOS reference was still being rebranded mid-project.

  • Design was trailing development when we joined.

Key Decisions

  1. Unblock development before perfecting design. With dev waiting on design, we restructured our sequence:

    • High-level wireframes for every main page first

    • Detailed happy path second

    • Edge cases layered in last

  2. Translate to the platform, not just the screen. Android needed to feel native, not converted:

    • Based the work on the existing iOS design system

    • Augmented with Material 3 wherever the platform required it

  3. Treat quality as part of design, not after it. As the build progressed, I stayed close to it:

    • Joined visual QA sessions as the only designer present

    • Set up an emulator myself to test builds against design

    • Built a UX kanban board to track incoming ad hoc requests

The Solution

A complete, launch-ready native Android experience:

  • Full guest journey across shop, browse, product, bag, checkout, and post purchase.

  • Membership and gated experiences designed from the ground up.

  • Edge, error, and empty states layered onto every flow.

  • Annotated designs and spacing specs left behind for the internal team.

For You Page

Shop

CDP

Membership Hub

Account

PDP

Bag

Checkout

Outcomes & Impact

  • lululemon’s first native Android app launched in market in August 2026.

  • Delivered a full app design against a timeline compressed from three years to six months.

  • Selected as the only designer of seven to extend through launch and post-launch work.

  • Established the Android design foundation the internal team continues to build on.

Reflection

This project changed how I think about pace:

  • I learned that speed and craft are a sequencing problem, not a trade-off.

  • I got comfortable designing without a finished reference to work from.

  • I found I like staying with a product through build, QA, and launch.

“She brings a sense of calm and clarity to every design request, which has been incredibly valuable in this fast-moving, high-pressure project.”

— Stephanie Bende (Senior Business Analyst)