Industry · Cultural institutions

Custom visitor app and audio tour. For museums, heritage sites and attractions.

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.

Target audienceMuseums and heritage
Target audienceZoos and botanical gardens
Target audienceTheme parks and attractions
Target audienceCities and tourist boards

The Dutch cultural sector in numbers.

~700
Registered museums in the Netherlands
~33M
Museum visits per year (NL)
~1,5M
Active Museumkaart holders
2025
European Accessibility Act in force

Source: Museumvereniging statistics overview, CBS Statline, Museumkaart annual report.

A standard tour rarely fits your collection.

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.

One app, many types of institution.

Every type of institution needs different features, different routes and different visitors. Here is what we typically build for the four largest segments.

Museums and heritage

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.

  • Audio tour in 5–7 languagesNL, EN, DE, FR, ES, JP, ZH: your audience chooses.
  • BLE beacons for indoor positioningThe tour responds to location, even without a mobile network.
  • AR layer over objectsARKit and ARCore for historical reconstruction.
  • Your own CMS for curatorsManage routes and content without involving a vendor.

The building blocks of a modern visitor app.

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.

Audio

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.

Navigation

Wayfinding

Indoors with BLE beacons (iBeacon, Eddystone) or QR codes. Outdoors with GPS and geofencing. Routes adapt to crowds or closed areas.

AR

Augmented reality

ARKit for iOS and ARCore for Android. Reconstruction of historic spaces, anatomical layers over objects, or treasure hunts for children.

Ticket

Ticketing integration

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.

Push

Location-based notifications

When a visitor enters a space, when a timed show starts, or near special objects. Fully opt-in and GDPR-compliant.

Offline

Offline mode

Audio, images and route data are downloaded at start-up. Works in cellars, castles and buildings without coverage.

Access

Accessibility modes

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.

Kids

Family and children's version

Its own audio track with cheerful voices, treasure hunts, badges and short explanations. Parents and children follow the same route with different content.

Shop

In-app merchandise and café

Visitors order a coffee or a catalogue from the app, avoiding queues at the counter. Payment via iDEAL, Apple Pay or Google Pay.

Crowd

Crowd management

Real-time insight into which spaces are busy, with alternative routes for your visitors. A dashboard of crowd patterns for your operations team.

Feedback

Visitor feedback and NPS

In-app NPS question at the end of the tour, with a direct link to your Google Maps page for positive reviews.

CMS

Curator CMS

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.

Analytics

Tour analytics

Popular routes, average time per object, drop-off points. Insight for the educator, not just for marketing.

Donation

Donations and membership

One-off donation or new membership directly in the app via Mollie, Adyen or iDEAL. Integration with Museumkaart or your own membership administration.

AI

AI-augmented tour

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.

Built on the standards for publicly accessible institutions.

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.

European Accessibility Act

Accessible from 2025

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.

WCAG 2.2 level AA

Universal access

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.

GDPR

Privacy with geofencing and analytics

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.

EU AI Act

Responsible AI in tours

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.

PSD2 and iDEAL

Donations and ticket payments

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.

Seamlessly connected to your institution's ecosystem.

We integrate with the systems your till, membership, donations and CRM already run on. The app complements what already works rather than replacing it.

Museumkaart
Membership validation
Recras
Ticketing and reservation system
CCV / Pretix
Ticketing and point of sale
Mollie / Adyen
Donations and payments
Firebase
Push and analytics
Salesforce / HubSpot
CRM and mailings
Directus / Strapi
Headless CMS
Own collection database
Adlib, TMS, Axiell

The curator manages the content, not the vendor.

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.

How we build custom visitor apps.

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.

From first workshop to go-live.

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.

01 · Workshop

Mapping the visitor journey

A day on site with the curator, educator and visitor services. Which routes, which audiences, which accessibility requirements.

02 · Design

Content and flow

One route per audience. Decision points on BLE versus QR, AR yes or no, languages, membership integration.

03 · Build

Two-week sprints

One working flow every sprint. Educators help test, and visitor feedback is included early. First flow live within a few weeks.

04 · Pilot

With real visitors

A small group tests on site. Drop-off points, audio connectivity and accessibility checks in practice.

05 · Maintenance

Ongoing development

