Jasmine Jackson

Mobile Sales Modernization

Redesigning QuickBooks Mobile’s Sales Receipt and Receive Payment so they feel like one consistent product, built on a new shared component library.

ROLELead Product Designer
TIMELINE4 months
TOOLS / STACKFigma, Usertesting
CORE OUTCOME80% Fewer Regressions

The Problem

QuickBooks mobile sales forms were vastly different from one another. A small business owner managing accounts receivable on the go found the app unintuitive, missing features available on web, and inconsistent form to form, leaving them unconfident in mobile and inclined to fall back to the website.

  • I am.. a small business using my mobile device to manage accounts receivable.
  • I’m trying to.. create and edit forms while on the go.
  • But.. the mobile app is not easy to use.
  • Because.. every form looks different and not all web features exist on mobile.
  • Which makes me feel.. unconfident, and inclined to just use the website.

The Solution

Create consistency across the sales forms and bring mobile to parity with web, using a new shared component library, starting with Sales Receipt and Receive Payment as the first real use case.

6 wks → 2 days
Design-to-Dev Handoff

Handoff timeline collapsed once the shared component library was in place.

80%
Fewer Regressions

Fewer regressions on high-traffic pages after the shared library rollout.

Protected

The rest of this case study is locked

Enter the password to see process, iterations, and the final design.