Focus
Discovery UX
Map · Event details
ROLE
Solo Designer
Self-initiated project
Timeline
1 week
2025, personal sprint
Tools
Figma
Wireframes & hi-fi
—— THE PROBLEM
The event page carries the decision.
Address, dates, and category sit above the fold. Two small pill badges — "Limited seats" and "3 days left" — signal urgency without alarm. A single blue CTA ("Save Event") replaces a form or account gate: the user commits with one tap, and the app remembers.
Why it works: Every element on this page answers a question the user is already asking — is it still on? is it close? can I still get in?
KEY SCREEN
——PROJECT SNAPSHOT
One-page overview — problem, wireframes, high-fidelity screens, and prototype flow.
SCROLL FOR THE FULL STORY ↓
—— Reflection
PopUpEase was an exercise in restraint. It would have been easy to bolt on ticketing, reviews, follow-a-brand, or social feeds — every one of those exists in adjacent apps. But the actual pain point was small and sharp: is this pop-up still on, and can I get there before it closes? Everything else was noise. The final concept is a smaller product than my first draft — and, I think, a more focused one. It was a one-week personal project, not a shipped product.
—— Final Designs ——
Three screens that carry the whole product.
Home, Map, and Event Detail — each optimized for a different mode of decision-making: browsing, orienting, and committing.
—— Takeaway ——
What this project taught me.
—— User Flow ——
Four screens from open to intent.
The whole flow is designed to fit inside a single subway ride. No account gate, no onboarding — the app opens straight to what's nearby.
—— Validation ——
A small check before committing to the direction.
Before locking the "decision speed" thesis, I ran short conversations with 4 people who had recently tried to visit a pop-up event. The sample is small and self-recruited — enough to sharpen the design direction, not enough to make a general claim.
—— Core Insight ——
Discovery isn't the problem — decision speed is.
My hypothesis: the bigger friction may not be initial discovery, but quickly deciding whether an event is still active, nearby, and worth the trip. I checked this with a short round of user conversations (see “Validation” below) before committing to a decision-speed design direction.
—— THE PROBLEM
Pop-up information lives everywhere — and reliably nowhere.
Pop-up events are inherently time-sensitive: a store might open for three days, a café for a weekend, an art show for a week. But the information that would help someone actually go — location, hours, whether it's still running today — is scattered across Instagram stories, neighborhood blogs, and half-updated Google listings. By the time a user pieces it together, the event is often over.
Recent Designs
