Skip to content

BlogFor companies

Museum app development: your own AI guide in about 2 months

Museum app development in 2026 means your own guide on visitors' phones: it recognizes an artwork from a photo and tells its story in the visitor's language, at the depth they choose. We explain how it works in plain words, how it compares with devices and subscription platforms, our 8-week plan and what a budget of about $20,000 covers.

For companies19 min readPublished By Eryk Kruk, CEO
Museo: scan screenMuseo: scanMuseo: narration modes screenMuseo: narration modesMuseo: narration screenMuseo: narration
Museo, the AI museum guide app we built: the visitor scans an artwork, picks a narration mode and hears its story. Screens from the live app in the App Store and Google Play.

A visitor stops in front of your best painting, looks for a number on the label, finds none and walks on. A family asks the front desk for a guide in Spanish, and there is none. The supplier of your audio guide devices sends a quote for a new fleet. If that sounds familiar, this article is for you: it shows what your own museum guide app does, how it works, what it costs and how to get it live in about 2 months.

Short answer: museum app development no longer means a year-long project. Your own guide app recognizes an artwork from the visitor's photo, narrates it in 20+ languages, meets accessibility rules and shows you which rooms people visit. On our Museo platform, a museum's own guide takes about 2 months and starts from about $20,000. Devices and subscription platforms exist too, but devices need staff at the desk every day, and a platform keeps your guide inside someone else's app.

We write from our own product, not a brochure. We built Museo, an AI museum guide app that is live in the App Store and Google Play, so the plan and the numbers below come from our own work. The article is for museum directors, digital leads and whoever writes the business case.

What a personal AI museum guide does for your visitors: recognize, narrate, adapt

In short: a personal AI museum guide is an app on the visitor's own phone that recognizes an artwork from a photo, tells its story in the visitor's language and adapts the story to the visitor: short or long, for children or for experts, with accessibility built in. Three verbs define it: recognize, narrate, adapt.

  • Recognize. The visitor points the camera at a painting, sculpture or object, and the app finds it in the museum's collection in about 100 ms. No numbers to type, no QR codes on the walls.
  • Narrate. The story plays in the visitor's language. AI narration means the text is drafted with AI, approved by your curator and read aloud by a synthetic voice. In Museo, narration comes in 20+ languages and the app interface in 28.
  • Adapt. The visitor picks a narration mode. Museo's visitor app offers Classic Guide, Expert, For Kids and Accessibility. During design we prototyped 5 narration modes.

Think of it as a private guide who speaks every visitor's language and never gets tired: the visitor decides where to stand and how deep to go, and the guide follows. A digital museum guide that plays a fixed tour in a fixed order is a simpler product. Deeper personalization, such as a guide that learns what a visitor likes, is on Museo's roadmap for a premium tier. It is not live yet, so it is not part of the budget below.

What this means for you. One app replaces the number keypad, the missing language at the desk and the guesswork about what visitors look at. A new language becomes a review by your staff, not a new recording contract.

Devices, a subscription platform or your own app: why owning the guide pays off

In short: a museum can rent devices to visitors, put its tour on a ready-made subscription platform, or publish its own guide app. With devices you run the guide by hand, and with a platform you rent it. Your own app is the only option where your brand, your content and your visitor data stay with you, and where visitors find a work with a photo instead of a number.

A subscription platform is an existing guide app or web page where the museum uploads its tours and pays every year. A web app is a website that behaves like an app: it opens in the phone's browser from a link or a QR code, with nothing to install. The table compares the three options on what matters to a museum.

Three ways to give visitors a guide, as of November 2026
What matters to the museumHandheld devicesA ready-made subscription platformYour own guide app on Museo
Whose app the visitor usesNo app: a device from the deskThe platform's app or a web pageYour app, with your name and icon in the App Store and Google Play
How a visitor finds a workTypes a number or walks near a markerDepends on the platform: often a list, a number or a QR codeTakes a photo: recognized in about 100 ms
LanguagesEach language is a new recordingWithin your plan; you write and translateAI narration in 20+ languages, approved by your curator; interface in 28
Visitor dataAlmost noneOn the platform's termsScans, most-viewed works and visit heatmaps in your admin panel
Staff workHand out, charge, clean and collect devices every open dayUpload and update tours yourselfReview and approve texts in the admin panel
How you payA fleet purchase, then staff time every dayA subscription, again every yearFrom about $20,000 once, plus usage-based running costs
What you keep if you leaveThe devicesAsk before you signYour app in your own store accounts; content export agreed in the contract

