It's Monday morning. Your operations manager walks past the charging rack and counts: seven handsets dead, two with cracked screens, one that nobody can find. The weekend rental queue at 11am had twenty people in it. Three of them walked off without a guide. A school group is arriving at 10:30 and the French audio pack hasn't been updated since the 2023 rehang.
If any of that sounds familiar, you've already started asking the question: what are the actual alternatives to running a handset fleet?
This isn't a theoretical exercise. The handset model was built for a world where visitors didn't arrive with a better device already in their pocket. That world is gone. The question is which of the alternatives fits your venue, your visitors, and your operational reality — and how to move over without breaking what's working.
The four real alternatives
Everyone talks about "going digital" as if it's one thing. It isn't. There are four distinct replacement paths, and they serve different museums differently.
BYOD with a native app. Visitors download your app before or at arrival. Tour runs on their phone. Offline-capable, typically, and you get deep platform features.
BYOD with a web app via QR. Visitors scan a code, the guide loads in their browser, no install. Lower friction, slightly shallower capability set, usually the right default.
Fixed kiosks or tablets at key stops. No visitor device involved. A mounted tablet at each major work plays content on tap. Fewer stops covered, zero visitor setup.
No guide, better wall text. Skip the audio layer entirely and invest the saved money in exhibit design, longer labels, printed gallery guides, and training floor staff to answer questions.
Each of these has been deployed at real museums and works. None of them is universally right.
The tradeoff matrix
Handsets optimise for one thing: every visitor, at every stop, hears the same content in the language they picked at the desk. That's the thing you're trading against.
Native apps give you the best offline behaviour and the most polished interactions, but they add a download step that cuts adoption. We've seen download-first guides run at 15–25% adoption where a QR-to-web equivalent hit 55–75% at the same venue.
Web apps remove the install friction. The cost: slightly weaker offline support, and you need real Wi-Fi coverage across the galleries. For most museums this is a better problem to solve once than a download wall to carry forever.
Kiosks cover fewer stops by definition — you can't mount a tablet next to every work — but they remove the visitor-phone question entirely. They suit venues with a small number of marquee objects and a visitor demographic that skews older or less phone-comfortable. Maintenance burden is real: screens get dirty, tablets get stolen, power runs need planning.
Going guide-free is under-discussed. A thoughtfully designed gallery with long-form labels, a printed guide for those who want it, and a confident floor team can absolutely work. It works best in small, single-subject museums where the collection itself isn't asking for deep interpretation. It falls apart fast in encyclopedic institutions where visitors are drowning in objects.
Which alternative fits which museum
The honest answer most consultants won't give you: for something like 90% of museums, BYOD with a web app is the answer. The 10% where it isn't usually have specific constraints that are better addressed with a small kiosk or loaner layer on top of BYOD, not instead of it.
Large encyclopedic museum (200k+ annual visitors, multiple floors, 20+ languages needed): BYOD web app as the default. Small handset fleet (15–30 devices) for accessibility and visitors who genuinely can't use a phone. Consider kiosks only at a handful of show-stopping works where you want everyone to get the same story.
Mid-sized regional museum (50k–200k visitors, 3–6 languages): BYOD web app, no handset fleet, one or two loaner tablets at the desk. This is where the economics really shift. The money you stop spending on handset repairs funds better content.
Small specialised museum (under 50k visitors, 1–2 languages, tight collection): Consider whether you need a guide at all. If the answer is yes, web app. If the answer is "maybe," try better wall text first and add a web guide only if visitors ask.
Historic house or heritage site: BYOD web app with location triggers works beautifully here because the narrative is inherently spatial. QR codes tuck into existing signage. A small kiosk in the entry hall can cover the tour for walk-ins who didn't bring a phone.
Traveling exhibition: Web app, always. The exhibition moves; handsets don't travel well; apps and kiosks both add friction at each venue. See our guide on AI audio guides for traveling exhibitions for the deeper version of this argument.
Transition planning
The mistake every museum makes the first time: treating this as a swap. It isn't. A handset retirement is an operational change, and the technology part is the easiest part of it.
Signage. If the QR code is the entry point to your guide, the sign has to be impossible to miss and impossible to misread. Visitors spend about three seconds deciding whether to engage. At the ticket desk, at the gallery entrance, and in the first room — three places minimum. Languages on the sign itself matter more than you think.
Staff training. Your desk team needs to answer "how do I use this?" in under ten seconds, in whatever language the visitor speaks. They need to know what to do when someone's phone is dead, when Wi-Fi hiccups, when a visitor simply refuses. Train for the failure modes, not just the happy path.
Language parity. This is where a lot of transitions quietly lose quality. Your handset had five languages. Your web guide launches with two because "we'll add the others later." Don't. Launch with parity at minimum, and use the moment to go wider — modern platforms can auto-generate additional languages from a single source script, so the incremental cost of going from five to twenty is close to zero.
Accessibility equivalence. This is non-negotiable and it's where kiosks and loaner devices earn their keep. A visitor with low vision needs screen reader support. A visitor with motor limitations needs larger touch targets. A visitor who's deaf or hard of hearing needs transcripts and sign-language video where possible. If your new guide is worse on any of these dimensions than your old handset, you've gone backwards.
For the deeper mechanics of the QR-to-web setup, our QR code audio guide setup guide covers placement, tracking, and the small details that determine whether 30% or 70% of visitors actually scan.
The objection you'll hear most
"Our older visitors won't use phones."
Address this honestly, because it's partly true and partly not. In our data across mid-sized museums, visitors over 65 adopt BYOD web guides at roughly 55–70% of the rate of under-45s. That's lower. It's not the gulf people imagine. A 70-year-old in 2026 has had a smartphone for over a decade. She's not scared of a QR code.
The visitors who genuinely won't engage with a phone-based guide tend to be the same people who didn't pick up a handset either. Handset adoption at most venues runs 20–35% of total visitors. The cohort you're "losing" in a transition is smaller than the cohort that already wasn't using what you had.
The honest middle ground: keep a small loaner fleet for the genuine outliers, make the paper map excellent, and train floor staff to offer a shared tablet walk-through on request. That covers the accessibility and preference cases without propping up a 200-device fleet for the 5% who need it.
For more on the BYOD-versus-dedicated question, see dedicated device vs BYOD audio guide.
The economics nobody spells out
Here's the part that actually changes how operations directors think about this.
A handset fleet is a capex model. You buy the devices, or you rent them on a multi-year contract that amortises the supplier's capex across your visitor numbers. Repairs, replacements, charging infrastructure, inventory labour — all of it is fixed cost. It lands whether visitors pick up the guides or not. If adoption is 20%, you still paid for 100% of the fleet.
The alternatives shift you to opex. A web-app platform on a revenue-share or per-interaction model only charges when visitors actually engage. No fleet to buy. No fixed floor under your costs in slow months. The guide costs you money in proportion to the value it's delivering.
That framing matters for transition planning too. In the first three months of a BYOD launch, adoption is noisy. Some days it's 40%, some days it's 15%, some days your Wi-Fi has a bad hour and it's 5%. Under a capex model, that volatility is your problem. Under a revenue-share model, it's the platform's problem — they get paid when you do, which means their incentive to help you drive adoption is perfectly aligned with yours.
Our deeper BYOD audio guide strategy piece walks through the adoption maths. And if you're specifically untangling a rental contract, replacing rented audio guide hardware covers the contractual mechanics of the exit.
What gets better, not just cheaper
The cost story is the loudest but it isn't the most interesting one. The interesting story is what you can do with a digital guide that a handset couldn't do.
Content updates stop being a production cycle. A curator fixes a factual error on Tuesday; the guide is corrected for every visitor Tuesday afternoon. No re-syncing 200 devices.
You get actual analytics. Which stops visitors skip. Where they linger. Which questions they ask. What languages they pick. Handsets gave you, at best, a play count per stop. Web guides give you behavioural data that feeds back into curation and label writing.
You get interactivity where it helps. A visitor can ask a follow-up question about a work instead of listening to a three-minute segment that didn't quite answer what they wanted to know. This isn't a nice-to-have anymore — it's the thing visitors coming off other cultural experiences have started to expect.
And you get language reach that was economically impossible with handsets. A handset tour in 25 languages required 25 separate recording sessions, 25 sets of voice talent, 25 QA passes. A modern platform generates additional languages from a single source at marginal cost. A small regional museum can offer the same language coverage as a major capital institution.
A note on getting this decision right
Every museum I've worked with that successfully retired a handset fleet did two things. They piloted before they committed — four to eight weeks of running both systems, with real visitors, collecting real data. And they planned the transition as an operations project rather than an IT project. The staff training, the signage, the accessibility layer, the visitor communication — that's what determines whether the new guide feels like an upgrade or a degradation on day one.
Get those right and the technology choice almost takes care of itself. Platforms like Musa fit naturally into this model — QR-to-web delivery, multilingual from a single source, revenue-share pricing so there's no fleet to buy and no fixed cost floor to carry through the transition. But the platform is the easier half of the decision. The harder half is the one only you can make: deciding the handset era is over for your museum, and planning the move with the seriousness it deserves.
If you're weighing app versus web for the delivery layer, our audio guide app vs web app breakdown covers the tradeoffs in more depth. Most museums land on web. A few have good reasons to go native. Both beat the charging rack.