Now Here

The city is alive.
You just can't see it.

Most event discovery tools are built for planners. You open Eventbrite on Sunday night, find something for the weekend, buy a ticket, go. That flow works — but it leaves an entire mode of being completely unserved: the spontaneous mode. Already out. No fixed plan. Open to whatever's happening within walking distance right now. That moment has no tool built for it.

Social media is a highlight reel of things you missed. Friends mentioning it the next day. News coverage after the fact. Every passive discovery channel delivers awareness after the moment has passed — or never at all. The structural failure is the same: discovery happens too late, and location is treated as a filter rather than the starting point.

I go to over a hundred shows a year. I play in bands. I organize DIY events across Seattle, Chicago, and Pittsburgh. The gap this product addresses is one I live with — the constant, low-grade frustration of finding out about something amazing the morning after. This isn't an abstract design exercise. It's a tool I want to exist.

Who feels this — and how.

Conversations across two cities with planners, spontaneous attendees, and event hosts surfaced a consistent pattern. Planners had built workarounds — newsletters, artist alerts, weekly routines. The gap was felt most acutely by people who don't operate that way. Physical proximity is the oldest form of event discovery, and it still works best. Flyers on lamp posts. Music from a block away. A crowd forming on a corner. Every digital tool has moved away from that model. Now Here is a return to it.

Current state — Jordan's experience before Now Here

The data strategy is the product.

The hardest design problem wasn't the map or the filters. It was the data model. The UX is only as good as the events on the map — and building a trustworthy, comprehensive, real-time event database is genuinely difficult. Now Here aggregates from three layers, deduplicated into a single canonical pin per event. Pin color encodes trust at a glance: users learn the system passively through use.

What I learned.

The flyer scan feature taught me something about where friction in a product actually lives. The obvious friction point was the submission form — too many fields. But the deeper friction was the gap between "I'm physically looking at this thing" and "I can do something about it." Reducing the form wasn't enough. The camera was the answer.

I kept coming back to the question of scope. Now Here could do a lot — social features, recommendations, past event history. All of those are real. All of them are later. The discipline of building for one moment — already out, open to anything, right now — made every product decision easier. When a feature doesn't serve that moment, it doesn't belong in MVP.

This is a concept project. The deeper documentation — sixteen design decisions with full rationale, the strategic and competitive analysis, the validation plan — is available on request.