Wanderply

About

We built this for one trip. It became the trip planner we'd been missing.

Wanderply started as a four-day Vegas itinerary for a family of six — two parents, two kids, two grandparents, one minivan. Spreadsheets weren't cutting it. Google Maps lists didn't have the why. And nothing was speaking to the kids on the drive.

The idea

Build a planner that survives the drive. Day-by-day plans with photos, maps, and a tour-guide voice that explains what you're looking at. Save the maps offline. Hand it to the back seat. Hit the road.

What's in it

  • Final plan view — every day as its own card, color-coded by theme, with photos, addresses, deep-linked Maps & Uber, and a famous-for blurb on every stop.
  • Podcast mode — two voices, hand-written tour-guide scripts for the big stops. Hoover Dam, the Sphere, the Skywalk — all covered like a real audio guide.
  • Drive co-pilot — trivia questions matched to each traveler's interests, with a road-trip playlist as the reward.
  • Checklists — before-trip, per-day, per-activity. Toggle live with Turbo, scoped where they matter.
  • Document vault — drop hotel PDFs, e-tickets, and .ics calendar files on a trip or an activity. They're there at the front desk.
  • Offline-first PWA — pre-cached map tiles, network-first pages with cached fallback, and a downloadable MP3/MP4 version of the day's narration.

The stack

Rails 8 with Hotwire, PostgreSQL with UUID primary keys, Devise + Pundit, Tailwind, and a service worker doing the offline heavy lifting. Hotwire Native shells for iOS and Android wrap the same web URLs. The web is the source of truth.

Why we kept it free

Because trips are already expensive, and the planning shouldn't be. No ads, no upsells, no premium tier that gates the good stuff. If you want to support it, share it with another family.