
TL;DR
Problem
Solution
Impact
Team

Every tab in the app felt like Whisker's — except the one that made money.

01
Fragmented experience
Web Drives Sales, App Builds Growth
Disconnected
Low Efficiency
02
Web View chaos
Disconnected UI, broken trust, and missed conversions
WebView-Bound
Inconsistent
03
High CX touchpoints
High Support
Low Insight
How might we improve the in-app Shop to support faster decisions and simpler order management — without a full rebuild or added engineering cost?
average time on screen — people hunted for account & subscription flows
misclick rate in the WebView flows
[ research artifact: moderated test + survey + benchmark board ]
The Call I Made
I didn't rebuild the shop. I shipped the half that mattered, native.
Native Shell + Web Core — native order, subscription, and account modules over a web core, phased by value.
Instead of
A full native rebuild (the north star) — the right long-term answer, but a long timeline and heavy engineering cost.
What it cost
Some surfaces stayed web for the MVP. I sequenced the highest-value flows native first — account, orders, subscriptions.
Who I brought
The app-team PM and engineering — aligned on a phased MVP so we could launch in months, not quarters.
Native. Delightful. Harmonized.






87%
8s → 3s
24 → 100
“Cleaner, smoother, more trustworthy.” — participant, usability testing
What outlasted the project
The work didn't stop at the app.
The redesign produced a system, not just screens — and it reached past the surface I was asked to fix.
One account model
A shared mental model
A shipping pattern
Native Shell + Web Core
A reusable component library
The app stopped borrowing the website — and the website started borrowing the app.
Two things I'd change.
EST. 2025
2:06:12 UTC








