NO
Loading selected work00
All work

Case study / 2025

Building the Lipaworld Mobile App: Marketplace × Wallet Integration

View live appGoogle Play

Designing two focused products under one roof: a marketplace for everyday services and a full-featured wallet for moving and managing money.

RoleProduct & Visual Designer
TimelineJanuary — September 2025
OutcomeA clear marketplace and wallet experience
Lipaworld mobile marketplace and wallet app cover

Overview

ScopeProduct Strategy · UX/UI · Branding
ToolsFigma
PlatformMobile App (iOS & Android)

01 / Context & motivation

Two powerful products, one connected experience.

Lipaworld’s mobile app was designed to balance two distinct user needs: accessing everyday services through a marketplace and managing money through a full-featured wallet. The challenge was not simply combining both, but ensuring neither experience felt compromised. From the start, we treated the marketplace and the wallet as two powerful but different products living under one roof.

02 / The real problem

Different intents, one crowded home.

Users came to Lipaworld for different reasons. Some wanted to buy vouchers and services quickly, while others wanted to send, receive, and manage money—especially from abroad. Blending both needs into one home experience risked confusion, cognitive overload, and a loss of clarity.

How might we give the marketplace and wallet enough space to feel complete, while keeping access between them effortless?
  • Keep marketplace discovery fast and immediately understandable
  • Give the wallet the depth and clarity of a standalone fintech product
  • Make movement between both experiences effortless
  • Build reusable flows for recipients, checkout, and money movement

03 / Design thinking & exploration

Separate the products, connect the journeys.

Early concepts blended marketplace actions, account balances, and money movement into one dashboard. The result asked users to process too much at once. Separating the products at the top level created a clearer mental model: browse and purchase in Marketplace; send, receive, and manage money in Wallet.

2

A clear marketplace and wallet experience

04 / Key product decisions

Marketplace and wallet, each with room to work.

A top-level tab system separates the marketplace from the wallet. Each product has its own focused navigation and flows, but both remain immediately accessible from the same home experience.

Appstore Screenshots

Product Flow Screens

Clear Separation, Seamless AccessTop-level Marketplace and Wallet tabs allow each experience to remain focused while keeping both immediately accessible.
Marketplace Home (Vouchers Page)Vouchers are the primary focus, helping users understand Lipaworld’s value within seconds of opening the app.
Cart (Checkout Entry Point)A clear overview lets users confirm intent before deciding how the voucher will be used or sent.
Send to Lipaworld UserSaved recipients minimize input and make sending to an existing Lipaworld user familiar and fast.
Send to Non-Lipaworld UserThe external-recipient flow introduces enough structure for accuracy without feeling technical.
Send to SelfThe same checkout system adapts cleanly for users purchasing vouchers for their own use.
Marketplace PaymentCost, payment method, and confirmation come together clearly at the most critical point in the journey.
Marketplace Saved RecipientsSaved recipients reduce repetitive input and build confidence in repeat transactions.
Marketplace Lipaworld UsersLipaworld users are surfaced clearly so peer-to-peer voucher sending feels native to the ecosystem.
Owned VouchersOwned vouchers remain visible as assets users can return to, rather than disappearing after a transaction.
Wallet HomeThe wallet is presented as a complete financial tool, not a secondary feature attached to the marketplace.
Wallet — Send MoneyThe send-money flow uses familiar recipients and direct actions to keep money movement clear.
Select RecipientRecipient selection keeps saved people and relevant account information close to the decision.
Transfer ConfirmationThe confirmation step brings recipient, amount, and transaction details together before money moves.
Offramp RecipientsExternal recipients save bank details instead of Lipaworld tags, supporting repeat offramp transactions.
Wallet Lipaworld UsersLipaworld users remain clearly distinguished while recipients from previous transactions are saved for reuse.

05 / Outcome & reflection

What the separation made possible.

Closely related products do not need to share one interface. Clear separation made both experiences easier to understand, while a consistent system preserved the feeling of one connected Lipaworld product.