RV LIFE Trip Wizard has a deeper campground database — they've been at it for ten years. Roadtrippers has slick general routing. Road Voyage's bet is on the Travel Day organizational model and real-time cascade. Different problems; partly overlapping. We wrap RV-quality data around a planning workflow that actually fits how RVers travel.
Practical difference: edit Day 6's hours; in Roadtrippers you redo the spreadsheet. In Road Voyage, Day 7's start coord shifts, mileage recomputes, and the dates ripple forward — automatically.
It's a working demo — fully playable, complete with the 14-day Tampa → Seattle trip, ~400 hand-curated POIs, the cascade logic, the print-to-PDF, and offline persistence. You can click around, edit Travel Days, watch the cascade, and print the PDF reference.
What it isn't yet: a planner that handles arbitrary US trips with national POI coverage. That's the next phase — and we're building toward it based on the feedback from this demo.
The demo prototype works offline once it loads — it caches the active trip in your browser's local storage. You can read the plan, view all stops, see the day detail, and even add notes — all offline.
The production build (Phase 2) will add a service worker that caches map tiles around the route, native PWA install for adding to home screen, and offline edit-queue that syncs when you reconnect.
Today: Road Voyage works on mobile browsers and (in the next phase) installs as a PWA — adds to home screen with a polished icon and full offline support.
Native iOS + Android apps are on the roadmap for the post-MVP phase. Push notifications for weather alerts and day-shift cascades, photo journal with camera integration, and GPS background tracking for "On the Road" mode are all planned.
All of them. Class A, Class B (camper van), Class C, fifth-wheel, travel trailer, popup. The setup wizard captures your length, height, weight class, and fuel type — and the routing + camp filtering responds accordingly. A 40-foot Class A gets different POIs than a 19-foot van.
In the demo, all 400 POIs are hand-curated for the Tampa → Seattle route. Phone numbers are 555-prefix mock numbers — accurate enough to validate the UX, not real reservations.
Production (Phase 2): real data from Recreation.gov (federal lands, free API), OpenStreetMap (fuel stations, propane, dump stations, scenic stops — free), iOverlander (boondocking — free community export), and partnerships with private campground brands as we hit traction thresholds.
Family sharing is in the roadmap. Phase 2 ships read-only public share links (a permanent URL anyone can view). Phase 3 adds full multi-user edit access — up to 5 family members on one trip, all with edit rights, plus public read-only links for friends not on the plan.
For now, in the demo: you can export a trip as JSON and import it on another device manually.
The demo is and will remain free. We don't have a confirmed pricing model for the production product yet — that's something we'll figure out based on what the community tells us.
What we know: there will likely be a free tier with core functionality, and a paid tier for power features (offline mode, family sharing, advanced routing). We're not interested in paywalling the basics. The demo + community-driven product development comes first; pricing comes later.
Honest answer: when the community tells us it's ready. The demo is live now (Spring 2026). Phase 2 — national POI coverage and Mapbox routing — is roughly 6 weeks of engineering work, but we're triggering it based on signals: 500+ newsletter subscribers, 50+ pieces of substantive feedback, 12+ blog posts published.
Realistic timing: 4-9 months from demo launch to production launch. Faster if your feedback comes hard and clear; slower if we're publishing into the void.
Three ways, all useful:
The fastest way to get a feel for the product. Both take less than 10 minutes.