The Device Problem: Why Museums Are Abandoning Traditional Audio Guides

Walk into most mid-sized museums and you'll still see them: the stack of handheld audio guide devices behind the desk, each one charging overnight, each one sanitized between uses, each one representing a small operational burden that compounds daily.

These devices work. They've worked for decades. But they solve a problem that no longer exists.

The original logic was sound: not everyone had a smartphone, and those who did might not want to drain their battery or use their data. So museums invested in dedicated hardware. Visitors got a curated experience. Museums got control.

But control came with costs that extend far beyond the purchase price.

Every device needs charging. Every device needs cleaning. Every device occasionally breaks, gets lost, or returns with a cracked screen. Someone has to manage inventory, troubleshoot technical issues, and stand at the entrance explaining how to use a device that feels immediately unfamiliar in the visitor's hand.

Then there's the bottleneck. On busy days, the desk becomes a chokepoint. Visitors queue to collect devices, queue again to return them. The ritual delays entry and creates friction precisely when first impressions matter most.

Progressive web apps eliminate this entire infrastructure.

A visitor scans a QR code. The guide opens instantly in their browser. No download. No app store. No permissions request. They're holding their own phone—a device they already trust, already understand, already keep charged.

This isn't about being modern for the sake of it. It's about removing obstacles between a visitor and your collection.

PWAs work offline once loaded, so connectivity isn't the barrier it once was. They update silently in the background, so your content stays current without anyone manually updating hundreds of devices. And because they run in a browser, they work equally well on iOS, Android, or any platform a visitor brings.

The visitor experience shifts too. With their own device, people can start the guide before they arrive, continue it after they leave, share it with someone who couldn't make the visit. The museum experience extends beyond your walls without you managing a single extra device.

Some curators worry about losing control—what if visitors don't have smartphones, or resist using them? Fair concerns, but the data tells a different story. Smartphone ownership among museum visitors is near-universal, and the friction of downloading a native app has always been higher than the friction of scanning a code.

The real question isn't whether PWAs work better than traditional devices. They do, measurably. The question is whether your institution is ready to let go of infrastructure that feels safe because it's tangible.

Devices sit on a shelf. You can count them. You can hold them. But that tangibility is expensive, and it doesn't serve visitors better—it just serves a model of control that museums inherited, not one they chose.

PWAs don't require you to abandon audio guides. They require you to abandon the assumption that visitors need your hardware to access your stories.

The guide was never about the device. It was always about the voice.