Before you sign anything, ask every option the same four questions: whose app does the visitor download, who sees the data, which languages are included and who writes them, and what do you keep if you leave. Your own app answers all four in the museum's favor.

A subscription platform can be enough for one temporary exhibition in one or two languages, or as a short pilot. For a permanent collection, visitors from many countries and a guide that carries your brand, your own app pays off: you pay for the build once, and after that mostly for usage, not for a subscription that comes back every year.

What this means for you. With a rented guide, the cost returns every year and the data stays elsewhere. With your own app, the money goes into something the museum keeps: an app under your name, in your own store accounts, with your texts, audio and visitor data.

Artwork recognition from a photo: no QR codes on your walls, an answer in about 100 ms

In short: the visitor takes a photo, and the app finds the matching work in your collection, in about 100 ms in Museo. Nothing hangs on the walls: no QR stickers, no numbers, no hardware to install. Here is how it works, in plain words.

An image model turns the visitor's photo into an image embedding: a list of numbers that describes what is in the picture. Think of it as a fingerprint of the image. Two photos of the same painting, one from the front and one from the side, get very similar fingerprints, while a different painting gets a different one. Vector search is the step that compares fingerprints: it finds the work in your collection whose fingerprint is closest to the visitor's photo.

Artwork recognition in four steps. One: the visitor takes a photo of the artwork. Two: an image model turns the photo into an embedding, a list of numbers that describes what is in the picture. Three: vector search compares it with the embeddings of that museum's collection and finds the closest artwork. Four: the app opens the artwork and plays its narration. Recognition takes about 100 ms once the GPU is warm.1PhotoThe visitor points the phone at the work2Image embeddingA model turns the photo into numbers3Vector searchClosest match in this museum's collection4Artwork and narrationStory in the visitor's languageAbout 100 ms once the GPU is warm
How Museo recognizes an artwork: photo, image embedding, vector search, narration.

The image model runs on a GPU, a type of processor built for AI work, rented from a cloud provider by the second. The phone crops the photo and sends it to that model. The search compares the photo with the works of your museum only, so a similar piece in another museum never gets mixed in. If the best match is close enough, the app opens the work and plays its story. In Museo the model is kept ready ahead of demand, like a taxi waiting with the engine running, so the answer comes the moment a visitor lifts the phone.

Recognition from the image itself holds up at an angle, under warm spotlights or with part of the frame cut off. There is nothing to print, stick, clean or replace. A new work in the collection needs photos and an update of the index, the stored fingerprints of your collection, not a new sticker. Plan for these limits:

  • Look-alikes. A series of prints or near-identical objects needs several photos per work and a test on exactly those works.
  • Glass and reflections. Works behind glass need photos taken in the real gallery light, not only catalogue scans.
  • Objects in 3D. Sculptures and objects in cases need photos from several sides.
  • The threshold. This is the minimum similarity the app accepts as a match. A wrong artwork with a confident story is worse than "try again", so the threshold is set with real visitor photos.

What this means for you. No hardware to buy, install or maintain in the rooms, and no stickers next to the works. The work that remains is photographing your collection once, and that is part of the 8-week plan below.

AI narration in 20+ languages that your curator signs off: how quality stays in your hands

In short: people decide what is said, and machines do the production and the checks. In Museo, AI drafts the description, a curator edits and approves it, the approved text is translated and voiced in 20+ languages, and every audio clip is turned back into text and compared with its script. A clip that drifts goes to a person before any visitor hears it.

