Travel Guide

A day-by-day plan that actually works

Things grouped so you are not crossing the city twice. Timings that assume you are a person and not a schedule. Meals where you will actually be standing. And an honest split between what has to be booked weeks out and what you can simply walk up to.

A plan is a structure of decisions, not a list of facts — which is the only way to build one honestly, because most of what an itinerary is normally made of expires. Which things sit near which, what order a day goes in and why, how long a kind of place absorbs: durable. A seasonal pattern or a rough city size: slow-drift, and it carries the year it was true for. An opening time, a price, a closing day, a booking window, a timetable, whether a restaurant survived the winter: current-state — this app will not state those at all, in any form, because it would state last year's version in this year's voice and you would plan a morning around it. It names who holds each one instead.

A city, a region, an island. Small and non-English-named places are fine.

Add it when the name is shared. There are a lot of Springfields.

A month or a season is enough. It changes the shape of a day.

Only used for the calendar export. Nothing in the plan depends on it.

This is the input that changes the plan most. A toddler, a bad knee, a teenager who hates museums, four friends who want a late night — each of those rules out different days.

What you actually care about

Pick a few. Picking everything is the same as picking nothing.

A level, not a number. This app does not state prices.

Name a destination to see what a run reserves.

Constraints are more useful here than wishes. What you cannot do shapes a plan harder than what you want to.