Content updates for every temporary exhibition, maintenance work for every OS update. Fixed monthly price for support.

Answers for the curator who is going digital.

The questions we hear most from directors, curators and education teams.

What is the difference compared with Smartify or Bloomberg Connects?
Smartify and Bloomberg Connects are shared platforms — your institution sits alongside many others under the same brand name, with the same interface and limited integration options. A custom visitor app carries your own brand, integrates deeply with your ticketing system, membership and CRM, and gives your curator full control over content. They are complementary choices: for institutions with a simple tour and no branding ambitions, an off-the-shelf package is perfectly fine. For institutions that want to shape the visitor experience or combine multiple features, custom is the logical step. Many larger museums — the Rijksmuseum, Stedelijk, Van Gogh Museum, Mauritshuis — therefore opted for their own app, while some smaller institutions use Bloomberg Connects for low-threshold distribution. Both strategies have their place.
BLE beacons or GPS for indoor wayfinding?
GPS almost never works reliably inside a building — walls, concrete and metal block the signal. For indoor positioning we work with BLE beacons (iBeacon or Eddystone) or QR codes per object. BLE gives a smooth, automatic experience (the tour moves along as the visitor walks around), while QR is cheaper and simpler to manage. For outdoor routes — a city walk, nature park or historic district — we do use GPS and geofencing. For hybrid locations (a castle with a park) we combine both techniques in one app, so the transition feels seamless for the visitor.
Is offline mode really necessary?
For museums, cellars, castles and old heritage buildings, offline mode is not a luxury but a necessity: Wi-Fi and 4G often work poorly there. We build the app so that audio tracks, images and route data are preloaded on installation or on arrival. For outdoor attractions with good coverage, a streaming approach may be enough, with audio caching on demand.
What about WCAG and the European Accessibility Act?
Since 28 June 2025, the European Accessibility Act has required digital services from public and commercial providers to be accessible, and a visitor app falls under that. We build to WCAG 2.2 level AA and deliver subtitles, sign language video for key objects, audio-described tours for blind and partially sighted visitors, a dyslexia mode and VoiceOver/TalkBack compatibility as standard. For institutions that have already passed the legal deadline, we help with a phased upgrade.
How many languages can we support?
Technically there is no limit. We see Dutch museums typically start with NL, EN and DE, and expand with FR, ES, JP and ZH for international collections. The biggest cost item is not the technology but the production of audio content: script, voice-over and mixing per language. We put you in touch with audio production studios that work in this market, or work with your existing supplier. For institutions that want to add languages later, we deliver the CMS so that a new language version can be entered entirely by your own team, without a new app release.
Will our curator manage the content themselves?
Yes. We deliver a headless CMS (Directus, Strapi or Contentful) with an interface designed for non-technical curators. New routes, objects, audio tracks, AR overlays and translations are managed by your own team. The app retrieves them via an API. We remain available for structural extensions, but you run the day-to-day content yourself.
When is AR worth it?
AR works brilliantly for reconstruction (what did this space look like in 1650?), for invisible layers (anatomy over an object, an X-ray image over a painting) and for young visitors. For a straightforward audio tour of contemporary art, AR usually adds little. We recommend AR only when it adds something to the story, not as a tech gimmick. For heritage institutions where little of the original building or object remains, AR can make the difference between a static tour and an experience visitors remember for years.
How do you handle our existing collection database?
Many museums use Adlib, TMS, Axiell or their own collection management system as the source of truth for object data. We connect to it with a synchronisation layer: your curator keeps working in the familiar system, and changes propagate to the app. For new content that lives only in the visitor app (audio tracks, AR overlays, children's text), we use the app's own headless CMS, so your collection database doesn't get bloated with visitor-specific metadata.
What determines the cost of a visitor app?
The biggest factors are the number of languages, whether AR features are included, whether we physically place and calibrate BLE beacons, how many routes and target groups there are, and which integrations (ticketing, membership, CRM, payment) you want. A venue-wide app for a single museum with one route in two languages is a compact project; a white-label platform for a museum cooperative with multiple locations and advanced features is a larger one. After the first workshop, we give you a concrete scope and price for the complete build.

Talk to us about your visitor app and audio tour.

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.

Edit content