It works like a newsroom: AI writes the fast first draft, and your curator is the editor who signs every page. Two terms help here. Text-to-speech is software that reads a text aloud in a synthetic voice. Speech-to-text does the opposite: it listens to a recording and writes down what it hears, and that is how every clip gets checked.

  • Draft. Collection data is imported, or a staff member photographs the work and its label in the Ambassador app, Museo's app for museum staff. AI drafts the description and fills in the metadata: the artist, the date and other facts about the work.
  • Approve the source text. A curator fixes facts, names and tone in the admin panel. Nothing is published without approval.
  • Translate and voice. The approved text is translated automatically and voiced by a text-to-speech engine chosen per language.
  • Check every clip. Each clip goes through speech-to-text and is compared with its script. Clips that drift are flagged for a person to listen to.
  • Keep it current. When a source text changes, or the prompt, the written instruction that tells the AI how to write, versioning flags the descriptions and audio that went stale.
Screens of the Museo Ambassador app: the home screen with an Add New Artwork button, a review screen with the label photo and artwork photos, adding a museum, a list of uploaded artworks ready to sync, and the camera framing a painting.
Museo Ambassador, the app staff use to add works: photograph the work and its label, and the AI pipeline drafts the rest. App Store screens of the live app.

Narration modes are separate versions of the same story, not a playback speed. Classic Guide runs about a minute. Expert runs 1-2 minutes and adds historical context and artistic significance. For Kids and Accessibility are written for their own listeners. Each mode is its own text, so each mode gets its own approval.

Plan the review work: a native speaker checks your top three languages on a sample of works, you give the pipeline a list of names that must never be translated, and someone from the museum listens to the clips of the 20 most visited works before launch.

The Museo admin panel: a list of artworks with thumbnails, titles, artists, years, the source of each photo and a status of Ready or Needs Review.
The Museo admin panel: every work shows Ready or Needs Review, so the curator sees at a glance what still waits for approval. A screen from the live product.

What this means for you. Content is usually the biggest cost of any guide. Here, a new language or a corrected date is a review in the admin panel, not a new recording session, and nothing goes live without your curator's approval.

From signing to the App Store in 8 weeks: the plan, week by week

In short: a museum's own guide on Museo takes about 8 weeks from signing to the stores, if the museum supplies collection data in the first week and approves texts on time. Recognition, narration and the admin panel already work in a live product, so the 8 weeks go into your collection, your content and your brand, not into building the basics.

  • Weeks 1-2Discovery and collection import. Scope frozen: works, rooms, languages, narration modes. Collection data imported, brand brief agreed.
  • Weeks 2-4Content enrichment and translation. AI drafts, curators approve the source texts, then translation and narration in every language.
  • Weeks 3-5Recognition indexing. Photos of every work in the rooms, the index built, a test set of real phone photos, the threshold tuned.
  • Weeks 4-6Your app. Name, icon, colors, home screen, store listings, accessibility checks and offline packs, so the guide works in rooms with no signal.
  • Week 7Testing on site with visitors. Real phones, real light, every main language, a screen reader user. Fixes the same week.
  • Week 8Store release. App Store and Google Play review, a short briefing for front-of-house staff, launch.

What the museum provides

  • Collection data. Titles, artists, dates, rooms and existing texts, as an export from your collection system or a spreadsheet.
  • Photos and rights. Permission to photograph the works in the rooms and the right to show the images in the app.
  • A content owner. One curator or educator who approves texts, with a few hours a week in weeks 2-6.
  • Gallery access. Time in the rooms, ideally before opening, to photograph works for recognition.
  • Brand and accounts. Logo, colors and your own Apple and Google developer accounts. Apple asks organizations for a D-U-N-S number, a free company number from Dun & Bradstreet that Apple uses to confirm who you are (government organizations are exempt), so start in week 1 (Apple enrollment).
  • Approvals. The privacy policy, an accessibility statement if you are a public body, and the go-ahead for release.

Projects like this rarely slip because of technology. They slip while someone waits for a collection export or a text approval, so put the approval dates into the plan on day one. You get a fixed price per milestone and a new build on your phone every week, so you see progress before you pay for the next step. How we run every project, from the first call to the stores, is on how we work, step by step.

What this means for you. You know the launch date before you start, and the main risk, waiting for approvals, sits on a calendar the museum controls.

