4 ms·
Quick update since both comments touched on this, shipped the budget filter this week, so worth closing the loop. On the price level data: the field was always
by prunax 7mo ago
Quick update since both comments touched on this, shipped the budget filter this week, so worth closing the loop.
On the price level data: the field was always there in the Google Places response, the app just wasn't surfacing it. We now map it on the proxy side, 1–3 become $ / $$ / $$$ directly, and we clamp Google's 4 to 3. The distinction between $$$ and $$$$ isn't meaningful when you're trying to find somewhere four people can agree on. 0 and absent both map to undefined and fall through to "Any." No extra API call, filtering is purely client-side on the already-loaded results.
UX is three chips below the category picker: Any · $ · $$ · $$$. Tap to filter, tap again to clear, resets on category switch. It only shows for Coffee & Casual, Restaurants, and Bars & Nightlife, not for Parks or Museums where price_level is sparsely populated and semantically odd. The honest caveat is that coverage is Google's, not ours. In Paris or London the filter works well; in a smaller city you might filter yourself down to three results. The "Any" default always shows everything, so it degrades cleanly.
I'll let you give a try! -> hugpoint.io