Originally, we never wanted guests to install an app just to join a single guided tour.
From the very beginning, the core idea behind elysium® was simple: scan a QR code, listen, and you're ready to go. No registration, no user account, and no login credentials. That's why listeners normally access the audio stream directly through the browser on their own smartphone.
For many guided tours, training sessions, and events, this remains the simplest solution.
However, an extensive real-world deployment during daily shore excursions revealed a second use case: professional tour operators who provide guests with pre-configured listening devices and use them every day under changing conditions.
For these heavy-use scenarios, we didn't need a new product concept or a more complicated user experience. What we needed was greater control over the connection between devices.
That's how elysium® – Listener was born.
elysium® – Listener at a Glance
elysium® – Listener is an Android app designed for guests and listeners. It receives audio streams from two elysium® applications:
- the elysium® Audio Tour Guide App for live audio transmission during guided tours, training sessions, and events
- the elysium® Live Translation App for live audio with real-time translation into more than 29 languages
The Listener app is not intended to start a tour, speak to participants, or manage groups. Those tasks continue to be handled by the appropriate Guide app.
Listeners simply open elysium® – Listener and scan the guide's QR code. If the QR code originates from the Audio Tour Guide App, they receive the original audio. If it comes from the Live Translation App, they can additionally select their preferred language.
No registration is required. There are no user accounts or login credentials.
Open the app, scan the QR code, and start listening.
The interface intentionally looks almost identical to the browser-based version. We wanted the experience to remain just as simple for guides and guests. The real improvements happen behind the scenes.
Why the Browser Remains the Right Choice
The Listener app is not a departure from our original approach.
Whenever participants use their own smartphones, the browser remains the most practical solution. Guests scan the QR code with their phone's camera, open the link, and can start listening immediately.
No download. No setup. No additional steps before the tour begins.
This simplicity is especially important for one-time events and public tours. Someone joining a tour for just an hour shouldn't have to search for an app, install it, and delete it again afterward.
That's why browser access remains an integral part of the elysium® platform.
The Listener app is designed for a different operating model: organizations that provide dedicated Android devices as receivers. These devices aren't used just once—they're used continuously, often for multiple tours every day.
In these professional B2B environments, guests don't install an app themselves. Instead, the app is permanently installed on the prepared devices. Before each tour, the guide configures the receivers and hands them out together with an earpiece.
For guests, the experience remains just as straightforward. They simply receive a ready-to-use device and start listening immediately.
What Six Weeks of Shore Excursions Taught Us
The direct trigger for developing the app was a large pilot project with an international tour operator.
Our solution was used for at least six weeks during shore excursions across several European countries. Every day involved multiple tours with different guides, routes, and mobile network conditions.
During coach tours, the issue that later became our primary focus rarely appeared. Receivers remained in relatively stable environments for extended periods.
Walking tours, however, told a different story.
Groups moved through narrow streets, between tall buildings, across open squares, and through areas with constantly changing mobile coverage. Under these conditions, brief connection interruptions were sometimes unavoidable.
The real question was what happened after those interruptions.
Our browser solution already included an automatic reconnect mechanism. Whenever connectivity returned, the audio stream was supposed to reconnect automatically in the background.
On many devices, this worked perfectly. On others, however, the browser page had to be refreshed manually or the reconnect process had to be triggered by the guide.
On a single smartphone, this is just one extra tap. But when managing dozens of prepared devices across multiple tours every day, it becomes a significant operational burden.
Later, the same challenge appeared during deployments with another cruise industry customer operating tours in Asia. It became clear that the issue wasn't tied to a specific country, route, or mobile network provider.
The audio streaming itself wasn't the problem. The challenge was ensuring reliable automatic reconnection across a wide variety of browsers and Android devices.
Why We Built a Dedicated Receiver App
A mobile browser has to perform many different tasks simultaneously.
It displays websites, manages browser tabs, plays media, and follows each device's security, privacy, and battery-saving settings. At the same time, the operating system decides which background processes are allowed to continue running.
As a result, the very same browser can behave differently on two Android devices.
One device reconnects immediately after a network interruption. Another blocks the reconnect because of battery optimization. A third limits playback when the screen is locked or when switching between mobile networks.
As the platform provider, we have no complete control over these individual settings. We can't inspect or centrally configure every device, and every new Android version introduces additional variables.
This isn't a limitation of the audio stream itself—it's simply the reality of running a specialized application inside a general-purpose browser.
A browser can do almost everything. The Listener app only needs to do one thing—and do it reliably.
With browser access, the Guide app communicates with a mobile browser. With elysium® – Listener, two dedicated apps communicate directly with one another—both specifically designed to send and receive our audio streams.
The Listener app is optimized for exactly this purpose:
- It receives the audio stream.
- It handles network changes.
- It automatically restores interrupted connections.
- It continues playback in the background.
- It is far less affected by browser settings and battery optimization features.
The idea of building a dedicated listener app had actually existed for almost two years. We deliberately chose not to develop it simply because it was technically possible.
What we lacked was a real-world use case.
The six-week pilot changed that. It clearly showed us who needed the app, under which conditions it would be used, and exactly which problem it had to solve.
Within roughly two weeks, we developed the first production-ready Android version and immediately tested it during live customer operations.
Not in a laboratory. Not on a single test route. But in the exact environment where the challenge had originally appeared.
Since introducing elysium® – Listener, these reconnect issues have no longer occurred in this form.
The app is now officially available on Google Play and complements our two existing Android applications.