What your own museum guide app costs: from about $20,000, and what that covers

In short: about $20,000 for your own personal guide built on the Museo platform, delivered in about 2 months. That is a starting point for a typical scope, not a quote: collection size, the number of languages and custom features move the price. Running costs come on top and depend mostly on use.

What is included

  • Your branded iOS and Android app in the App Store and Google Play, with the interface in 28 languages and an offline mode.
  • Recognition indexed on your collection.
  • AI descriptions and narration in the languages and narration modes you choose, from the 20+ available.
  • The admin panel, the web page where your staff edit content and see the numbers, with its interface in 20 languages: import, AI enrichment, auto-translation, approval, and analytics with scans, most-viewed works and visit heatmaps (floor plans colored by how many people stop in each room).
  • WCAG 2.1 AA accessibility, testing on site, store release and a 6-month guarantee.

Running costs

Running costs of your own museum guide app, as of November 2026
ItemHow it billsWhat to expect
Store accountsApple yearly, Google once$99 a year (Apple), $25 once (Google Play)
Recognition GPUPer second while the GPU runs, zero when nobody scansUp to about $2,900 a year even if one L4 GPU stayed warm 10 hours a day, every day; less when it sleeps between visitors
AI narrationGPU time when you add or change content, not per visitorA one-off cost per work, mode and language. Replays cost only storage and transfer
HostingBackend, database, photos and audioDepends on visitor numbers; we estimate it for your traffic in week 1
Care after the guaranteeMonthly, or updates when you need themCare from $2,000 a month, or updates ordered once a year before new iOS and Android versions

GPU figure: one L4 GPU at Modal's list price ($0.000222 a second) for 10 hours a day, 365 days. The GPU is serverless: you do not rent a whole server, the provider starts the GPU when there is work and bills only while it runs, so a GPU that sleeps when nobody scans costs less. The backend in the table is the server side of the app that stores your works, texts and audio. Store fees: Apple, Google Play.

What changes the price

  • Collection size. Every work is photographed, indexed, described and approved.
  • Languages and modes. Each language and each narration mode is text someone approves.
  • Content you already have. Good existing texts shorten the work. Writing from scratch lengthens it.
  • Custom features. An integration with your ticketing or collection system, games or a custom design go beyond the base scope.

For public museums: a project this size is far below the EU-wide tender threshold for supplies and services, EUR 216,000 for most museums in 2026-2027 (EU thresholds 2026-2027, Polish Public Procurement Office). National thresholds differ, so check yours. What goes into any app budget is in How much does it cost to build an app in 2026?.

What this means for you. One build price, plus running costs that follow your visitor numbers, instead of a device fleet to replace or a subscription that returns every year. All our other prices, including Care, are on the Codigee pricing page.

Accessibility and the law: what your museum app must meet

In short: build to WCAG 2.1 AA. WCAG is the international standard for accessible websites and apps, and AA is the level most laws point to. For public museums in the EU it is in practice a legal requirement: the Web Accessibility Directive covers the websites and mobile apps of public sector bodies, and mobile apps have been in scope since 23 June 2021. Museo is built to that level.

  • Public museums. Directive (EU) 2016/2102 applies, and each app needs an accessibility statement, on your website or with the download information (Article 7).
  • The heritage exception. Reproductions of items in heritage collections that cannot be made fully accessible, for example because of preservation or authenticity, are excluded (Article 1). The app around them is not: menus, the player and the texts must be accessible.
  • Private museums and foundations. NGOs that do not provide services essential to the public are outside the directive. WCAG 2.1 AA is still the right target: your visitors are the same people.
  • The European Accessibility Act. Since 28 June 2025 it covers a list of consumer services, including e-commerce (Directive (EU) 2019/882, Article 2). A guide app is not on the list, but ticket sales or a paid tier inside the app may count as e-commerce. Ask your lawyer about your case.

In the app, accessibility means more than contrast. Museo works with screen readers, the phone feature that reads the screen aloud for blind and low-vision visitors, and with larger text, and it has a separate Accessibility narration mode. Test it with a screen reader user on site in week 7, not only with an automated checker.

