Can a tag replace an audio guide?
It can carry the same audio to a visitor's own phone, which removes a hire desk, a cleaning routine and a cupboard full of chargers. What it also removes is the museum's control of the hardware, because the headphones, the battery, the network and the language are now the visitor's.
What the museum stops owning
A hire desk with a queue at opening. Devices to charge, clean, repair and replace. Deposits, lost units, and a member of staff explaining the same three buttons all day.
A tag on the label removes all of that, and it removes the decision a visitor makes at the entrance about whether the guide is worth the queue and the fee.
What arrives in exchange is a different support load: the visitor whose phone will not tap, whose battery is flat, or who has no headphones. It is cheaper, and it is not nothing.
What the visitor brings instead
Headphones, or not. A visitor without them either plays audio out loud in a gallery or skips it, and which of those a museum prefers is a policy decision that belongs in the plan rather than in the room.
Battery, for a visit measured in hours rather than minutes, on a phone that has already been used for photographs.
Network. Audio is heavier than a page of text, and a basement gallery with no signal and a crowded guest network is the ordinary case, which the offline page covers. Streaming to three hundred phones is a capacity question before it is an NFC question.
And a phone that reads tags at all. A share of visitors carry one that does not, or that has the feature turned off, which the fallback page treats as a planning number rather than an exception.
Audio is not a web page
A tap opens a page. A page that begins talking by itself is not something to rely on, so the design that works lands on a single obvious play control, already showing which object it belongs to, and starts in one press.
Keep each piece short and tied to one object, so a visitor who skips ahead is never lost and never has to scrub through a recording made for a different route.
Publish a transcript beside it. It serves anyone who cannot use sound, anyone without headphones, and anyone in a hurry, and it is the part the accessibility page insists is a property of the page rather than of the tag.
And name the file for the object rather than for the route. A page reached from a label has to make sense on its own, since nobody arrived at it through a menu.
Why both usually survive
The hire device stays for the visitors the tap cannot serve: no smartphone, no headphones, a school group whose phones are in a box, and anyone for whom the lent device is the accessible option rather than the fallback.
That is not a failure of the tag. It is the same conclusion the label page reaches about printed labels: the tap is an addition, and the moment it becomes the only route, the exhibition has excluded someone.
What changes is the ratio. A museum that expected to lend four hundred devices lends forty, and the desk stops being the bottleneck at ten in the morning.
Frequently asked questions
Do visitors need an app?
No, if the tag holds a web address and the audio plays in the browser. An application is a second decision, and most visits do not justify a download.
What about visitors with no headphones?
They play it aloud or skip it. Decide which of those the galleries can live with before removing the hire desk, and keep transcripts either way.
Will the network cope?
That is the real question. Audio to hundreds of phones in a basement gallery is a capacity problem, and it decides whether this works at all.
Should the audio guide be retired?
Usually not entirely. The lent device serves visitors the tap cannot reach, and it is the accessible option for some of them.