Full-Cycle Mobile Audio Guide for Museums

A visitor approaches an exhibit and hears a narration without a single tap. Or scans a QR code on the plaque. Or manually enters the number. All three scenarios must work offline—museum Wi-Fi often fails. According to research, over 60% of visitors use mobile devices in museums, but an unstable netw

Development and support of all types of mobile applications:

Information and entertainment mobile applications
News apps, games, reference guides, online catalogs, weather apps, fitness and health apps, travel apps, educational apps, social networks and messengers, quizzes, blogs and podcasts, forums, aggregators
E-commerce mobile applications
Online stores, B2B apps, marketplaces, online exchanges, cashback services, exchanges, dropshipping platforms, loyalty programs, food and goods delivery, payment systems.
Business process management mobile applications
CRM systems, ERP systems, project management, sales team tools, financial management, production management, logistics and delivery management, HR management, data monitoring systems
Electronic services mobile applications
Classified ads platforms, online schools, online cinemas, electronic service platforms, cashback platforms, video hosting, thematic portals, online booking and scheduling platforms, online trading platforms

These are just some of the types of mobile applications we work with, and each of them may have its own specific features and functionality, tailored to the specific needs and goals of the client.

Showing 1 of 1All 1734 services
Full-Cycle Mobile Audio Guide for Museums
Medium
from 1 week to 3 months

Our competencies:

Frequently Asked Questions

Latest works

  • image_mobile-applications_feedme_467_0.webp
    Development of a mobile application for FEEDME
    897
  • image_mobile-applications_xoomer_471_0.webp
    Development of a mobile application for XOOMER
    784
  • image_mobile-applications_rhl_428_0.webp
    Development of a mobile application for RHL
    1216
  • image_mobile-applications_zippy_411_0.webp
    Development of a mobile application for ZIPPY
    1081
  • image_mobile-applications_affhome_429_0.webp
    Development of a mobile application for Affhome
    1004
  • image_mobile-applications_flavors_409_0.webp
    Development of a mobile application for the FLAVORS company
    599

A visitor approaches an exhibit and hears a narration without a single tap. Or scans a QR code on the plaque. Or manually enters the number. All three scenarios must work offline—museum Wi-Fi often fails. According to research, over 60% of visitors use mobile devices in museums, but an unstable network undermines the experience. That's why developing a mobile audio guide for a museum must account for autonomy, reliable detection, and resource efficiency. A well-designed architecture can reduce support and licensing costs—for instance, dropping commercial maps saves money. Our team builds audio guides for museums from scratch: from beacon selection to store publishing. Over the years, we've delivered dozens of projects, including large state museums. In this article, we'll dive into technical details: how we build a reliable offline system that never lets visitors down.

Contact us to discuss your project and get a preliminary estimate.

How Automatic Exhibit Detection Works

The most interesting scenario is a proximity trigger with no user action.

iBeacon / Bluetooth LE. Beacons near each exhibit (Estimote, Kontakt.io). iOS: CLLocationManager.startRangingBeacons(satisfying:) obtains a list of beacons with proximity (.immediate / .near / .far) and rssi. We pick the closest with .immediate and start audio. Important: we don't react to every proximity change—apply a 2-3 second debounce to avoid switching audio due to random signal fluctuations.

Android: BluetoothLeScanner with a filter by beacon manufacturer UUID. The AltBeacon library simplifies ranging. A Foreground Service is needed for background scanning—while the app is active, normal scanning suffices. Bluetooth LE — official Android documentation.

QR scanning. Fallback method. iOS: VNDetectBarcodesRequest (Vision) — faster than AVMetadataOutput for single scans. Android: ML Kit Barcode Scanning. Flutter: mobile_scanner.

Manual number entry. Always as a fallback—in case Bluetooth is off or beacons are missing.

Comparison of Detection Methods

