2
1 Comment

How should a budget-food map warn that a price may be stale?

Disclosure: I run Fooglemap, a live affordable local restaurant and meals map.

I am testing a source-freshness problem on the Busan city page rather than trying to claim complete coverage.

One concrete record is Suje Mandujip in Sasang-gu: 10 handmade dumplings listed at KRW 4,000, with the page last updated 2026-04-29 and a map/directions link.

The limitation matters: the price may have changed, coverage is incomplete, and this is not a comprehensive Busan restaurant guide.

Before a visitor opens directions, which freshness signal would you trust most: a prominent last-checked date, a price-confidence window, a one-click correction report, or the original source?

Prototype: https://fooglemap.com/bmap-city/busan/?utm_source=indiehackers&utm_medium=community&utm_campaign=fooglemap_busan_2026q3&utm_content=2026-07-30-price-freshness

Drafted with AI assistance and reviewed against the live page.

on July 29, 2026
  1. 1

    I think this goes beyond freshness.

    A stale price is frustrating, but uncertainty about whether the information can be trusted at all is what usually determines whether someone acts on it. The way users interpret that uncertainty is probably more important than the specific signal you choose.