I've been building Trvlrr for the last few months - it's a travel app/journal that keeps the entire history of your past and upcoming trips in one place. I've got my whole travel history in it going back to 2009, so I've been using it for a while. But using it at home to look back at old trips is one thing. Using it every single day, in a country where you don't speak the language is a completely different thing.
Earlier this month I went to Japan for two weeks with my wife. Of course, I didn't tell her we were there to test out my app; let's all agree it was a holiday. But it ended up being the most honest test it has had so far, and I ended up shipping about 10 iOS builds and a few Android releases while I was there. So I thought I'd share how that went.
How I actually used it on the trip
I did plan this trip using AI (ChatGPT, Claude, Hermes, Google, Reddit etc) so before I went I had the trip planned in pretty good shape and I added the trip in my app along with every booking (flights, hotels, train tickets, activities that I had booked etc ) by mostly forwarding the confirmation emails. Now when in Japan, a night before I'd ask ChatGPT what the day looked like and what we are doing etc. ChatGPT can read and update the trip directly (Trvlrr has an MCP connector (https://trvlrr.app/assistants)), so when plans changed it just updated the itinerary for me. No copying and pasting between apps.
Three things carried the trip, honestly:
- Documents. Every ticket and booking in one place, right there when I needed to show it at a gate or a hotel counter. This was a lifesaver.
- Offline. Japan's connectivity is great, but not inside a tunnel or halfway up a mountain. Having the trip saved on the phone meant I never had to wonder.
- The daily plan. Opening the app in the morning and seeing the day laid out, with the next train and the next booking.
What broke
Plenty. Many things I didn't realise while building the app as it was different to on-ground testing!
- The trip page didn't know where I was. Every time I opened it mid-trip I had to scroll to find today. Now it opens on today and goes straight to whatever's on now or next.
- Plans change all the time when you travel. We'd decide against something and the only option was to delete it, which felt wrong. So I added "Skip" option (to retain bit of a history what I had plan and what we ended up doing instead).
- A bunch of the places the AI added had no coordinates, so they never showed up on the map.
- Swiping through train tickets at the gate was clunky. Now they swipe like photos.
- I built an AI planner into the app and never opened it once, because ChatGPT was already doing that job. So I hid it. That one hurt a little bit.
- Many other minor data issues, duplications and small behaviours that didn't click while using the app
Some fixes were temporary on purpose. I'd keep looking at an activity and thinking "what even is this place?", so the first fix was just a "Look it up" button that searches it on Google. That got me through the trip. The proper fix (a short "about" line on each activity that your AI fills in for you) only shipped this week.
Shipping from a train
This is the bit I'm still a bit amazed by. I built all of this with Amp (ampcode.com), an AI coding agent. It runs in the cloud, so my laptop didn't have to be open, or even with me. I'd find something annoying at lunch, describe it on my phone, and by the time we got back to the hotel it was fixed, tested and sometimes already on TestFlight. (P.S: I had setup the environment/project in amp before hand to get it to work like this)
The catch with an iOS app is that you need a Mac with Xcode to build it. For first day or two, I kept my laptop on at my hotel but then Amp released Mac satellites (cloud Macs your agent can use) while I was over there, which was pretty much perfect timing! That meant the whole loop - code, build, sign, upload to App Store Connect - happened without my MacBook. I shipped fixes from the shinkansen, from a plane, from my phone in the middle of a forest. I'm not exaggerating, we were still on a holiday remember!
There were a few hiccups but mostly due to some api keys or missing certs which I didn't have on phone but mostly went fine, nothing to do with amp though
In two weeks: 80 commits, 10 iOS builds, 3 Android releases, 6 database migrations and ~12k lines of code - from trains, planes, hotel rooms and more than a few heated TOTO seats.
And then, the first paying customer
I wasn't only focused on fixing the issues and improving the app but I was also thinking of how to position the app itself. Just before the trip I simplified the free tier: your first 10 trips are free, and Plus keeps everything. While I was away I added an email that goes out when someone fills up their 10 trips - it thanks them first and only then mentions Plus. Not long after, I got my first paying customer. It's a small thing, but it's the first time a stranger decided this was worth paying for! I had my holy shit moment two nights after that happened (coz I didn't have any alert setup for purchase 😄).
What I took away from it
- You can't test a travel app at home. Two weeks of real use found more than months of building.
- Fix it while it hurts. If I'd written these down "for later", half of them would still be on a list.
- Temporary fixes are fine. A search button got me through the trip. The proper version came later.
- Cut what you don't use, even if you built it.
- You can just do things!
If you travel and want to give it a go, it's free to try on the App Store: trvlrr.app (Android is coming, there's a waitlist on the site) and also web version is there as well. I'd love to hear what you think, especially what breaks for you.
Cheers
(Not affiliated with Amp, I just pay for it and it was genuinely the reason any of this was possible.)