Industry · Culture & heritage

Custom apps for cultural institutions: museums, theatres and heritage sites.

We build apps for the Dutch cultural sector: visitor apps, audio tours, ticketing flows, member portals and educational experiences that fit the gallery, the collection and the audience. Vendor-independent, with the code owned by the institution, a requirement that funders increasingly impose.

SectorMuseums & heritage
SectorTheatres & concert halls
SectorArchives
SectorFestivals & venues

The Dutch cultural sector in numbers.

~700
Registered museums in the Netherlands
~150
Professional theatres and concert halls
~32M
Museum visits per year pre-pandemic, recovering strongly
~68%
Of visitors use mobile content during or after their visit

Source: Museumvereniging Cijfers & Trends, CBS Cultuurstatistieken, Boekmanstichting research on digital audience reach.

Off-the-shelf software never covers the whole visitor journey.

Most cultural institutions use a combination of Adlib, Axiell or Memorix for collection management, ITix, Stager or Spektrix for ticketing, and separate small tools for donations, audio tour hire and education. The core functions work: tickets are sold, objects are registered, donations come in. But any coherent visitor experience stalls on the fact that no single tool is built for your specific programme, your collection or your audience. The ticketing system knows nothing about the education flow, the audio tour knows nothing about membership, and the collection system knows nothing about what the visitor sees on their phone.

A museum wants a visitor app that combines tours, deep links to object information, audio content and a route map in a single tap, linked to the ticketing system so a guest has the tour content on their phone straight after purchase. A theatre wants an app where subscribers find their season ticket, vouchers and programme recommendations, plus a low-threshold donation flow without endless redirects. An archive wants a researcher portal with IIIF viewers for manuscripts and a request system for depot orders. With an off-the-shelf package, that always ends in a long wish list that nobody can fulfil.

Experience also shows that culture is a sector where software decisions keep ticking away for years. A museum that once chose an audio tour device supplier pays buy-out fees every year for content it produced itself. A theatre that chose a ticketing system without an open API cannot analyse its own audience data. The only way to break that dependency without a massive migration is to build your own layer that supports your visitor experience, with integrations so data is entered only once, and with a roadmap driven by your curators, your audience team and your education staff.

A custom app solves this differently: the visitor flow is exactly what your programme demands, the collection integration is built properly once, and your education team gets a tool that serves a school class or a family day well. We work structurally with clients in culture and also build broader app development projects, combined with a custom ticketing system where that is worthwhile. For one specific museum, see our page on custom museum apps; this page looks at the cultural sector as a whole.

Software that fits every type of institution.

Each type of cultural organisation has its own visitor flow, its own integrations, and its own accessibility and open data requirements. Below, by layer, is what we typically build.

Museums & heritage

Museums have the broadest demand for apps. Besides the classic visitor app with audio tour, related needs are increasingly common: a family app for Saturday-morning families, an AR experience for an exhibition, a member portal for friends' associations, and an education tool for teachers visiting with their class. What connects all these apps is that they must integrate seamlessly with the collection management system, the ticketing system and your branding, and they must last a long time without an external supplier charging for every small change.

Our module set for museums integrates with Adlib, Axiell Collections or Memorix RMA for object data, reads in IIIF manifests for images and panoramas, and builds an experience on top that fits your curatorial direction. For audio tours, we work with BWAV files, subtitles per track and, where required, a sign language avatar. For AR layers, we build WebAR (no separate app download needed) or native ARKit/ARCore when the exhibition justifies it.

For education, we often build a separate teacher portal, with teaching materials, class codes for pupils and an integration with the booking system for groups. For audience researchers, we deliver anonymous visitor data in dashboards, with GDPR-compliant retention periods and no identifiability of individual visitors, so curators can discover which galleries work and which descriptions are actually read.

  • IIIF Image & Presentation APIThe standard for cultural heritage: a deep-zoom viewer for objects and manuscripts.
  • Adlib / Axiell / MemorixLive object data from the collection management system, in the app.
  • Audio tour engineBWAV streaming, subtitles, sign language track and offline cache for use in the gallery.
  • WCAG 2.2 AAAccessibility tested with JAWS, NVDA and the sign language flow.

The culture apps we typically build.

