A subscription, not an export
Stub hands your calendar app a URL, not a file. Apple Calendar takes the webcal:// form in one tap; Google Calendar takes the https:// form under From URL. The calendar app re-reads it from then on.
So a change to the trip is a change to the feed. Move a hotel night, add the flight you were rebooked onto, and the calendar has it the next time it refreshes — nothing to export again, nothing to re-import. Stub asks calendar clients to hold their copy for up to an hour, so the update lands on their schedule rather than the moment you make it.
The link is the credential: the feed checks the token in it and nothing else, so it goes into your calendar app and nowhere else.
Every trip you're on, in one feed
One subscription per person, not one per trip. The feed carries every trip you're a traveler on — the ones you added and the ones somebody else added you to — which is why the control sits on your trips list instead of inside a single trip.
Archive a trip and it leaves the feed. A cancelled item, and an item with no time on it, never enter it: the feed is rendered from the trips as they stand at the moment your calendar app asks.
Every event carries the title, the time and the place, and nothing else
Every dated item on the trip becomes one event, titled the way the trip titles it: a flight as its number and both airports, a stay as Stay: and the hotel, a car or a seaplane as Transfer: and where it runs. The trip itself is one all-day event across its dates, marked free, so it banners the days without blocking them.
An event carries a title, a start, an end and a location. It has no description field at all — no confirmation number, no record locator, no cost, no points. A calendar store is the least-secured surface most people have, and the feed is written on that assumption.
Where it lives
- App
- Your trips
New here? Signing in creates your Miles account.