Marketplaces
Two customers, not one — and they usually want opposite things.
2.16.1Definition & Purpose
A marketplace connects two distinct user groups — buyers and sellers, riders and drivers, renters and hosts — facilitating transactions between them without being the party on either side of the exchange. Its central challenge is a two-sided design problem: growing supply and demand together, since neither side alone makes the product useful.
2.16.2Architecture Priorities
Trust and safety infrastructure — identity verification, reviews, dispute handling — is core product architecture, not an add-on, because marketplaces inherently connect strangers around money. Payment flows are more complex than standard e-commerce, frequently requiring holding funds in escrow and splitting payouts between the platform and the seller/provider.
2.16.3UX Priorities
- Separate, tailored experiences for each side — a seller/provider dashboard and a buyer-facing browsing experience solve entirely different problems.
- Trust signals (reviews, verification badges, response times) need to be visible at the point of decision for the side choosing who to transact with.
- Clear dispute and refund processes, since transaction problems between two independent parties are inevitable at scale.
2.16.4Common Mistakes
- Building only for one side of the marketplace first without a credible plan for how the other side gets bootstrapped.
- Underestimating the trust and safety investment required once real money and strangers are involved.
2.16.5Best Practices
- Design onboarding and incentive structures for both sides explicitly and separately from the start.
- Invest in trust infrastructure (verification, reviews, dispute resolution) as early, core functionality.