MiamiGo Marketplace Product Design Case Study

Designing a
two-sided local
discovery product.

A two-sided mobile product connecting consumer discovery with venue demand generation through one shared offer object across discovery, claim, redemption and measurement.

Two-Sided Product
End-to-End Flows
Venue Operations
Platform UI

View Figma Visit website

SCOPE

Consumer discovery, venue onboarding, offer creation, redemption states and performance UI.

CONSTRAINT

Two audiences need different interfaces, but the offer must remain one shared state across the system.

DECISION

Use the offer as the product object connecting discover → decide → claim → redeem → measure.

EVIDENCE IN THIS CASE

Consumer flows, business portal, offer states, redemption flow, measurement screens and UI foundations.

VALIDATION STATUS

The case shows the designed product loop. Claim-to-redemption, venue activation and repeat discovery remain next-validation metrics.

Two audiences, one shared transaction loop.

Consumers need to decide quickly what is worth doing nearby. Venues need a way to activate demand and understand whether an offer created action. The product challenge was to support two different user models without letting them drift into two disconnected systems.

CONSUMER

What is worth doing nearby, right now?

VENUE

How can I turn an empty time window into demand I can measure?

What if one offer object connected discovery, redemption and measurable demand?

The core product decision was to make the offer the shared object across both sides of the system: discovered by the consumer, claimed and redeemed in the real world, then measured by the venue.

DISCOVER

Consumer

DECIDE

Consumer

CLAIM

Shared state

REDEEM

Shared state

MEASURE

Venue

Reduce the decision cost of “what should I do tonight?”

Discovery is organized around time, proximity, visual context and offer value so the interface supports a fast decision without collapsing into a generic local directory.

TIME

Surface what is happening now

PROXIMITY

Keep distance and map context visible

VALUE

Make the offer legible before the tap

CONFIDENCE

Give enough context to decide

01 · DISCOVER
Discover screen
Start with nearby choices, timing and context so the user can quickly understand what is worth considering.
02 · MAP
Map screen
Keep location visible when proximity matters, without forcing the user to leave the discovery flow.
03 · DEALS
Deals and offers screen
Turn promotional value into a clear decision surface before the user commits to a venue.
04 · DETAILS
Venue details screen
Add the venue context needed to act with confidence while preserving the offer as the shared object.

01 / 04

A claim is not the end of the journey.

The product needed to connect digital intent with a real-world venue action. Claim, redemption and expiration were designed as explicit product states so both sides understand what happens next.

MiamiGo claimed offer screen — CLAIMED -> PRESENT -> REDEEMED / EXPIRED

MiamiGo redeemed offer screen — CLAIMED -> PRESENT -> REDEEMED / EXPIRED

01 / 03

The same product has to work from the other side of the counter.

Venue onboarding turns a business need into a guided operational path: enter the partner experience, create the account, establish the venue and move directly toward publishing an offer.

01 · ENTER BUSINESS
Business portal
The venue side starts from a focused partner entry point, not the consumer browsing experience.
02 · CREATE ACCOUNT
Create business account
Account creation collects the minimum structure needed before asking the venue to publish anything.
03 · ESTABLISH VENUE
Account created
The product confirms the business context, then moves the operator toward the next meaningful action.
04 · CREATE OFFER
Create offer
Offer creation becomes the operational bridge between venue setup and measurable consumer demand.

01 / 04

Publishing is a lifecycle, not a button.

The offer model includes creation, preview, live states, editing, pausing and expiration. Designing these operational states makes the product usable beyond the happy path.

LIST

Offer list

The venue can see offer status and manage published inventory from one operational surface.

Measure what happened after discovery.

Views and taps are only part of the story. The venue experience was designed to surface claim activity, offer performance and time-based patterns so operators can learn what demand actually converted.

01 / 02

INTEREST

Views and offer engagement

INTENT

Claims created

OUTCOME

Redemption and performance

TIMING

Best time and day signals

One system across two very different workflows.

The consumer and venue sides share the same foundations, interaction language and reusable patterns. The system keeps MiamiGo recognizable while supporting very different tasks and information density.

From local discovery to a closed-loop demand system.

The design treats consumer discovery and venue operations as one connected product system. A shared offer object carries state across discovery, decision, claim, redemption and measurement, creating a measurable loop instead of two separate interfaces.

CONSUMER CLARITY

A clearer path from “what is nearby?” to a confident action.

VENUE ACTIVATION

A focused operational path from business setup to publishing and managing an offer.

PRODUCT LEARNING

A measurable loop that can connect discovery behavior with claims and venue performance.

NEXT VALIDATION

Claim-to-redemption rate · Venue activation · Repeat discovery · Offer performance by time window

Next project: GoPool