The cultural sector has a wide range of app needs. For one museum, a visitor app with an audio tour matters most: stories about objects, a route map across the galleries, a sign language track and subtitles you can call up in every room. For another museum, it is all about a family app in which parents and children follow a treasure hunt together, with a quiz, audio clips at children's height and a collection book at the end that can be read further at home. For a third museum, it is a member portal that links membership, donations and advance announcements to a simple profile, giving a sense of personal involvement with the institution without an external membership system dictating the house style and the communication.

For theatres and concert halls, we build apps that bring together a season ticket, performance information, programme booklets and seating plans, integrated with the ticketing system the institution already uses. We build in a low-threshold donation flow, with no separate microsite, just one field and an iDEAL button, and, where required, integrate it with the fundraisers' CRM. For subscribers, there is a digital season ticket that can be transferred when exchanged, a recommendation engine based on the performances they have seen, and a notification flow for programme changes.

For archive institutions, we build researcher portals with IIIF viewers for manuscripts, photographs and historical maps. We integrate with the collection management system for metadata, with the ordering system for depot requests and with the visitor booking system for reading room appointments. For genealogical research, we build search flows that make scans of deeds and population registers searchable, with an OCR layer on handwriting models where the material allows. Open data publication via Linked Open Data and alignment with the Netwerk Digitaal Erfgoed hubs are part of our standard approach, not as an afterthought but as an architectural starting point.

For education apps, we build tools that work for pupils in the gallery and in the classroom: a teacher dashboard with groups, a pupil app that guides them through an exhibition, and a follow-up module that links the visit to the SLO learning goals. We often work with partner platforms for cultural education and, where required, integrate with SOMtoday or Magister for group registration. For concert halls and youth theatres, we build similar school performance flows, with a booking system, programme information and teaching materials in one package.

For institutions that work with events, such as a museum night, a festival weekend or an opening, there is overlap with our event technology: badge systems, phased access per time slot, push notifications for programme changes and an interactive map for on-site orientation. We also build immersive content apps for institutions that work with VR or 360-degree video: a digital extension of an exhibition, a virtual tour for those who cannot attend, or an AR layer that continues the story outside the gallery.

Finally, for donor and friends associations we build apps that combine membership, recurring donations and a visit credit. Integration with CRM packages such as Salesforce NPSP, Stichting Donateursbelangen tools or an in-house system is a standard part of our approach. For institutions with an international audience, we build multilingual flows in at least Dutch, English and German — and for large museums also French, Spanish or Chinese, linked to the exhibition labels and the audio tour content.

Built to the strictest standards of the cultural sector.

Culture is a public function. Accessibility, privacy and open data integration are not extras at handover — we work within them from the first sprint.

European Accessibility Act & WCAG 2.2

Accessibility as a public obligation

Now that the European Accessibility Act is in force, public cultural apps must meet WCAG 2.2 AA. This affects visitor apps, audio tour flows, ticketing paths and all communication with the public. We build accessible by default — colour contrast, screen reader flows tested with JAWS and NVDA, full keyboard navigation, subtitles on video, audio transcripts for speech, sign language tracks where useful, and a separate mode for visitors with dyslexia or an intellectual disability. Handover includes an accessibility statement that is published on the institution's website, in line with the requirements of DigiToegankelijk and the Bewijs van Toegankelijkheid (Proof of Accessibility).

GDPR & minors

Privacy with extra care for young visitors

Education apps for pupils and family apps for children fall under a stricter GDPR regime. We collect only data that is educationally or operationally necessary, define retention periods per data object, arrange school consent via the teacher or parental consent for young users, and deliver a DPIA as standard at handover. Data processing agreements and sub-processor registers are part of the handover, not of a later quarterly release. Donation and membership flows also come with strict rules on marketing consent and purpose limitation, which we adhere to as standard.

IIIF, LIDO, Linked Open Data

Standards for cultural heritage

For images of objects, we use the IIIF Image API and the IIIF Presentation API — the international standard for heritage imagery, supported by virtually every major museum worldwide. For object metadata, we work with LIDO or a derived schema, so that collection export to Europeana, NDE or Wikidata is possible from day one. For Linked Open Data, we publish in line with the NDE guidelines, with persistent URIs per object so the data can still be found ten years from now — a requirement that the Mondriaan Fund and the OCW subsidy register increasingly include in grant decisions.

Ownership of code & data

No vendor lock-in with subsidy funding

