Sector · 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 suited to the venue, the collection and the audience. Vendor-independent, with the code owned by the institution, a requirement funders increasingly ask for.

SectorMuseums & heritage
SectorTheatres & concert halls
SectorArchives
SectorFestivals & performance 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, now steadily recovering
~68%
Of visitors use mobile content during or after their visit

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

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

Most cultural institutions combine Adlib, Axiell or Memorix for collection management, ITix, Stager or Spektrix for ticketing, and separate tools for donations, audio tour hire and education. The core functions work: tickets get sold, objects get registered, donations come in. But every joined-up visitor experience stalls because no single tool was built for your specific programme, your collection or your audience. The ticketing system knows nothing about the educational 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 guided tours, deep links to object information, audio content and a route map in a single tap-through, integrated with the ticketing system so that a guest has the tour content on their phone straight after buying a ticket. A theatre wants an app where subscription holders can find their season pass, 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 requests. On a standard package, that always ends in a long wish list that nobody can deliver.

Experience also shows that in culture, a software decision can echo for years. A museum that once chose an audio tour equipment supplier pays annual buy-out fees 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 huge migration is to build your own layer that supports your visitor experience, with integrations so data is entered just once, and with a roadmap steered by your curators, your audience development team and your education staff.

A custom app solves that differently: the visitor flow is exactly what your programme requires, 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 with cultural clients on an ongoing basis and also build broader app development projects, combined with a custom ticketing system where that is worthwhile. For one specific museum institution, 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 gets its own visitor flow, its own integrations, and its own accessibility and open data requirements. Below is what we typically build for each category.

Museums & heritage

Museums have the broadest demand for apps. Alongside the classic visitor app with audio tour, there is growing interest in adjacent needs: a family app for weekend family visits, an AR experience for an exhibition, a member portal for friends' associations, and an education tool for teachers who bring their class. What unites all these apps is that they must integrate seamlessly with the collections management system, the ticketing system and the visual identity, and they must stay in service for years without an external supplier charging for every small change.

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

For education we often build a separate teachers' portal, with teaching materials, class codes for pupils and a link to 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 that curators can discover which galleries work and which descriptions are read.

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

The cultural apps we typically build.

The cultural sector has a wide range of app needs. For one museum, a visitor app with audio tour is the most important thing: stories about objects, a route map across the galleries, a sign language track and subtitles that can be called up in any room. For another museum, it is a family app in which parents and children go on a treasure hunt together, with a quiz, audio fragments at child 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 notifications to a simple profile, giving the feeling of being personally involved with the institution, without an external membership administration dictating the visual identity and communication.

For theatres and concert halls we build apps that bring together a season ticket, performance information, programme booklets and venue floor plans, linked to the ticketing system the institution already uses. We build an accessible donation flow into it, with no separate microsite, just one field and an iDEAL button, and integrate with the fundraisers' CRM where wanted. For subscribers there is a digital season ticket that can be transferred when exchanged, a recommendation engine that suits the performances they have attended, and a notification flow for changes to the programme.

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 both in the classroom and in the school hall: a teacher dashboard with groups, a pupil app that guides students through an exhibition, and an after-school module that links the visit to SLO attainment targets. We often work with partner platforms for cultural education and, where wanted, 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 organisations that run events, such as a museum night, a festival weekend or an opening, there is overlap with our event technology: badge systems, phased access by time slot, push notifications for programme changes and an interactive floor plan for on-site orientation. We also build immersive content apps for organisations working 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 beyond the gallery walls.

Finally, for donor and friends associations, we build apps that combine membership, recurring donations and a credit of visits. Integration with CRM packages such as Salesforce NPSP, Stichting Donateursbelangen tools or your own administration is standard in 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 audio tour content.

Built to the strictest standards of the cultural sector.

Culture is a public function. Accessibility, privacy and open data compatibility are not extras at handover; we work on them from the very first sprint.

European Accessibility Act & WCAG 2.2

Accessibility as a public obligation

Since the European Accessibility Act came into force, public cultural apps must meet WCAG 2.2 AA. This applies to 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 dedicated mode for visitors with dyslexia or an intellectual disability. At handover comes an accessibility statement, published on the organisation's website, in line with the requirements set by DigiToegankelijk and the Bewijs van Toegankelijkheid.

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 only collect data that is necessary for educational or operational purposes, record 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. Processor agreements and sub-processor registers form part of the handover, not a later quarterly release. Donation and membership flows also follow strict rules on marketing consent and purpose limitation, which we keep to by default.

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 almost 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 remains findable ten years from now, a requirement that the Mondriaan Fonds and the OCW Subsidieregister increasingly include in their grant decisions.

Ownership of code & data

No vendor lock-in with subsidy-funded projects

