Tourlet

Tourlet does not exist yet. This page describes the plan, not a released app — there is no install link on it, because there is nothing to install. It will be replaced by the real thing as it is built, not backdated to look further along than it is.

The problem it is meant to solve

Planning a trip usually ends up spread across a dozen places: a flight confirmation email, a hotel booking in another app, a shared document with the day-by-day plan, a photo of a train ticket, a note with the Wi-Fi password for the flat. None of it is in one place, and the one moment it matters most — standing at a gate, or a platform, with patchy signal — is the moment it is hardest to go and gather. That moment is sharpest on a trip that moves between cities: the thing most likely to go wrong with patchy signal is not “what time is the museum” but “what time, in which timezone, does the overnight train actually get in.”

Tourlet is built for the trip that moves between cities, joined by long legs — a domestic flight, a high-speed or overnight train, a ferry, a long-haul bus — the kind of trip (Beijing → Chengdu → Shenzhen is the case it was designed against) where a day-by-day planner built around one destination has no natural place for the leg that actually shapes the trip. Tourlet holds that leg as a first-class thing, alongside the places it connects: one itinerary, on the device that travels with you, readable without hunting through email, and readable without signal.

What is actually decided

Not much yet, and this page says so rather than implying otherwise:

• An Android app, phone first (name.gpm.tourlet).
• A trip is a sequence of places joined by legs — flights, trains, buses, ferries — each shown in its own timezone, not a single day-by-day plan around one destination.
• A Wear OS companion is planned, with at least a tile and a complication for a glance at “what’s next on the trip” from the wrist — not built.
• A home-screen widget is planned, for the same reason.
• An optional sync, through a backend of Tourlet’s own, so an itinerary can follow a person across devices rather than staying trapped on the phone that made it — optional, and off until asked for.
• No location tracking today. Nothing in the current plan reads or stores where the device is; the app currently declares no location permission at all.

Everything past that — which screens it has, what a day actually looks like on screen, what if anything is a paid tier — is being worked out in the design brief, not decided yet. See the docs repository for the current state of that work, including the open questions it has not answered.

Where things stand

There is no build to try and no store listing. The changelog will start the day there is a first release to describe; today it says exactly that and nothing more.