Written when there’s something to say. Honest, short, unedited.
For a lot of people, “where to eat” quietly means “where that’s pure-veg.” Simple to ask for, less simple to get the data clean. For the people who don’t want to scan every result twice, it’s the first thing they reach for. Asked for it enough that it stopped being optional.
A thousand ‘where to?’s answered in under 24 hours. Either people are very hungry and indecisive, or just checking if their favourite nearby spot is recommended. Probably both.
Two threads: getting found at all, and making the pick less generic. Chains nudged down, hotels pushed out, and a small memory that leans toward what you keep choosing.
Spent the day on the unglamorous half — wording, timing, the little ways things appear and settle. None of it lands as a feature; all of it lands as feel.
A lot happened under the hood today — the kind you don’t see. It’s starting to feel real. Had to test it on our own to believe it.
Realised people want to use just one filter at once maybe, not always both at once. Reach-time only. Or just distance. Gave each one its own on/off switch.
Prelaunch live, v1 shape settled. More time on the foundations than the surface — both smaller and quieter than the first sketches, on purpose.
Domain bought: whereto.food. personally, i just called it “wtf” because I didn't clearly know what I was trying to get done.
Planned to build this to finally stop wasting several minutes every day deciding where to eat from, how far is it, how bad is the traffic. It wasn't just about the food — it was about the mental energy I felt wasted on the decision.
that’s all so far. more soon.