Wing Bank 4.0

Faster Updates for a Popular Banking App

The Problem & Opportunity

{Title to be filled}

Feature demand was outpacing design capacity, patterns were drifting across every release, and product managers arrived with folders of complaints instead of one clear problem.

I improved a high-traffic banking app with quick updates, using AI to turn large amounts of user feedback into finished, ready-to-build designs.

My Role

UX/UI Lead

I owned UX/UI direction for Wing's consumer banking app as the product grew from specialist banking into a commercial bank look and feel.

  • Day-to-day UX/UI for a high-traffic consumer banking app
  • The app revamp that shifted Wing toward a commercial bank identity
  • A feedback pipeline that turned messy complaints into clear problems
  • Stakeholder requests translated into shippable product decisions

Hero

Faster updates for one of Cambodia's most-used banking apps.

Design handoff in 10 days instead of 3 weeks. UI consistency up 40%.

Challenge

Keep a high-traffic app coherent while the roadmap accelerated.

  • Transfers, wallets, QR pay, and onboarding for a growing national base
  • Every release added screens; pattern drift compounded across squads
  • Business needed velocity without a sloppy UI

Context

Over four years as UX/UI Lead, my job was not to draw more screens.

It was to compress the loop from “we heard 500 complaints” to “here is one testable flow.”

Existing Experience

Mixed button styles, inconsistent success states, and no shared language for post-transaction flows.

Pattern drift across releases before the refresh.
  • Success states looked different on every flow
  • Three button styles and two navigation models coexisted in production
  • Every quick fix added another variant

Pain Points

{Title to be filled}

  • Onboarding OTP failures and transfer limit confusion
  • QR receipt anxiety: users could not find history after paying
  • Inconsistent success states and button styles across journeys
  • PMs arrived with reviews and call-center notes before problems were prioritized

Design Decisions

{Title to be filled}

  • Build a lightweight pipeline to cluster qualitative feedback into ranked themes
  • Use generative tools to explore layout density; designers rebuild winners in Figma
  • Apply AI inside the design operation first, not as a customer-facing chatbot
  • Redesign receipt and history as one path (68% of QR complaints were about finding history)
Transfer receipt with unified history and share actions.

Validation

{Title to be filled}

  • Usability testing selected one confirmation pattern before high-fidelity UI
  • Advisory copy and step count validated early
  • Winning flows reviewed for accessibility, then added to the shared pattern library

Outcome

{Title to be filled}

10 days Dev-ready handoff, down from 3 weeks
40% Rise in cross-journey UI consistency
23% Climb in QR repeat usage after receipt/history fix
5 Designers contributing to the shared library

Reflection

Release-speed design ops, AI-assisted synthesis with human craft, and pattern libraries that outlast one squad.

Next time I would instrument the feedback pipeline earlier so volume and severity score every theme before the workshop.

Contact

Let's Connect

Working on a product, or hiring for a Senior UX/UI Lead role in Cambodia? Email me or connect on LinkedIn or Telegram.

Resume LinkedIn Telegram
View More Work