← All projects
Live

Case study

itinerary tracker.

Gives a traveller the whole trip on one page they can use on the street: countdown, flights, a day-by-day timeline and a checklist, drawn like a Japanese picture book.

Role
Designed & built end-to-end
Type
Mobile-first web app
Status
Live on GitHub Pages
See the demo ↓
Itinerary Tracker

The spark

Trip plans live everywhere except where you need them: flight details in an email, the day's route in a chat thread, the to-buy list in a notes app. On a train platform in Tokyo, nobody wants to search three apps. The question was what the smallest possible thing is that puts the whole trip in one place, and is pleasant enough that you actually open it.

The problems to solve

  1. P1

    Trip plans are scattered across apps

    Searching three apps on the move is slow, and one trip page only helps if people actually want to open it.

  2. P2

    Planning tools are built for the laptop, not the trip

    Travel planning tools serve the planning phase: on a laptop, weeks before departure. The trip itself happens on a phone, often one-handed and half offline, with one question in mind: what's next and how do I get there?

  3. P3

    A new trip should not mean a new page

    The goal was the smallest possible thing that holds a whole trip. If the itinerary were written into the layout, every new trip would mean rebuilding the page instead of swapping in new data.

How it works

  1. 01

    Countdown & flights

    The home view counts down to departure and shows outbound and return flight cards, the two things people check most before a trip.

    SolvesP1P2

  2. 02

    Day-by-day timeline

    Day tabs switch a time-ordered schedule; transport is colour-tagged by type and the can't-miss stops are flagged, so the day reads at a glance.

    SolvesP1P2

  3. 03

    Lodging & checklist

    Where you're sleeping, plus a to-do list that strikes items through when ticked. It remembers them, along with the last day you viewed, in the browser.

    SolvesP1

  4. 04

    Edit three constants

    The whole trip is data: a departure time, a list of days and a to-do list at the bottom of the file. Changing the trip never means touching the layout.

    SolvesP3

Product decisions

One HTML file, zero dependencies

It's vanilla JS and one web font, with no framework, build step or backend. It loads fast on patchy mobile data and hosts free on GitHub Pages. Anyone can fork it by copying a single file.

SolvesP2P3

Data separated from design

Itinerary content sits in three constants and isn't written into the markup, which is what lets the page work as a reusable template.

SolvesP3

Animation you can turn off

The hand-drawn SVG illustrations gently move (floating, drifting petals, a passing train), but every animation stops for people who ask their system to reduce motion. Tabs and the live countdown are labelled for screen readers.

SolvesP1

Built with

Product
HTMLCSS (keyframe animations)Vanilla JavaScriptHand-drawn SVG
Browser APIs
localStorageIntersectionObserverprefers-reduced-motionARIA tabs + live region
Delivery
GitHub PagesGoogle Fonts (Huninn)

Demo

Live site, shown at phone size because that's where it's meant to be used. Switch days and tick a few to-dos.

Open the live app ↗Interactive. Scroll and click inside the frame.

Outcome

A live, mobile-first itinerary that works as a template: the structure follows the official GO TOKYO five-day route, with sample times, flights and lodging, so a new trip only needs new data.

What's next

  • Offline support with a service worker, for metro tunnels and spotty roaming.
  • Fill the itinerary from a shared Google Sheet so a travel group can co-edit.
Next projectStandfirst

let's build something. ✦

Happy to talk about products, AI and the calls behind them.

Say hello