What this means for you. Accessibility is part of the build and the price from week 1, not an extra project after launch, and your accessibility statement can be ready on release day.

Why museums build their guide with us: a senior team that already shipped one

In short: pick a team that has a museum guide live in the stores, lets you try it in front of a real artwork and gives you a fixed price before you sign. We pass that test with Museo, and our small senior team is the reason we can deliver a museum's own guide in about 2 months.

The Museo case: from a museum's problem to a live guide

Museo is our own product, built for a problem most museums know: going digital meant months of curator writing and voice-actor sessions, language by language, with no IT team to run the software and no idea how visitors move through the rooms.

  • ProblemMonths of writing and recording in every language, no IT team, no visitor data
  • What we didOne connected product of 6 parts: Flutter apps for iPhone and Android, an admin panel a curator runs from a browser, and an AI pipeline that recognizes works, drafts the narration and checks it
  • ResultFrom concept to a live product in about 3 months, in the App Store and Google Play, with recognition in about 100 ms, narration in 20+ languages and WCAG 2.1 AA

Flutter is Google's toolkit for building the iPhone and Android app from one code base, which is why one team ships both at once. An AI pipeline is a chain of automatic steps, like an assembly line: photo in, recognized work, draft text, voice, check, out. Before writing the app, we tested the design: 49 home-screen variations, 30+ screens and 5 narration modes, described in how we prototyped Museo.

What you get when we build your guide

  • Proof you can try, not slides. Museo is live in the App Store and Google Play. Try it yourself in front of a painting: recognition in about 100 ms, narration in 20+ languages, WCAG 2.1 AA.
  • Seniors on your project, no layers in between. You talk directly to the senior engineers and designers who build your guide, with no account managers relaying messages. They are the people who took Museo from concept to a live product in about 3 months.
  • One team for the whole product. The app, the admin panel and the AI pipeline come from one team under one contract, as in Museo's 6 connected parts. Why that matters is in what handoffs between app vendors cost you.
  • Predictable cost. A fixed price per milestone, a written list of what the museum supplies and your own store accounts from day one.
  • Rated by clients. 5.0 on Clutch from 19 reviews, and Clutch 2026 awards for Top Flutter Developers Poland and Top App Development Company Poland.

Ask every team you talk to for the same things: a live app you can test in front of a real work, recognition and narration on a sample of your own works before you sign, a fixed price per milestone and a clear answer on what you keep if you leave. We show you recognition on photos of 10 of your works before you commit. What we build for museums and other organizations is on app development for companies. If your team wants to try AI tools on its own first, our free skills pack and answers from our engineers are on Build with AI.

Common questions

01What is a museum app with an AI guide?

An app on the visitor's own phone that recognizes an artwork from a photo, tells its story in the visitor's language and lets the visitor choose the depth, for example a short version, an expert version or one for kids. Buyers also call it an AI museum guide or an AI tour guide app.

02How much does a museum guide app cost?

Your own guide app built on our Museo platform starts from about $20,000, plus usage-based running costs such as store accounts and GPU time. A subscription platform is paid again every year, and handheld devices need a fleet purchase plus staff time at the desk.

03How long does it take to launch your own museum app?

About 2 months on the Museo platform, if the museum supplies collection data in week 1 and approves texts on time. Museo itself went from concept to a live product in about 3 months.

04Does artwork recognition need QR codes or hardware in the rooms?

No. The app recognizes the artwork from the visitor's photo, in about 100 ms in Museo. You photograph each work for the index, and nothing is installed on the walls.

05Is AI narration accurate enough for a museum?

With people in charge, yes for most collections. In Museo a curator approves every text, and every audio clip is checked against its script automatically. Clips that drift go to a person before visitors hear them.

06Does the guide work without internet?

Yes. Museo has an offline mode, which helps in basements, thick-walled buildings and for tourists without a local data plan.

Was this article useful?

4.8 / 5 · 11 ratings

Rate this article

Keep reading.

All posts

Let's make something together.

No overengineering. No wasted time. Just straight-up execution.

Or book a call with Eryk (opens the booking calendar)[email protected]
Who are you?
Budget