Method Accuracy Offline Capability Implementation Cost
iBeacon High (up to 1 m) Full (offline) Medium (beacons $10–30 each)
QR code High (camera-dependent) Full (offline) Low (paper labels)
Manual entry Low (input errors) Full (offline) Zero
NFC tags Medium (contact) Full (offline) Medium (tags $1–5 each)

Offline Content and Data Structure

A museum with 200 exhibits means 200 audio files, images, and texts. Total 300–500 MB. Update strategy:

  • On first launch, download a 'lightweight' package: texts, 200px previews, metadata (beacon UUIDs, exhibit numbers)
  • Audio downloaded on demand or in batches with caching

Storage structure: CoreData/Room for exhibit metadata (id, title, beacon_uuid, qr_code, languages). Audio files in Application Support/filesDir with id→path mapping. SQLite query 'find exhibit by beacon UUID' is instantaneous.

Multilingualism: user selects language at start. Audio and texts stored with language suffix. Only the selected language is downloaded—saving space.

Audio caching details For streaming playback, we use AVAssetResourceLoader (iOS) and CacheDataSource (ExoPlayer). Cache is stored up to 1 GB, evicted LRU when full. Only the current session's audio is guaranteed to be cached. Users can preload all audio via settings.

Exhibit Audio Player

AVPlayer (iOS) / ExoPlayer Media3 (Android) / just_audio (Flutter). Features specific to audio guides:

  • Auto-stop when moving away from exhibit (proximity returns to far)
  • Progress saved: returning to exhibit resumes from pause point
  • Playback speed: 0.8x for elderly visitors, 1.5x for quick ones
  • Lock screen controls via MPNowPlayingInfoCenter (iOS) / MediaSession (Android)

Interactive Exhibition Map

A hall map with exhibit markers. Not Google Maps—museums want no external dependencies or fees. We use an SVG hall map: rendered in a WKWebView with interactive SVG (iOS), WebView (Android), or flutter_svg with GestureDetector (Flutter).

Alternatively, a native implementation with Canvas/CustomPainter: load a PNG map as a base, draw exhibit points on top with pinch-to-zoom scaling.

Visitor's current location on the map is determined via the same iBeacon ranging: we identify the hall by the set of visible strong-signal beacons. No GPS—it doesn't work indoors. Dropping commercial maps saves up to several hundred dollars a year in licensing.

Why a CMS for the Museum Is Essential

Administrators update texts and audio without releasing a new app version. Backend: simple REST API + S3 for media files. On launch, the app checks the manifest version—if changed, it downloads the delta. This saves moderation time and allows quick updates to tour content.

How to Implement an Offline Audio Guide: Process

  1. Analysis and design. Gather requirements: number of exhibits, halls, languages, budget. Choose stack: native or cross-platform.
  2. Development. Backend (CMS, API), mobile app (player, map, detection), beacon integration.
  3. Testing. Real-world testing with beacons, offline mode, load testing.
  4. Deployment. Publish to App Store and Google Play, configure Code Signing, Provisioning Profile, TestFlight.
  5. Maintenance. 3-month warranty, then contract.

Timeline Comparison

Phase Duration (basic version) Duration (extended version)
Analysis 3-5 days 5-7 days
Development 2-3 weeks 4-5 weeks
Testing 1 week 1.5 weeks
Deployment 3-5 days 5-7 days

What's Included

  • Architecture documentation and API description
  • App source code (Git repository)
  • Operating manual for staff
  • Staff training (1-2 days)
  • Test run and tuning with real beacons
  • Support during warranty period

Timeline and Cost Estimation

Basic version (QR + offline + player + map) — 4-6 weeks. Version with iBeacon and CMS — 7-9 weeks. Exact cost is calculated after requirements analysis. We'll assess your project for free—contact us for a consultation.

Certified developers with 5+ years of experience guarantee quality. We've built 10+ audio guides for museums in Russia and the CIS. iBeacon is the standard for proximity solutions.

Get a free project estimate: contact us, and we'll prepare a commercial proposal.