Going private to make the inside beautiful

The reliability month was about trust. Once trips lived safely in the cloud and followed you across devices, the next question was harder to answer with code alone: does the inside of the product actually feel good to use? So Voyra went quietly private behind a waitlist, and I spent five weeks making the inside beautiful. This is the honest version of how that went, including two features I built and then took back out.

If you missed the foundations, the post on making every trip permanent covers the month before this one.

One home, opened by invitation

The first job was plumbing, and it was the kind nobody ever sees. Trips you sketch on the map in Explore and trips you plan in the itinerary had been living in two separate places. To make a route flow straight into a plan, those two had to become one. That meant merging two databases into a single store and re-keying every record so nothing lost its place.

It is invisible when it works and very visible when it does not, so I did it carefully over one long evening rather than rushing it across a busy day. When it was done, an Explore link sat quietly on the itinerary and a route you drew on the map could become the bones of a real trip.

Then I closed the doors. Voyra moved behind a waitlist with a clean sign-up page, so the public site could collect interested travellers while invited testers got straight in. Going private sounds simple. It was not. Testers got bounced in a loop between the landing page and the home page, and a sign-in snag needed chasing down before anyone could actually get in. Most of that week was unglamorous gate-keeping, the work that earns no screenshots.

Bookings, and the story of a trip

With the doors managed, I turned to the parts of a trip that travellers actually juggle.

Bookings got real structure. The page was rebuilt into three clear tabs, Accommodation, Transport and Experiences, each with partner links out to go and book, and a simple way to record what you have already locked in. You can mark a stay as confirmed, jump out to search, and pull the link back into the right day. The itinerary stays the single source of truth; bookings just hang off it where they belong.

Attachments got friendlier too. You can tag a file to a specific part of a day and rename it inline, the small things that make a folder of confirmations feel like part of the trip rather than a pile beside it.

Then the Timeline. A finished trip deserves to read like a story, not a spreadsheet, so I built a narrative Timeline that turns your trip into a scrollable journey, grouped by city, with a hero header and photo moments pulled from your memories.

A finished trip deserves to read like a story, not a spreadsheet.

Here is the honest part. I built that Timeline, then deleted it, then rebuilt it, all inside two days. The first version shipped with a toggle between a story view and a day-by-day view, two ways to look at the same trip. On reflection the toggle was clutter. It asked the traveller to make a choice that did not need making. So I scrapped it, threw out six old files, and kept a single clean narrative view. Calling a feature done twice in forty-eight hours is not a great look, but it is the truth of how the good version got made.

One quieter change landed this stretch and it matters more than it sounds: deleting a trip or clearing a long itinerary now asks you first. A stray click can no longer wipe your work.

The dashboard, and the smart feature I removed

The trip home screen was the last big piece. I rebuilt it as a set of arrangeable cards: today's plan, your route, trip readiness, budget, memories. You could drag them, hide them, reorder them to suit how you travel. Two ways to get around as well, a classic side menu or a slim top bar, your choice. The whole app finished moving onto one shared design language top to bottom.

I also built something clever into it. A phase system that reshuffled the cards depending on where you were in the trip, one layout before you leave, another while you are travelling, another once you are home. On paper it was the smartest thing on the page.

In practice it was the main source of the layout bugs. Cards landed in the wrong place. The arrangement you set did not hold. Every odd report traced back to the same clever mechanism quietly rearranging things behind you.

So I pulled it out entirely. Now every trip starts from the same clean layout, and the cards simply adjust their wording for before, during and after, rather than rearranging themselves. Removing the smart feature was the fix. That redesigned, simpler dashboard is what shipped live.

This keeps happening across the build, and I have stopped being surprised by it. Earlier it was road-following map routes reverted to plain straight lines. Here it was a card-shuffling dashboard reverted to one steady layout. The calmer choice is almost always the better one. Voyra is meant to organise the trip you are already planning, not perform cleverness at you.

The dashboard settling marked a shift. With the inside looking right, attention moved from polishing individual pages to walking the whole journey a first-timer takes, which is where the next post picks up.

Voyra is live and free to use. Start planning if you want to plan your next trip somewhere calmer.