Audio guides vs museum apps: which should a museum choose?

Purpose-built handheld players owned or rented by the museum and lent to visitors at a handout desk. Content is stored locally on the device, controls are physical, and the museum controls charging, cleaning, and content updates. Hardware such as Trend is designed for continuous daily lending, with long battery reserve between uses and support for up to 32 languages on one device.

Applications the visitor downloads from an app store onto their own phone. A native app can use the phone's GPS, camera, and notifications, and it stays on the visitor's phone after the visit. It also requires a download, storage space, a compatible operating system version, and ongoing development work to keep pace with iOS and Android releases.

Browser-based guides opened by scanning a QR code, with no store download. Web tours remove the download barrier and work across operating systems, which makes them the more practical app format for a single visit. They still depend on the visitor's phone battery, headphones, and a working connection for streamed content, and browser support for offline caching is less dependable than a native app's local storage.

Being outdoors does not by itself favour an app. Dedicated audio guides can use battery-powered RF triggers outdoors while keeping all content on the device, which works well when a sculpture park, heritage site, or open-air museum has a controlled entrance and exit for handout and return. An app with GPS and a map becomes practical when a city route is too long or dispersed to recover hardware, or has no staffed return point. The decision depends on fleet recovery and wayfinding needs, not simply whether the route is indoors or outdoors. Trigger choices are compared in museum audio guide triggering modes.

An app reaches visitors before they arrive and can remain on their phone after they leave. This is useful for visit planning, membership access, event notifications, and content that the museum wants visitors to open directly on their phone. It is not the only way to continue the relationship. At the exit, visitors can return an audio guide through an Interactive Kiosk that starts a quiz or survey and, with consent, collects an email address. Personalized Visitor Reports can then send what the visitor saw, what they missed, and links to the museum shop or future exhibitions. Ticketing integration can provide the same follow-up route through contact details supplied at purchase. A membership or repeat-visit strategy therefore does not by itself require an app.

A device fleet needs a daily operation: handout, return, charging, cleaning, and content sync. Small sites, unstaffed heritage locations, and venues without a secure charging room may not be able to run that workflow. A QR-code web tour removes the handout and return desk, although the museum still needs clear signage, content maintenance, analytics, privacy controls, and a way to help visitors who cannot open the tour. For sites that could not otherwise operate a fleet, lower uptake may be an acceptable trade-off.

For a small museum with internal web capacity, a mobile web tour can be a sensible first test. Museum practitioners discussing low-cost tour platforms on r/MuseumPros recommended starting with a simple website and QR codes, then upgrading only after observing visitor response. A useful pilot covers one gallery or temporary exhibition and measures passers-by, scans, starts, completed tracks, support requests, staff time, and accessibility failures. This tests demand without committing immediately to a native app or full device fleet.

A museum that promises interpretation to every visitor cannot assume every visitor has a suitable phone. Some visitors arrive with low battery, no headphones, no local data plan, an old operating system, or no smartphone at all. International visitors may avoid roaming data entirely. A fleet sized for peak demand, with charged spares and a working handout process, lets the museum remove these visitor-side failure points. Fleet sizing for that promise is covered in how many audio guides does a museum need.

A dedicated fleet gives every visitor the same controls, trigger behaviour, audio output, and content. Apps and web tours inherit differences between phones: screen sizes, operating-system versions, browser settings, permissions, audio connections, and accessibility configurations. A responsive interface reduces some variation, but no museum can test every current and older device that enters the building. The result is an inconsistent experience and more support work for front-of-house staff.

Audience mix can change the answer. In a June 2026 r/MuseumPros discussion of BYOD and dedicated devices, contributors noted that children often lack their own phones, family visits can be hard on consumer electronics, and some older visitors prefer a simple loan device to installing and learning an unfamiliar app. These are practitioner observations, not universal rates. Museums should segment a pilot by school groups, families, age, language, and accessibility needs instead of applying one uptake forecast to the whole audience.

Many visitors do not want a tour to use the phone battery they still need for tickets, maps, photographs, messages, and the journey home. Streaming audio, keeping a screen active, and using Bluetooth or mobile data add to that concern. Headphones create a second barrier: visitors often do not bring them, may not want to pair their own wireless set, and cannot reasonably play narration through a phone speaker in a shared gallery. A charged dedicated player supplied with cleaned headphones removes both decisions at handout.

A native app adds several steps before listening begins: find the store listing, wait for the download, provide storage space, grant permissions, and open the correct tour. A QR-code web tour removes the app-store step but still depends on signage, connectivity, browser compatibility, battery, headphones, and willingness to scan. Each step can lose users, but neither format should be assigned a universal conversion rate; the museum must measure its own audience. In Look2Innovate deployments measured through Visitor Statistics, average listen-through reached 98% in one dedicated-device reporting period. Listen-through is the mean percentage of each started audio track heard, calculated across plays with a recorded listening percentage. The client-specific sample size and reporting period are not published, so 98% is a deployment example, not a benchmark. It does not measure the share of all museum visitors who took a guide. Uptake asks who starts; listen-through asks how much those users hear after starting.

Test the funnel in person. During a defined observation window, stand near the QR sign and count how many visitors pass it and how many visibly scan it. For the same window, use tour analytics to count guide opens, audio starts, and completed tracks. Join the manual and digital counts only when their time window and location match. If the analytics cannot separate those stages, report only the stages that can be measured instead of presenting an estimated full funnel.

Format is not the only influence on uptake. Museum professionals discussing QR codes reported better results when frontline staff mentioned the codes and explained how to use them, while also warning that this promotion creates staff work. They also recommended an alternative for visitors who cannot or will not use the technology. See the r/MuseumPros QR-code discussion. Report signage, staff promotion, support time, and alternative provision alongside scan and listening figures; otherwise two museums are not measuring the same deployment.

Dedicated players store all content locally and need no network during the visit. Historic buildings with thick masonry, basement galleries, and temporary venues often have patchy Wi-Fi and mobile coverage, and a streamed web tour fails exactly where the visitor density is highest. A native app can pre-download content, but only if the visitor completes that download before entering the dead zone, which returns to the uptake problem.

Some blind and low-vision visitors benefit from physical buttons, tactile orientation, and an optional braille keypad; others prefer the screen reader and accessibility settings they already use on their own phone. A visitor-phone tour therefore needs well-built, WCAG-conformant markup. A dedicated fleet can also be issued with induction neckloops or other hearing support, while a phone-only plan depends on each visitor bringing a compatible device and audio connection. The museum should test both channels with disabled visitors and keep loan equipment for anyone without a suitable phone. The full picture is covered in accessible audio guides for museums.