Bringing an iOS-first rewards experience to Android with native Material Design 3 patterns — not pixel-perfect copies.
Verizon Offers is the central mobile hub where Verizon customers discover and redeem benefits: partner discounts, content subscriptions, device promos, and loyalty rewards. It is a key touchpoint for reinforcing Verizon's value beyond the monthly bill.
The iOS app was already live, stable, and heavily used. Android, however, lagged behind and often reused iOS visual patterns directly — from tab bars to modal dialogs — creating friction for Android users who expected native behaviors and system conventions.
Android users were using an experience that felt like a direct iOS port: iOS tab bars, segmented controls, and modal patterns appeared in a context where users expected Android conventions and gestures. This created non-native friction and inconsistency with other Verizon Android apps.
To avoid blindly copying iOS, I started with a structured parity audit: comparing iOS and Android implementations across navigation, filters, cards, and flows. This surfaced both functional gaps and non-native UX patterns on Android.
These gaps helped align stakeholders around a simple message: we needed feature parity, not pixel parity.
From the audit, I defined three principles to keep the team aligned while moving fast.
With principles and gaps defined, I redesigned key flows for Android — Home, Offer Detail, Redemption, and Wallet — as a cohesive MD3 experience. Each flow balances Verizon's brand with native Android patterns.
To avoid one-off decisions, I formalized Android-specific tokens — spacing, corner radii, elevation, and color roles — and used them to structure cards, chips, navigation, and bottom sheets.
Under accelerated timelines and shared squads, I worked closely with PMs and engineers to slice parity vertically: shipping complete flows end-to-end rather than scattered screens.
Early explorations over-rotated into "pure MD3" and lost some of Verizon's brand presence. We corrected by re-introducing key brand elements while keeping MD3 structure. At another point, there was pressure to reuse iOS-style full-screen dialogs for redemption to save time — walking through System Back edge cases and long-term UX debt helped us align on MD3 bottom sheets instead.
The complete 28-slide deck — covering product context, parity audit, design system, key flows, wallet, accessibility, and strategic learnings. Navigate with arrows, keyboard, or touch swipe.
