Insights  /  Article

How to choose a visitor app platform: a checklist for museums, zoos and parks

A practical checklist for choosing a visitor app for your museum, zoo, park or attraction, with the questions to put to every vendor.

Pigeon-Tech TeamMarch 18, 202510 min readUpdated Nov 2026
Illustration of a visitor pausing where a garden path splits toward a glasshouse, pond and aviary
On this pageShort versionStart with the visitThree routesEight things to testRed flagsPrintable RFP questionsHow to run the selectionWhere Pigeon Suite fitsFrequently asked questions

Choose a visitor app platform by testing it against the visit you actually run, not against the longest feature list. Write down the few moments where your visitors get stuck, then ask every vendor how their platform handles those moments, who keeps the content current, how it connects to your ticketing and membership systems, and what happens after launch.

A demo shows the vendor’s best day, not your busiest Saturday, so this checklist starts from your visit instead.

The short version

  • Start from three to five visitor moments you want to fix. Features come second.
  • The biggest long-term cost is keeping content, maps and schedules current, so have your own staff test the editing tools.
  • Ask what works indoors, outdoors and without a signal, and get the conditions in writing.
  • Integrations, app store ownership and support after launch decide more than any single feature.
  • See real apps in production first, then roll out one journey before expanding everywhere.

Start with the visit, not the feature list

Before you look at a single vendor, walk your own site the way a first-time visitor does. Start in the parking lot, and note every place where someone would stop, hesitate or ask a member of staff.

Picture a zoo on a busy Saturday (an illustration, not a customer example). Families miss the 2 pm keeper talk because it was only listed at the entrance. Visitors on the far side ask where the nearest restrooms are. The refurbished reptile house gets a fraction of the traffic the big cats get. None of these is a feature. Each is a moment an app could help with, and each points to a different capability: schedules and alerts, a map with filters, a suggested route.

Write your list in the visitor’s words:

  • “Find the exhibit I came for, even on the second floor.”
  • “Know what is happening near me in the next 30 minutes.”
  • “Take an audio tour in my own language.”
  • “Keep the map working on the trail where the signal drops.”
  • “Show my ticket or membership at the gate without printing anything.”

These moments become the test script for every demo.

Three routes: app builder, custom build or platform

Buyers usually meet three kinds of offer:

RouteWhat it isSuitsWatch for
Museum app builder (do it yourself)A template tool where your team assembles screens and contentSmall sites with one simple tour and staff time to build itLimited maps, location features and integrations; your team does setup and upkeep
Custom buildAn agency or in-house team writes an app just for youVenues whose app is core to the business, with a team to keep developing itEvery update, operating system change and fix is new work for your team or agency
Visitor experience platformA ready platform configured and branded for your venue, with an admin console for your teamMost museums, zoos, aquariums, parks and destinationsHow far it can be tailored, and what is included after launch

Weighing a custom build against a platform? The guide Pigeon Suite vs building your own app covers that decision. If the term is new, start with what a visitor experience platform is.

The checklist: eight things to test

A good answer from a vendor is specific and names its conditions. A vague “yes, we do that” is your cue to ask for a demonstration.

1. Fit with your visitor moments

Ask the vendor to show, on screen, how their app handles each moment on your list. Common building blocks include interactive maps, digital wayfinding, self-guided and audio tours, scavenger hunts, camera recognition of animals or exhibits, schedules and alerts, ride wait times, virtual queues, mobile tickets and food ordering. What matters is that the ones you need work together, so a visitor who finishes a tour can see what is on next and how to get there.

2. Location and offline use

GPS works well outdoors and poorly inside buildings. A live “you are here” dot indoors needs additional setup, so ask what your venue would need and what visitors see where that setup is missing. Ask which maps and content keep working once downloaded to the phone, and what still needs a connection (usually the first download, content updates and live information). For more, see how to choose an indoor navigation app and what wayfinding technology is.

3. Who keeps the content true

Exhibits change, animals move and opening hours shift with the seasons. Ask for a live demo of the admin console in which the vendor does three tasks while the person who will maintain the app watches: change the opening time, add an event and swap a photo. Ask which changes appear straight away and which need a new app store release, whether content can be scheduled ahead, and how translations work. Usually, the venue supplies or approves translated text; nothing translates itself.

4. Connections to the systems you already run

Send every vendor a list of your ticketing, membership, point-of-sale and CRM systems by name. For each, ask whether a connection already exists, what the other system must provide (usually an API, a way for two systems to exchange data), who builds and maintains it, and how the timeline is set. A careful vendor will want a technical review before promising a date.

5. Your brand and your app store listing

Visitors should see your name, logo and colors, not the vendor’s. Ask whether the app is published under your own Apple App Store and Google Play accounts, who handles store submissions, and what happens to the listing if you change provider.

6. Data, privacy and security

Ask what visitor data the app collects, whether analytics are anonymized, and how visitors agree to share their location. Get the security basics in writing: encryption in transit and at rest, role-based access for staff, and a log of who changed what. If a vendor mentions a certification, ask to see it.

7. What you learn after the visit

Ask which measures are included, such as popular zones, content views, dwell time and drop-off points, and how each is defined: “dwell time” can mean time in the app or time in a place. Indoor movement data usually needs the same setup as the indoor “you are here” dot.

8. Service after launch

Ask what the service includes: hosting, support, updates when Apple and Google release new operating systems, app store publishing, help with content and staff training. Ask who owns the content and visitor data, and how you take it with you if you leave. The answers belong in the contract, not only in the sales presentation.

