Skip to content
All work
Case 09

Woodoos Native App

Designed native app flows including login/register, SSO phone number, Fingerprint/Face ID, OTP, catalog with wallet, account, inbox, wallet/sub-wallet/import, split payment, and purchase completion.

Native AppWalletPaymentAccountAuthenticationSplit Payment
Outcome highlights
  • A consistent authentication experience across SSO, biometrics, and OTP
  • Clearer wallet, sub-wallet, and split-payment behavior
  • A coherent navigation model across catalog, account, inbox, and wallet
Product type
Native app — account, wallet & payments
Platform
Native App (iOS/Android)
Timeline
2019–2022 · multi-phase native-app program
Role
UX flow, UI design, authentication & wallet logic
Team
Designer, PM, mobile engineers
Tools
Figma, FigJam
Context

Why this project existed

A native app product where users manage accounts, wallets, and purchases in one place — authentication needed to feel fast and trustworthy, and wallet and payment behavior needed to stay clear across split-payment and sub-wallet scenarios.
My role

What I owned

  • Native App UX
  • Account & Authentication Flow Design
  • Wallet UX
  • Payment Flow Design
  • Cross-platform Collaboration
Challenge

What made it hard

  • Multiple authentication paths (SSO phone number, Fingerprint/Face ID, OTP) needed to feel consistent
  • Wallet structure (wallet, sub-wallet, import) is inherently complex to explain
  • Split payment across wallet and other methods needed clear status
  • Catalog, account, and inbox needed to share one coherent navigation model
  • Native app constraints — platform patterns, performance, offline states
Process

How it came together

  1. 1Mapped login/register and authentication paths
  2. 2Designed catalog with wallet integration
  3. 3Structured account, inbox, and wallet/sub-wallet/import flows
  4. 4Designed split payment and purchase completion states
  5. 5Reviewed against native platform conventions
  6. 6Iterated with engineering on edge cases
Design decisions

The thinking behind it

Kept authentication options visually consistent regardless of method, and made wallet, sub-wallet, and split-payment status visible at every step so users always know where their money is.
Final design

Selected views

Abstract representations — original mockups, not client screenshots.

Outcome / impact

What changed

  • A consistent authentication experience across SSO, biometrics, and OTP
  • Clearer wallet, sub-wallet, and split-payment behavior
  • A coherent navigation model across catalog, account, inbox, and wallet
Reflection

What I took away

Native app constraints — platform conventions, biometric flows, offline states — pushed me to design authentication and wallet logic that holds up outside of a browser tab.
Back to all work