For cultural institutions that work with subsidies — the Mondriaan Fund, the Performing Arts Fund NL, OCW, municipal culture funds — code ownership is not a luxury but increasingly a hard subsidy requirement. We always deliver source code, infrastructure configuration and deployment scripts into the institution's ownership. Hosting can be with us, with your partner, with SURF, or with a private cloud provider — that is your choice. We document the architecture so that a future party can take over further development without needing any further involvement from us.

EU AI Act & culture

Responsible AI in collection access

AI applications in the cultural sector — automatic object descriptions, artwork recognition, sign language avatars, AI tour guides — almost always fall under the AI Act categories that require governance, transparency and human-in-the-loop oversight. We document the governance for every AI feature: training data, bias tests, fallback behaviour when the model is uncertain, and human validation for content on historical and sensitive subjects (colonialism, the Second World War, restitution issues). We advise against fully automated text generation for museum gallery labels — the reputational risk for the institution is too great. AI is an aid, not a replacement for the curator.

Dutch Fixed Book Price Act & copyright

Rights and licences in code

Much cultural content carries layered copyrights: the artwork, the photograph of the artwork, the curator's text, the audio tour voice, the music for the exhibition. We build rights administration in as a configurable layer, with expiry dates per asset and automatic removal or blacking out when a licence expires. For open data publication we know the Rights Statements vocabulary and automatically apply the correct licence to every object that is published externally. For international collections we also work with European restitution guidelines, so that objects with a sensitive provenance are correctly flagged and presented.

Seamlessly connected to the cultural ecosystem.

We integrate with the software your institution already uses. No migration of your entire stack — our app complements and rarely replaces.

Adlib
Collection management · museum
Axiell Collections
Collection management · cloud
Memorix RMA
Archive & museum management
ITix
Ticketing · Dutch venues
Stager / Spektrix
Ticketing · theatres & venues
NDE hubs
Dutch Digital Heritage Network
Europeana
European heritage platform
Salesforce NPSP
CRM for donors

Standard integrations, no project-specific connections.

We have standardised the integrations listed above across multiple cultural projects. For a new project we set up the integration using the same abstraction layer, which means fewer bugs, a faster turnaround, and your own application management team can run it once we step out. For cultural institutions that last point is more than a nice-to-have — it is often a prerequisite for grant applications that require continuity and code ownership.

For institution-specific software, such as in-house middleware, a catalogue built by the IT department decades ago, or an audio distribution system from a vanished supplier, we build an integration case by case. This takes extra time in the planning phase but prevents integration debt later. For institutions that work with an external ticketing partner, we also look at a custom ticketing system when that shifts the annual fee structure and vendor dependency towards ownership and self-determination.

Internationally, we work with partners for IIIF implementations, Wikidata publications and the Europeana aggregation platform. For museum shop integrations we integrate with Shopify, Lightspeed or your existing museum POS. For donation flows we integrate with Mollie, Stripe and — for recurring direct debits — directly with SEPA via your own bank. For education tools we integrate, where it makes sense, with Magister, SOMtoday or SLO learning pathways, so that schools can see visit data and lesson results in their own systems.

From programme audit to go-live in clear steps.

A project for a cultural institution has its own rhythm. Five phases that will be familiar to every client.

01 · Audit

Visitor & collection mapping

A day with a curator, a visitor engagement officer and an IT specialist as guides. Result: the current visitor journey mapped, bottlenecks flagged, and the content principles documented.

02 · Design

Scope per target group

Which flow for each visitor type (first-time visitor, member, school class, researcher), which integrations take priority and which modules belong in a later release.

03 · Build

Short sprints

One working flow delivered per sprint. The curator and visitor engagement team test along with us — the first working flow is already running after a few sprints.

04 · Cutover

Pilot & rollout

First in one gallery or for one exhibition, then across the whole institution. With every rollout: training for gallery attendants, materials for the front desk, and hand-over to your application management team.

05 · Maintenance

Ongoing

We make adjustments with every OS update, GDPR change or new exhibition. Fixed monthly price, first-line support within the same working day.

Working in a sector that is held publicly accountable.

Museumvereniging figures & trends

"Visitors expect digital support around their visit: beforehand through ticketing and programme information, in the gallery through an audio tour or context, and afterwards through deeper content and membership. Museums that serve this whole chain well see higher return rates."

Netwerk Digitaal Erfgoed annual report

"The greatest added value of digital heritage work lies not in the presentation layer alone, but in the standards-based integration between collection systems, public-facing applications and open-data hubs."

