Skip to content
Curiosive
TR
Santa Fe, New Mexico · Museum visitor companions

Museum Digital Experience Development for Santa Fe Teams

A digital museum companion should connect a visitor to the exhibit in front of them without making the interface the main attraction. Curator-approved chapters, media and clear navigation can support an experience that continues at the visitor's pace. We help Santa Fe, New Mexico museum and cultural teams develop that connected web product.

Our Murder in Prague work, recorded in Czechia, pairs a physical experience with a chaptered Next.js companion, CMS-managed media and saved progress. It is a reference for digital storytelling engineering, with museum-specific interpretation and visitor requirements defined separately. Curiosive uses AI to accelerate implementation with human review and remains a long-term product partner as the experience evolves.

Start a partnershipFrom $2,000 per month
Fictional gallery exhibits linked to chaptered media and a saved-position marker on a visitor companion interface
AI-generated museum visitor concept; not a client museum, published artwork collection or Murder in Prague screenshot.
25
published case studies
5+
years building for production
12
countries the work runs in
100%
of code read by a senior engineer
1 day
to hear back, from the engineer
Browse industry workflows →

Organize the visitor journey around approved exhibit references

Begin with a small set of exhibits and the story the curatorial team wants each chapter to tell. Decide whether visitors follow an order or choose chapters independently, and what identifies the intended exhibit in the interface. Model text, audio and other media together so an editor can understand what belongs to one chapter. Agree who approves interpretation and rights for publication. A focused pilot can make these relationships reviewable before expanding the experience across a larger collection.

Relevant work: Murder in Prague's chaptered companion

The published Murder in Prague case describes a Shopify storefront for a physical detective kit and a Next.js and TypeScript companion on a subdomain. The application presents chapters of video interviews, phone calls and text messages. Sanity manages game content, while Supabase supports accounts and saved progress. A mobile-only step continues part of the experience on a phone. The project is recorded in Czechia. Its connected physical and digital storytelling provides engineering evidence; a museum companion would have a separately agreed visitor and editorial model.

Let the visitor pause without losing the intended chapter

Agree what a return point means: a chapter, a media position or another defined step. Decide whether it belongs to an account or another approved visitor access model. Make it easy to return to the exhibit list and distinguish an unopened chapter from the current one. Review unavailable media and interrupted playback alongside the ideal journey. Define text alternatives and supported interactions with the team before implementation so the experience can be reviewed across the intended devices and visitor needs.

Plan exhibit changes alongside saved visitor context

A chapter can be reordered, its interpretation revised or its exhibit removed. Decide which reference stays stable and what appears when a visitor returns to older content. A content owner should be able to understand the effect of publication before the update reaches the companion. AI accelerates interface exploration and familiar integration work; engineers review media behavior, saved-state relationships and recovery. Curatorial teams approve the interpretation and assets, while the development scope defines how those approved materials behave in the product.

Review one visitor chapter and its return point after a content change

For a new engagement, bring approved exhibit references, representative media and the intended visitor access model. Proposed acceptance examples: a chapter opens the matching media; a visitor can use the agreed alternative to audio; returning restores the intended position; and a retired exhibit follows the approved replacement rule. Include unavailable media and a reordered chapter. These are proposed visitor-software checks, not claims about Murder in Prague's museum delivery, accessibility certification or exhibit interpretation.

A product partner across the next exhibition

Visitor questions and curatorial updates reveal where chapter context, navigation or media presentation needs improvement. We work through a shared backlog and reviewed releases so those findings shape the next version. Monthly AI-accelerated development starts from $2,000, with capacity, content responsibilities and supported devices agreed in writing. Curiosive LLC collaborates remotely with Santa Fe teams through agreed Mountain-time review windows, with engineering led from Ankara. The partnership continues beyond the first digital exhibition launch.

Delivered work in detail

Murder in Prague: a Shopify storefront and a Next.js game app

A Shopify storefront that sells a physical detective kit, paired with a Next.js companion app where buyers play a chaptered murder mystery with saved progress.

Read the case study →
AI-accelerated development
from$2,000
per month

Senior engineers building your product with AI coding agents: web, mobile, SaaS or browser extension, reviewed before anything ships.

  • Web, mobile, SaaS and browser extensions
  • AI-assisted delivery under senior engineer review
  • Scope and capacity agreed in writing, renews monthly

AI-accelerated development, billed monthly. We confirm scope, capacity and start date in writing before checkout.

Questions

The things people ask before starting.

Can you build a museum digital companion for a Santa Fe team?

Yes. Bring approved exhibit references, representative media and your intended visitor journey so we can scope a focused chaptered experience.

How is Murder in Prague relevant to a museum companion?

Its Czechia-recorded case demonstrates a physical experience connected to CMS-managed digital chapters and saved progress. Museum interpretation and access would be new requirements.

Can visitors return to their previous chapter?

That can be scoped with an agreed access model and definition of saved position. We would also define what happens when the chapter changes or is retired.

Can you develop the experience for future exhibitions?

Yes. A continuing engagement can prioritize visitor feedback, approved content changes and new chapter journeys through a shared backlog and reviewed releases.

Related pages

Solutions
Services

Website Development with Next.js and Sanity

Technologies

Next.js product and web development

Services

Full Stack Development for Web Products and SaaS

How it starts

What happens after you write to us.

  1. 01

    You describe the product

    One paragraph on what you are building, roughly when you need it, and who it is for. No brief, no form with fifteen fields.

  2. 02

    You get a reply within a day

    From the engineer who would do the work, not a sales team. If we are not the right fit we say so, and where possible we point you somewhere better.

  3. 03

    You get a scoped plan

    Scope, price and timeline in writing before anything is committed. You decide with the numbers in front of you.

No long contract to begin, no lock-in to our tooling, and the code is yours from the first commit.

Start a conversation
Contact

Looking for an engineering partner for the long haul?

A short note about the product, the timeline and who it is for is enough to start. You will hear back from the engineer who would do the work, not a sales team.

hello@curiosive.comSee what we have shipped

Ankara / Türkiye · Working across European and US time zones