pink
#F489ADMiamiGo

Designing a
two-sided local
discovery product.
01
Two audiences. One product loop.
Consumers need a fast way to decide what is worth doing nearby right now. Venues need a simple way to activate demand during low-traffic windows and understand whether an offer created action. The product challenge was to connect both needs without building two disconnected experiences.
CONSUMER
What is worth doing nearby, right now?
VENUE
How can I turn an empty time window into demand I can measure?
02
What if the offer became the connection between discovery and measurable demand?
The core hypothesis was to make one shared object carry the experience across both sides of the product: 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
03
Make “what should I do tonight?” easier to answer.
Discovery was organized around time, proximity, visual context and offer value so the next action could stay obvious without turning MiamiGo into another generic 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 / 04
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.
01 / 03
05
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 / 04
06
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.
07
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
08
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.
Foundations
Colors, type and radius tokens
sky
#3ED6D0black
#0D0F10white
#FFFFFFwhite-55
#FFFFFF8Cwhite-5
#FFFFFF0Dstroke-pink
#F489AD33stroke-sky
#3ED6D033black-75
#0D0F10BFCANELA TRIAL
HeadlinesNEUE HAAS GROTESK
UI / BodyUI, effects & radius tokens
09
From local discovery to a measurable demand loop.
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