Project story / Somewhere · 19 Jul 2026
Building the day-trip planner I actually wanted to use
Somewhere began with a Replit hackathon, which was a useful forcing function: choose a problem, make the idea concrete and get something working. The event ended, but the product stayed interesting because it solves a problem I still have myself.
Planning a day out sounds simple until the constraints appear. Where can I reach in the time available? Is the journey realistic by train or car? Does the destination contain enough things I care about? Can those places form a sensible route rather than a list of pins scattered across a map? Most discovery products answer one of those questions and leave the rest as homework.
From inspiration to an itinerary
The core idea is to turn a few preferences into a day that could actually be followed. Somewhere takes a starting location, travel-time limit, transport choice and interests. It can suggest destinations, check them against real journey times, then build an itinerary from places of interest, lunch and the routes between each stop.
That two-stage flow was an important correction. Asking an AI to produce a complete trip in one response is easy to demo and difficult to trust. Separating destination discovery from itinerary generation lets the system validate the big decision first. Once someone chooses where they are going, the search can become local and specific.
The itinerary itself combines different kinds of work. Open map data provides candidate places. AI helps curate a coherent set rather than blindly returning the most popular results. Routing services check whether the order makes sense on foot or by public transport. The product value sits in that orchestration, not in pretending one model already knows every opening time and travel connection.
The unglamorous product work
A hackathon rewards the visible path. A product has to survive repeated use, unreliable services and a bill. Some of the most important work after the first version was therefore defensive: rate limits, caching the expensive parts of the generation pipeline, monitoring failures and putting boundaries around free usage.
That work does not make for the best demo, but it changes whether I would feel comfortable letting other people use the app. A generated trip is only useful if the system can explain failure, avoid wasting paid requests and return enough consistent information for someone to trust a day of their time to it.
The product is not the itinerary text. It is the confidence that the day holds together.
Why it is unfinished
Somewhere is not one of the projects I want to describe as done. The app has a substantial working foundation, but the positioning, discovery experience and operational shape still need attention. It also needs the simple test I care about most: would I repeatedly choose one of its plans over doing the research myself?
That is why it remains active rather than moving into an archive. Unlike an idea that was only entertaining during a hackathon, I can picture opening Somewhere on a free Saturday morning and asking it to get me out of the house. Adding features can wait. The next useful phase is returning to the core journey: using it for real trips and tightening every point where the generated plan loses credibility.
The hackathon proved the concept could exist. The more interesting job is making it dependable enough that I stop thinking of it as a hackathon project at all.