0+
September 24, 2026
September 23, 2026
Travel App is a WP App, an app for WordPress with the primary focus of being
used by yourself, or your family or social group. It can only be accessed logged-in
and adds a menu entry to the Masterbar to be reached.
Travel App is a private travel organizer that allows you to organize travel itineraries
as timelines. You can paste booking confirmations, calendar exports and itinerary notes,
and Travel App turns them into a structured trip: flights, lodging, trains, rental cars,
activities and anything else you want to keep track of.
There are lots of other small features:
– map view (with Open Street Map),
– journal entries per day,
– you can share your trip with a link,
– subscribe to your trips in your Calendar,
– access your trips (including reservation files) offline, and
– delegate another user on your site to create or edit trips on your behalf.
As every WP App, Travel App comes with support for the Abilities API by providing all
the abilities necessary to use the app with an AI.
If WordPress has AI Connectors configured, it will use them to better parse your pasted
booking confirmations.
You find the source at https://github.com/akirk/travel-app
travel-app directory to the /wp-content/plugins/ directory/travel-app/ on your siteNo. ICS calendar files are parsed locally, and free-form text falls back to a
built-in parser when no AI connector is configured. An AI connector makes
importing messy confirmation e-mails better, it is not required.
No. Trips are taxonomy terms, itinerary items and journal entries are custom
post types, and the rest is post meta and options.
Only you, unless you say otherwise. Trips are private to their owner; the app
requires a logged-in user. Share links are created explicitly per trip and can
be removed again, and users you delegate to have to be granted the capability
you pick.
Yes. Each trip can be subscribed to as an ICS feed, and there is a feed covering
all of your trips at once.
Yes. Travel App is a Progressive Web App: the timeline is cached for offline use
and changes you make offline are queued and synced when you are back online.
The map uses OpenStreetMap tiles and OpenStreetMap’s Nominatim geocoder, called
from your browser. Looked-up coordinates are cached on your own site so repeat
visits do not query it again.