We Built a World Cup Trip Command Centre Because Chaos Was Getting Ideas

There is a moment in every big group trip where the spreadsheet stops being a planning tool and becomes a haunted filing cabinet.

You know the one.

Flights in one tab. Hotels in another. Match dates somewhere else. Someone has a screenshot. Someone else has “the updated version”. A booking confirmation is buried in Gmail under a subject line written by a robot with no love in its heart. The group chat contains useful information, technically, in the same way a landfill contains jewellery.

That was the early shape of the 2026 World Cup trip.

So we built an app.

Not a startup. Not a lifestyle platform. Not some venture-funded rectangle called Triply or VaycayPilot or whatever fresh nonsense is currently stalking Product Hunt.

We built a small, specific, slightly over-engineered travel ops console for a bunch of Australians crossing North America in pursuit of football, chaos, and probably several deeply questionable airport meals.

The Beast We Were Trying to Tame

The trip is not a weekend away.

It is a multi-city World Cup migration across Canada, the United States, and Mexico. Sydney to Vancouver. Seattle. Vegas. San Jose. San Francisco. New Orleans. Miami. Cancun. Los Angeles. Matches, flights, hotels, ferries, transfers, tickets, budgets, documents, bags, risks, and humans.

Especially humans.

Humans are the problem software has been trying to patch since the Bronze Age.

The same few questions were going to keep coming up:

Where are we today?
What is next?
What time is kickoff in local time and back home?
Where are we sleeping?
Who still needs to do admin goblin work?
What has this magnificent circus cost us?
Where did we put the booking reference?
Are we about to miss something expensive?

A spreadsheet can answer those questions, if you enjoy pinching and zooming in a hotel lobby while your soul quietly leaves through the emergency exit.

I do not.

The Idea: Less “Trip Planner”, More Mission Board

The app became a World Cup trip command centre.

Not a generic travel planner. Generic travel planners are built for imaginary people called “users” who take clean stock photos of cappuccinos beside passports.

This is for actual people on an actual trip, tired, roaming, sunburnt, full of stadium food, trying to work out whether the next critical action is “get an Uber”, “find the hotel”, “scan the ticket”, or “stop Adrian from opening another tab called final-final-v3”.

The goal was simple:

Put the trip brain in one place.

On the phone. Fast. Clear. Offline-tolerant. Low fuss. No ceremony. No login maze guarded by a SaaS goblin.

What It Does

The World Cup app now acts like a little field console for the trip.

It tracks the route, the days, the bookings, the risks, the budget, the places, the notes, the expenses, and the useful wallet-type references that future-us will absolutely need at the worst possible time.

The important bits:

Today / Trip Ops: what matters now, not what looked neat three months ago
Trip timeline: the route spine across cities and match days
Bookings: hotels, flights, references, and the fragile paper trail of civilisation
Risks ledger: the “this could bite us later” section, because future pain should be labelled early
Budget: costs in AUD, because pretending exchange rates are friendly is how the spreadsheet demons win
Places board: useful stops, things to do, match-day targets, food, bars, transport points
Expenses: shared costs without needing a forensic accounting team in the group chat
Wallet references: the important little numbers and links that always vanish when roaming data gets spicy
Offline/PWA bones: because stadium Wi-Fi is not infrastructure, it is a rumour

It is not trying to be beautiful in the fake Dribbble sense. It is trying to be useful while someone is walking through an airport with 7kg of carry-on, 18 percent battery, and the emotional texture of a boiled sock.

That is the design brief.

The Tech Stack, Mercifully Not Dramatic

The first version is a PWA: web tech, phone-first, installable, cheap to host, quick to change.

Static frontend where possible. SQLite-backed API where shared mutable data actually matters. Local/offline behaviour where reality requires it. Hosted in the lab, served out like a tiny travel goblin with a clipboard.

Public home:

https://wc.integrate.network/wc2026/

There is no grand architecture astronauting here. The app exists to survive contact with travel.

The stack has one job: answer the question before the group chat becomes a crime scene.

Why Not Just Use Google Sheets?

Because Google Sheets is where trip enthusiasm goes to become admin mulch.

Sheets are great when planning. They are less great when you are outside a stadium trying to work out which booking applies to tonight, whether the next city has a transfer gap, and why the hotel confirmation is in someone else’s inbox under “Reservation confirmed”.

The app is not replacing the planning source of truth. It is turning that source of truth into something usable in motion.

A spreadsheet is a warehouse.

This thing is the forklift.

The Best Feature Is Trust

The quiet trick with this kind of app is not feature count. It is trust.

Can I open it and immediately know what matters?

Can I use it while tired?

Can someone else in the crew understand it without a guided tour and a whiteboard?

Can it help us avoid the dumb expensive mistakes, missed transfers, lost booking references, forgotten documents, double-paid nonsense, and “wait, who booked that?” moments?

If yes, it is working.

A travel app does not need to be clever. It needs to be calmly useful while the humans are becoming less clever by the hour.

The Fun Part

The fun part is that it feels less like building software and more like building a tiny control room for an adventure.

The match schedule is not just sport data. It is the drumbeat of the trip.

The route is not just cities. It is a trail of future stories, airport benches, questionable diners, and one or two moments where everyone stands around saying “surely this is the right terminal”.

The budget is not just maths. It is the grim little oracle that tells us how much joy costs in Australian dollars.

The risk ledger is my favourite sort of grim practicality: a labelled shelf for future problems, so they stop lurking in the walls.

And the offline wallet is pure travel superstition made useful. Keep the important stuff close. Assume networks will fail. Assume batteries will die. Assume the one PDF you need is hiding behind a loading spinner with the moral character of a raccoon.

What We Learned

A good trip app is not about travel content. It is about reducing panic.

Nobody needs another generic list of “top 10 things to do in Miami”. The internet is already screaming that at us through a megaphone.

What we need is:

the next action
the right booking
the right address
the shared cost
the crew status
the match-day plan
the thing we must not forget

That is the difference between a travel guide and a trip brain.

Also, mobile-first is not optional. If the app only feels good on a laptop, it has already failed. Nobody is opening a laptop in a rideshare to check the hotel address unless the trip has entered its cursed phase.

What Comes Next

The current version has the bones. The next evolution is making it more like a proper field companion.

Things on the radar:

Match Day Mode: run-sheet, ticket links, venue notes, transport, meetup points
Travel Day Runbooks: airport, hotel, transfer, check-in, and “do not forget this” steps
Decision Mode for risks: turn vague worry into clear options and deadlines
Crew Readiness Matrix: who has documents, tickets, insurance, payments, and app access sorted
Ground Transfer Planner: because “we’ll figure it out there” is how money catches fire
Offline Wallet upgrades: better cached documents, references, and search
Expense settlement: less “who owes what?” and more “pay Steve before he becomes feral”

This is the good kind of feature list: all of it exists because travel will generate the problem whether we build for it or not.

Final Whistle

The World Cup app started as a way to make the trip less messy.

It is becoming something better: a pocket-sized mission board for a once-in-a-lifetime football pilgrimage across North America.

It will not prevent delayed flights, weird hotel carpets, stadium queues, roaming issues, or the ancient group-trip ritual of someone asking a question answered three messages ago.

But it will give us one trusted place to look.

And sometimes that is the whole game.

Built in the lab. Powered by football, travel anxiety, and the ancient engineering principle that every group chat eventually needs a database.