You build a map view with an "open now" toggle. It's the kind of feature you ship in an afternoon and mostly forget about — until someone tells you they drove across town to a place your app marked open, and stood in an empty parking lot reading a handwritten sign about a private event.
The pin was in the right spot. The name and address were correct. The one fact that mattered in that exact moment — is it open right now — was a guess wearing the same formatting as everything else on the card.
1. What goes wrong with a friendly default?
A place without a published detail is a very common thing, not a rare edge case. Plenty of small venues don't post hours anywhere obvious, or they post them once and never touch the page again after the schedule changes for a season. The tempting fix is a reasonable-sounding default — most places like this are open weekday mornings, so assume that until proven otherwise.
The problem isn't that the default is usually wrong. It's that it's indistinguishable from a real, confirmed answer once it's sitting on a card next to a name and an address. Nothing about "9 to 5" tells you whether that came from the venue's own page or from an assumption filling a blank field.
2. What did we decide instead?
We treat hours and admission details as facts that need evidence, not fields that need filling. A place's hours count as known when something actually supports them — a stated schedule on the venue's own page or other direct evidence. Short of that, we say we don't know yet, instead of quietly supplying an average.
That trade-off costs us coverage. Plenty of places sit with an honest gap where a guess would have looked more complete on a dashboard. I'd rather have that gap than a card that looks finished and sends someone to a locked door.
3. What does "more than a pin" actually mean?
A pin answers "where." It says nothing about whether you can walk in right now, what it costs, or whether this is even a good day to go. Those facts change on their own schedule, independent of the address, and they go stale in ways a location never does. Treating a place record as just a point on a map, with hours bolted on as an afterthought, undersells how much of what someone actually needs to decide has nothing to do with geography at all.
4. What does this mean for how you'd use it?
If you're building something that answers "can I go there right now," check what backs the hours you're showing, not just whether the field is populated. A populated field and a confirmed one look the same in a response; they are not the same claim. Build your "open now" logic, and any confidence you show a user around it, assuming some places will honestly have no answer yet — and treat that gap as information, not a defect to paper over before launch.
Why this matters if you build on local data
A place is a moving target dressed up as a fixed one. The address barely changes; almost everything else about whether it's worth visiting right now does. If your product tells someone a place is open, that sentence deserves the same scrutiny you'd give a date or a price — where did this come from, and how sure are we, really. A pin on a map was never the hard part.