Why this matters

most of the work of a visitor app arrives after launch, so give areas 3, 4 and 8 as much time as the demo.

Red flags worth taking seriously

  • Accuracy figures or visitor results promised before anyone has seen your site.
  • “Works offline” or “indoor navigation” with no conditions attached.
  • Integrations described as universal, with no list of systems already connected.
  • No live apps from venues like yours that you can download today.
  • No clear written list of what the service includes, such as hosting, support and updates.

Printable RFP questions for visitor app vendors

Copy these into your RFP or use them as a call script. Ask every vendor the same questions, including us.

Visitor experience

1. Show how your app handles these visitor moments: [your three to five moments].

2. Which capabilities are live in customer apps today, and which are planned?

3. Which languages can the app show, and who provides the translations?

4. What accessibility options does the app offer, such as screen reader support and larger text?

Location and offline

5. What does a visitor see outdoors, indoors and where there is no signal?

6. What setup or hardware does indoor positioning need, and who installs and maintains it?

Content and operations

7. Can our staff change text, images, events and hours without a developer? Which changes need an app store release?

8. Can content be scheduled in advance, and can staff have different roles and permissions?

Integrations

9. Which of our systems [list them] do you already connect to, and what do you need from each?

10. Who builds and maintains each connection, and how is the timeline set?

Brand, data and security

11. Is the app published under our own app store accounts, with our branding?

12. What visitor data is collected, how is consent handled, and is analytics data anonymized?

13. How is data protected in transit and at rest, and is there an audit log?

14. Who owns the content and data, and how do we export it if we leave?

Service and support

15. What does your service include: hosting, support, operating system updates, app store publishing, help with content, training?

16. What does setup involve, and what must our team provide?

17. How long does it usually take from signing to a live app, and what affects that?

Proof

18. Which live apps from venues like ours can we download today?

19. Can we speak to a current customer?

20. Can you walk us through the admin console in a live demo?

How to run the selection

  1. 1

    Plan

    Agree your visitor moments, the systems to connect and who owns the app internally.

  2. 2

    Shortlist

    Send the RFP questions to three to five vendors and compare the written answers.

  3. 3

    Demo with your content

    Ask finalists to walk through your moments, using your map or exhibits where possible.

  4. 4

    Check live apps and references

    Download them and call at least one customer.

  5. 5

    Start with one journey

    Launch one problem first, such as an overlooked exhibit, and agree up front how you will measure it. Measure it, then expand.

  6. 6

    Roll out and keep improving

    Train staff, soft-launch, collect feedback with in-app surveys, then launch fully and review the data.

Where Pigeon Suite fits

Pigeon Suite is Pigeon-Tech’s visitor experience platform for attractions, venues, events and destinations. Each venue gets its own branded app on iPhone and Android, run from a browser-based admin console. Depending on the venue and its systems, it combines digital wayfinding, offline maps, AI recognition of supported animals and exhibits, audio and self-guided tours, treasure hunts, mobile tickets, alerts and visitor analytics. Integrations are already running with ticketing, membership, POS and payment systems, and Pigeon-Tech can build custom connectors for a venue’s own systems when needed.

Live Pigeon Suite apps serve zoos, wildlife parks, aquariums, heritage trails and historic downtowns in the US and France, with 20,000+ downloads on iPhone and Android. Read how Fossil Rim Wildlife Center and Parc Animalier d’Auvergne use it. Pigeon Suite is a 2026 IAAPA Best New Product Award Finalist.

Hosting, support, platform and app updates (including app store release management) and help with content are part of the service, along with white labelling, security and staff roles in the admin console. Pigeon-Tech demos the admin console, shows live production apps, and shows your team how to use the console and update content. The apps support screen readers and larger text. Your venue owns its content and data. Pigeon Suite goes live in days to weeks, not months, and content, events and exhibits are updated from the admin console.

See all features, or the pages for museums, zoos and aquariums, theme parks, fairs, and stadiums and campuses.

Bring your list of visitor moments

Let’s explore one challenge, one journey and one measurable outcome.

Book a conversation

Frequently asked questions

How much does a visitor app for a museum or zoo cost?

Vendors package their services very differently, so a headline figure tells you little. Compare what each one includes in writing: hosting, support, updates, app store publishing, help with content, and who owns the content and data. For Pigeon Suite, book a conversation and we’ll walk through what your venue needs.

What is the difference between a museum app builder and a visitor app platform?

A museum app builder is a do-it-yourself template tool: your team assembles the screens and content. A visitor app platform is configured for your venue by the provider, with maps, location features, integrations and analytics already built, plus an admin console for updates. Builders suit one simple tour; platforms suit venues with several areas, changing events or systems to connect.

Should a visitor app be a downloaded app or a web app?

A downloaded app from the App Store or Google Play is usually the more reliable choice on site, especially for offline maps, notifications and camera features. A web page needs no download, which helps visitors planning at home, but it depends more on a live connection. Many venues use both: the website for planning and the app during the visit.

How long does it take to launch an attraction app?

Pigeon Suite goes live in days to weeks, not months. Whichever vendor you choose, preparing content (maps, stops, texts, photos, audio and translations) is often the longest part. Connections to ticketing or membership systems add time and are best estimated after a technical review.

Can a small museum justify a visitor app?

Often yes, if you start small. One self-guided tour, a simple map and one way to measure use can be enough for the first year. The real question is staff time, because someone must own the content. Pigeon-Tech’s page for small museums offers a free download, the Small Museum Digital Growth Blueprint.

Keep reading