Mondriaan Fonds explanatory note on digitisation

"In digitisation projects, we consider whether the applicant institution retains control of its code and data, and whether the solution fits into the wider heritage infrastructure in the Netherlands."

Answers for the cultural institution that is going digital.

The questions we hear most often from directors, heads of public engagement and heads of collections.

What types of cultural app do you build?
We build visitor apps with audio tours, family apps and treasure hunts for families, member portals and donor apps for friends' associations, researcher portals for archives, AR and immersive content experiences for exhibitions, education tools for school visits, ticketing integrations and season-pass apps for theatres, and open-data publishing platforms for Europeana or Wikidata. For one clearly defined service, see also our page on building a museum app and the dedicated page on visitor apps with audio tours. For the broader context of app development, you can find additional information on that service page.
What does code ownership mean in subsidised projects?
For cultural institutions working with funding from the Mondriaan Fonds, Fonds Podiumkunsten or the Ministry of Education, Culture and Science (OCW), code ownership is not a formality but often a strict funding condition. We always hand over source code, infrastructure configuration and deployment scripts as your property. Hosting can be with us, with SURF or in a private cloud, and that choice stays with you. The documentation is written so that a successor can pick up the work without us needing to be involved. For us this is a principle: we don't want to be the permanent development partner, we want to be the right partner for the project in front of us.
How do you handle WCAG 2.2 and the European Accessibility Act?
In the cultural sector, accessibility is not a box to tick at the end but architecture from the first sprint. We build in colour contrast, screen-reader flows and keyboard navigation as standard. For audio tours, we provide subtitles, audio transcripts and, where the content justifies it, sign language tracks using an NGT (Sign Language of the Netherlands) interpreter or an interpreter avatar. Delivery includes an accessibility statement that is published on the institution's website and can be verified by Stichting Drempelvrij or a comparable audit partner. For education apps used in primary schools, we provide additional dyslexia-friendly and plain Dutch modes.
Do you work with Adlib, Axiell, Memorix or another collection system?
Yes, all three and more. We have built integrations with Adlib, Axiell Collections, Memorix RMA and a number of smaller or in-house systems. We work through the official APIs where they exist and otherwise build a readable layer on top of the database. The principle is that object data comes from a single source, the collection management system, and is never retyped or maintained in a separate table. For IIIF images, we connect to the IIIF server your institution already uses or set up a new one (Cantaloupe, IIPImage, or a hosted option through a partner).
Can you integrate with our ticketing supplier?
We have standard integrations for ITix, Stager and Spektrix. For other ticketing systems, we look at the available APIs or webhooks; this usually works, and if not, we build a readable middleware layer. We're also seeing more and more institutions consider building their own custom ticketing system to escape vendor lock-in and annual fee structures. That is a different track with different trade-offs, and we'll give you honest advice on when it does or doesn't make sense — not every institution benefits from building its own.
Can you handle open data publication to Europeana or Wikidata?
Yes. For institutions that want to open up their collection data through Netwerk Digitaal Erfgoed hubs, Europeana or Wikidata, we build the export pipelines, with persistent URIs per object, the correct Rights Statements per asset and continuous synchronisation so the open data version stays in line with the collection management system. We work with LIDO-XML, EDM for Europeana, or direct Wikidata edits via QuickStatements or the official API. For IIIF images, we generate manifests that international researchers can also use in their own viewer or a research tool such as Mirador or Universal Viewer.
Can you build an event app for a temporary exhibition or festival?
Yes. For museum nights, festival weekends, programme series or a one-off major exhibition, we build apps that run for a defined period — with timeslot access, an interactive floor plan, programme recommendations and push notifications for changes. For the broader context, see also our page on event technology. We can keep a temporary app separate from your permanent app offering, or combine the two in a single app with a seasonal mode — depending on what your audience is used to.
How much does it cost to develop a cultural app?
A visitor app for a single exhibition is a smaller project than an institution-wide platform with collection integration, ticketing integration, a member portal and an education layer. We work with a fixed sprint budget and, after the planning phase, give you a concrete price for the complete build, including integrations and compliance work. What we often do: start with one clearly defined flow — for example, the audio tour for the permanent collection — and only broaden the scope once it works and visitors are actively using it.

Talk to us about your cultural app.

A half-hour introduction with a director, head of public engagement or curator. We listen, ask questions and give you an initial direction. No obligation.

Edit content