For cultural institutions that rely on grants, such as the Mondriaan Fonds, Fonds Podiumkunsten, OCW and municipal cultural funds, code ownership is no longer a luxury but an increasingly firm grant requirement. We always hand over source code, infrastructure configuration and deployment scripts to the institution as its property. Hosting can be with us, with your partner, with SURF, or with a private cloud provider: the choice is yours. We document the architecture so that a future party can take over further development without needing us to be involved.

EU AI Act and culture

Responsible AI in collection access

AI applications in the cultural sector, such as automatic object descriptions, artwork recognition, a sign-language avatar and an AI tour guide, 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 testing, a fallback when the model is uncertain, and human validation for content dealing with historical and sensitive subjects (colonialism, the Second World War, restitution questions). We advise against fully automated text generation for museum wall labels, as the reputational risk to the institution is too great. AI is an aid to the curator, not a replacement.

Fixed Book Price Act & copyright

Rights and licences in code

A lot of cultural content carries layered copyright: 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 lapses. For open data publication we apply the Rights Statements vocabulary and automatically assign the correct licence to every object that goes public. For international collections we also work with European restitution directives, 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 it and rarely replaces it.

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

Standard integrations, no project-specific connections.

We have standardised the integrations mentioned above across several cultural projects. For a new commission, we set up the integration using the same abstraction layer, which means fewer bugs, a shorter lead time, and your own functional management can run it once we step away. For cultural institutions, that last point is more than a welcome extra. It is often a condition of 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 connect with Shopify, Lightspeed or the existing museum POS. For donation flows, we integrate with Mollie, Stripe and, for recurring direct debits, directly with SEPA via the institution's own bank. For education tools, we connect where it makes sense to Magister, SOMtoday or SLO learning lines, so that schools can see visit data and learning outcomes 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 are recognisable for every client.

01 · Audit

Visitor & collection mapping

A day with a curator, learning and engagement officer and IT lead as your guides. Result: the current visitor journey mapped out, pain points marked and content principles recorded.

02 · Design

Scope per audience

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

03 · Build

Short sprints

One working flow delivered per sprint. Curators and the engagement team test along the way, so the first working flow is live within a few sprints.

04 · Cutover

Pilot & rollout

First in one gallery or with a single exhibition, then across the whole institution. With each rollout: training for gallery staff, materials for the front desk, and a handover to your functional management.

05 · Maintenance

Ongoing

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

Working in a sector that values public accountability.

Museum Association 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 chain well see higher return rates."

Digital Heritage Network annual report

"The greatest 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 Fund note on digitisation

"For digitisation projects, we consider whether the applying institution keeps code and data under its own control, and whether the solution fits the broader heritage infrastructure in the Netherlands."

Answers for the cultural institution going digital.

The questions we most often hear from directors, heads of learning and 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 feeding into Europeana or Wikidata. For one specific 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'll find further information on that service page.
What does code ownership mean for grant-funded projects?
For cultural institutions working with a Mondriaan Fund, Fonds Podiumkunsten or OCW contribution, code ownership is not a formality but often a strict grant condition. We always deliver source code, infrastructure configuration and deployment scripts into your ownership. Hosting can be with us, with SURF, or in a private cloud, and that remains your choice. The documentation is such that a successor can take over the work without us needing to be involved any further. For us, this is a principle: we don't want to be the eternal further-development partner; we want to be the right partner for the project in front of us.
How do you approach WCAG 2.2 and the European Accessibility Act?
Accessibility in culture is not a checkbox 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 deliver subtitles, audio transcripts and, where the content justifies it, sign language tracks via an NGT interpreter or an interpreter avatar. Upon delivery, an accessibility statement comes with the project, published on the institution's website and open to review 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 collections management 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 over the database. The principle is that object data comes from a single source, the collection management system, and is not 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 provider?
For ITix, Stager and Spektrix we have standard integrations. For other ticketing systems, we look at the available APIs or webhooks; this usually works, and otherwise we build readable middleware. We are increasingly seeing institutions consider building a custom ticketing system to escape vendor lock-in and the annual fee structure. That is a different project with different trade-offs, and we give you honest advice on whether it makes sense in your case, since not every institution benefits from building its own.
Can you handle open data publication to Europeana or Wikidata?
Yes. For institutions wanting to make their collection data available through Netwerk Digitaal Erfgoed hubs, Europeana or Wikidata, we build the export pipelines, with persistent URIs per object, correct Rights Statements for each asset, and ongoing synchronisation so the open data version stays in line with the collections 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 events 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 separate a temporary app from the permanent offering, or bring both together in one app with a seasonal mode, depending on what your audience is used to.
What 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 give a concrete price for the complete build, including integrations and compliance work, after the planning phase. What we often do is start with one clearly defined flow, such as the audio tour for the permanent collection, and only broaden it once that works and visitors are actively using it.

Talk to us about your cultural app.

A thirty-minute introductory conversation with a director, head of audience engagement or curator. We listen, ask questions and offer an initial direction. No obligation.

Edit content