Multilingual audio tour
NL, EN, DE, FR, ES, JP, ZH or more. Audio streamed or preloaded for offline use. Player with quick rewind and chapter navigation.
An app that guides your visitors through your collection or site: multilingual, accessible and in your own house style. We build custom visitor apps that go further than the standard packages from Smartify or Bloomberg Connects, without making your curator dependent on a vendor. From audio tour to AR overlay, from ticketing integration to crowd management: modules you choose based on your collection and target audience.
Source: Museumvereniging statistics overview, CBS Statline, Museumkaart annual report.
Many museums and attractions start with a commodity package: Smartify, Bloomberg Connects, Acoustiguide or a legacy Antenna app. As a first digital step that works, but as soon as your curator wants to manage their own content, add AR overlays, integrate ticketing or run a children's mode alongside the adult route, you run into the vendor's limits.
Another problem: the visitor experience feels the same to your audience as at thirty other institutions. Your own house style, story and brand identity don't come across. For the Rijksmuseum or the Van Gogh Museum, a dedicated app therefore makes sense — for the mid-sized segment it long seemed out of reach. With today's stack (React Native, headless CMS, manageable beacons), custom is within closer reach than five years ago.
The third problem is depth of integration. A commodity tour does not know your visitor. They are treated as a first-time visitor every time, with no memory of earlier visits, no recognition of membership and no connection to their ticket or donation history. For a museum that depends on friends, members and repeat visits, that is a missed opportunity: your own app does know your visitor, and can use that respectfully for curatorial communication or fundraising.
Our view: a custom visitor app with audio tour functionality becomes worthwhile as soon as you have more than one of these needs: multilingual support for diverse audiences, indoor wayfinding, AR, children's versions, accessibility modes, ticketing and membership integrations, or a white-label version for multiple locations. At that point, integration, your own branding and knowledge of your visitors outweigh the price of an off-the-shelf package. See also our page on app development for the broader approach.
Every type of institution needs different features, different routes and different visitors. Here is what we typically build for the four largest segments.
The classic starting point: an audio tour along a permanent display or a temporary exhibition. Curators manage their own content, and visitors choose between the full tour, a children's version or a themed selection. For indoor spaces we work with BLE beacons or QR codes, as GPS is rarely reliable inside a museum building.
For heritage institutions, such as castles, historic sites and religious buildings with tourist footfall, we build routes with AR overlays that show how a space used to look. Multilingual from the first release, with attention to accessibility in line with WCAG 2.2 AA.
For zoos and botanical gardens, we work with outdoor routes using GPS and geofencing, linked to feeding times, demonstrations and seasonal content. For theme parks and attractions, the focus is on waiting times, route optimisation and game elements for young visitors. For cities and tourist offices, we often deliver a white-label platform that lets you manage multiple points of interest across an area from one central place.
A custom app is a collection of modules that we put together for each project. Not every institution needs everything, so we decide together what fits your collection, audience and operational reality.
NL, EN, DE, FR, ES, JP, ZH or more. Audio streamed or preloaded for offline use. Player with quick rewind and chapter navigation.
Indoors with BLE beacons (iBeacon, Eddystone) or QR codes. Outdoors with GPS and geofencing. Routes adapt to crowds or closed areas.
ARKit for iOS and ARCore for Android. Reconstruction of historic spaces, anatomical layers over objects, or treasure hunts for children.
Visitors scan their ticket QR code and automatically get the right tour. Integration with Recras, Pretix, CCV, your own ticketing system or a museum API.
When a visitor enters a space, when a timed show starts, or near special objects. Fully opt-in and GDPR-compliant.
Audio, images and route data are downloaded at start-up. Works in cellars, castles and buildings without coverage.
Sign language video, subtitles, an audio-described tour for blind visitors, a dyslexia mode, and a calm mode for visitors with autism or sensory sensitivity.
Its own audio track with cheerful voices, treasure hunts, badges and short explanations. Parents and children follow the same route with different content.
Visitors order a coffee or a catalogue from the app, avoiding queues at the counter. Payment via iDEAL, Apple Pay or Google Pay.
Real-time insight into which spaces are busy, with alternative routes for your visitors. A dashboard of crowd patterns for your operations team.
In-app NPS question at the end of the tour, with a direct link to your Google Maps page for positive reviews.
A headless CMS (Directus, Strapi or Contentful) so your curator manages routes, objects, audio tracks and languages themselves, without raising a ticket with us or a vendor.
Popular routes, average time per object, drop-off points. Insight for the educator, not just for marketing.
One-off donation or new membership directly in the app via Mollie, Adyen or iDEAL. Integration with Museumkaart or your own membership administration.
A chatbot per object: 'ask me something about this painting'. It works on your own content, not on a generic model. Transparent and compliant with the EU AI Act.
For cultural institutions, accessibility and privacy are no longer nice-to-haves. From sprint one, we work within the framework of WCAG, the EAA, GDPR and the EU AI Act.
Mandatory since 28 June 2025 for public and commercial digital services: an audio tour app falls within scope. From the first sprint, we build EAA requirements into the design checks.
Subtitles for every audio track, an audio-described tour for blind and partially sighted visitors, sign language video for key objects, a dyslexia mode, and navigation that works with VoiceOver and TalkBack.
Indoor positioning data is privacy-sensitive. We deliver a DPIA, anonymise visitor movements where possible, and document retention and data subject rights, so your data protection officer can take it from there.
For AI features, such as a chatbot per object, automatic translation or audio generation, we map out the risk classification. For most museum applications this falls under limited risk, with transparency requirements that we fulfil properly.
Secure in-app payment via Mollie or Adyen for donations, memberships, café orders or merchandise. iDEAL, Apple Pay, Google Pay and credit card: your visitor chooses.
We integrate with the systems your till, membership, donations and CRM already run on. The app complements what already works rather than replacing it.
A frequent complaint about commodity packages: every content change goes through a ticket with the vendor. With custom development, we deliver a headless CMS (Directus, Strapi or Contentful) in which your curator uploads new routes, objects and audio tracks themselves. A temporary exhibition goes live within a few sprints of the first delivery.
For institutions with their own collection database (Adlib, TMS, Axiell), we build a synchronisation layer so that object metadata has a single source. For AI-augmented tours, such as a chatbot that answers questions per object, we work with custom LLM integrations on top of your own content.
For the mobile app layer, we use React Native as standard. One codebase builds the iOS and Android versions simultaneously, with native performance for most museum features. Only when an AR feature, indoor positioning or an audio engine has to run without compromise do we switch to native Swift or Kotlin for that component, while the rest stays cross-platform.
The content layer is always headless. Your curator works in Directus, Strapi or Contentful, depending on your IT preference. Audio tracks are served via a CDN, so every visitor gets smooth playback even at peak times. Images and AR models are optimised to keep the app size manageable — users don't like downloading a gigabyte.
For BLE beacons we work with vendor-agnostic hardware (Kontakt.io, Estimote or generic iBeacon modules) — no vendor lock-in. We handle placement, calibration and software management. For institutions that prefer QR codes, we deliver a simple CMS that gives every room its own sticker.
For AI features in the tour — a chatbot per object, for example — we work with a dedicated content layer: the language model draws its answers from texts approved by your curator, not from the open internet. This gives you transparency, complies with the EU AI Act for limited-risk systems, and stops the model from making things up about your collection.
Building a visitor app requires its own rhythm — curator, educator, IT and visitor services all sit at the table. Five phases that run the same way for every institution.
A day on site with the curator, educator and visitor services. Which routes, which audiences, which accessibility requirements.
One route per audience. Decision points on BLE versus QR, AR yes or no, languages, membership integration.
One working flow every sprint. Educators help test, and visitor feedback is included early. First flow live within a few weeks.
A small group tests on site. Drop-off points, audio connectivity and accessibility checks in practice.
Content updates for every temporary exhibition, maintenance work for every OS update. Fixed monthly price for support.
The questions we hear most from directors, curators and education teams.
A half-hour introduction with your curator, director or education team. We listen, ask questions and give an initial direction. No obligation. Also read about our approach to mobile apps in the field.
Appfront uses cookies and similar technologies to make the website work properly, for analytics and for marketing. You choose what you allow. Read more in our privacy policy.