Skip to content
All work
Case 10

mPOS / WebPOS

Supported mobile POS and desktop WebPOS experiences for B2B2C scenarios involving transaction-heavy product contexts and business-facing operations.

mPOSWebPOSB2B2CPOSRechargeOperational UX
Outcome highlights
  • Consistent core task patterns across mPOS and WebPOS
  • Faster, less error-prone transaction and recharge flows
Product type
mPOS & WebPOS — operational transactions
Platform
Mobile POS, Web (desktop terminal)
Timeline
2021–2024 · multi-phase POS program
Role
Operational UX, flow design, cross-device consistency
Team
Designer, PM, operations stakeholders, frontend engineers
Tools
Figma, Flow diagrams
Context

Why this project existed

Point-of-sale experiences spanning a mobile device (mPOS) and a desktop web terminal (WebPOS), used by business operators to process transactions, recharge, and day-to-day operational tasks in B2B2C scenarios.
My role

What I owned

  • POS UX
  • Operational UX
  • B2B2C Flow Design
  • Cross-device Consistency
  • Recharge Flow Design
Challenge

What made it hard

  • Same core tasks need to work on both a small mobile screen and a desktop terminal
  • Transaction-heavy flows leave little room for ambiguity or error
  • Operators need speed over decoration
  • Recharge and operational tasks needed consistent status and confirmation patterns
  • Designing for business-facing operators, not end consumers
Process

How it came together

  1. 1Mapped core operator tasks across mPOS and WebPOS
  2. 2Designed shared interaction patterns for transaction and recharge flows
  3. 3Adapted layout for mobile vs. desktop terminal contexts
  4. 4Designed confirmation and error states for transaction-heavy use
  5. 5Reviewed with operations stakeholders for real-world usability
Design decisions

The thinking behind it

Prioritized speed and predictability over visual flourish — operators repeat the same tasks dozens of times a day, so every extra tap or ambiguous state has a real cost.
Final design

Selected views

Abstract representations — original mockups, not client screenshots.

Outcome / impact

What changed

  • Consistent core task patterns across mPOS and WebPOS
  • Faster, less error-prone transaction and recharge flows
Reflection

What I took away

POS work reframed efficiency as the actual design goal — clarity matters, but for an operator running the same flow all day, speed is the real success metric.
Back to all work