AudibleTour is being built to bring your route and stories to passengers' phones, with multilingual commentary, location-triggered playback, and downloaded audio for areas without mobile service.
Pre-launch: the app is still being built and is not yet available to download. We are talking with a small number of operators about first pilots.
Prepare commentary in the languages your passengers need, from the route and stories you already have. Narration is being built to be produced from your script in the voices and languages you choose.
Manage scripts and recordings in a browser. Nothing is published until you approve it, and passengers get the new version the next time they open the tour.
Give guests a link or code with their booking so they can install the app and download the tour before they board, with less to sort out at the gangway.
Concept render of the back office. Final screens will differ.
This is the passenger experience we are building. Until the app ships, treat it as the intended flow rather than a demonstration.
A tour link or QR code goes into your booking emails, tickets, or boarding signs.
On first use they install the AudibleTour app and it opens on your tour. No account to create.
While still connected, they pick a language, download the tour, and allow location access.
Downloaded narration plays at each location as the boat reaches it. Play, pause, and skip stay under the passenger's thumb.
Phone screens are concept renders. Final screens will differ.
Your stories are told the way a good museum guide tells them: clear, factual, and warm. Built-in AI researches each one against trusted historical sources and flags what it cannot confirm. When a tour calls for something more imaginative, it helps with that too.
Narration is produced from your script in the voices and languages you choose, with restrained ambient sound under the voice: a harbor, a canal, a town square. No music under the narration, no radio drama.
The whole tour downloads before boarding. Out on the water, narration plays from the phone's own position with no mobile signal needed, and manual controls are always there if a passenger wants a story again.
A browser-based back office for your team. Scripts, pronunciations, translations, and the final audio are yours to review before anything reaches a passenger.
The same platform is planned for city bus tours, walking tours, museums and galleries, and parks and trails, with small indoor beacons where GPS cannot reach. Running something else? Tell us about your operation.
We are a husband-and-wife team. One of us is a chief architect at a global systems integrator. The other has spent a career running tours for one of the largest tour companies in the United States. Between us we have sat through a lot of tour narration around the world — and heard where it breaks. AudibleTour is what we built to fix it, on the narration system behind our first app, ICW Planner.
Visit rhumblineapps.comTell us about your route, passenger mix, and current commentary. We will discuss a focused pilot, agree the scope and evaluation criteria, and provide pricing for your operation.
A pilot can focus on one route, a defined selection of languages, and an agreed evaluation period. Availability, content work, and timing are confirmed individually.
Get one email when the app is available to download.
Not yet. AudibleTour is pre-launch and is not in the App Store or Google Play. We are talking with a small number of sightseeing operators about first pilots. If that could be you, request a pilot discussion above.
Yes. The AudibleTour app, for iPhone and Android, is required. Passengers install it once; every tour they add afterwards lands in the same app. Your link or QR code opens it on your tour.
Installing the app and downloading a tour. After that, the downloaded narration plays without mobile service, and the phone's GPS works without a data connection. Ticket purchases or other online services may still need a connection.
That is the design: no account, nothing to type. They open your link or scan your code, choose a language, and download the tour.
Yes, that is the intended starting point. Your existing script goes into the back office and narration is produced from it in the languages you choose. The back office is being built to take your existing recordings as well, whether as narration or to play between stories, provided you hold the rights to them.
iPhone and Android. Narration can be produced in many languages; the confirmed list of languages, phones, and system versions will be published before launch. Tell us the languages you need and we will confirm them for your pilot.
Share your route and stops, your current script or recordings, and the languages you want. Review and approve the narration. Then add the tour link or QR code to your booking emails and boarding signs. We agree who does what, and by when, as part of the pilot scope.
One route, a defined selection of languages, and an agreed evaluation period. Content work, timing, and price are quoted for your operation once we understand it; there is no public price list yet.
We agree one primary outcome before we start, such as bookings from a language group you currently underserve, fewer headsets to buy and maintain, faster commentary updates, or passengers getting going without help from your crew. Then we measure it together during the evaluation period.