You love to travel and don't want to waste time managing logistics or making decisions while you're on a trip.
You enjoy the process of planning – the anticipation and preparation are nontrivial contributors to your overall enjoyment.
You gravitate towards spreadsheets when you need to organize information.
You want all your confirmation numbers and other trip details available on your phone, in one place and available offline.
You need to share your itinerary with other people, whether they're travling with you or not.
You still use Foursquare/Swarm, and hate having to guess which venue is the right one, especially in places where you don't read the local language.
Spreadsheets are great for organizing infromation, but they are not great for referencing that information on your phone with luggage in tow while rushing to catch a Shinkansen. Fortunately, tabular data is relatively easy to transform into other formats, such as a calendar that you can view natively on whatever device you choose, with whatever information is applicable.
In this guide, we'll follow a simple template to create the columns for your trip's Google Sheet, and then using Google Apps Script, we'll publish an .ics file that you can subscribe to in the calendar app of your choice. We'll conclude with a couple of examples from real trips.
You'll notice that these example trips have every minute accounted for. Some might view this a rather extreme style of trip planning, but it's worth considering:
Probably! It could be viable B2C, perhaps with a per-trip fee. One challenge is Google's (justified!) rules and warnings about third-party app authorizations, so you might need to use a different online spreadsheet application – maybe there are even open-source or white-labeled options.
Alternatively, it could be viable as a SaaS app for travel agents or tour operators.
Consider using Airtable instead of Google Sheets and Google Apps Script. Airtable almost makes this trivial with a calendar view that is shared via a link, but unfortunately they currently do not allow you to specify the location
, description
, or other VEVENT
properties. Please feel free to contact support@airtable.com to request this enhancement.
Research open source calendar hosting software. They probably store events in some sort of database, and perhaps it's cleaner to build a simple CRUD API directly on top of those tables. There's something about generating the VEVENTs myself that feels inelegant and brittle.
[object Object]
After giving this more thought, I'm leaning back towards a CalDAV server with Airtable as the database. The server can/should be read-only, which might make it much easier to build, less locked-in to Airtable, and perhaps not that hard to spec out for Upwork/etc. Also, the similarities between CalDAV and CardDAV (both based on WebDAV) might mean that a lot of the code can be re-used between Travel Planning, Vacation Day Planning, and Contact Management.
:
: