Software & Custom Solutions service

Interactive experiences that invite people into the story.

Asban combines experience design, software, motion, media, and hardware planning for museums, events, public spaces, learning, tourism, and the web.

Raccoon software engineers connecting reliable digital platforms and services.

Scope and deliverables

Interactive Experiences: scope and deliverables

A typical engagement includes experience concept, prototype and production and installation and operating package.

01 / Foundation

Experience concept

Audience, setting, story, interaction, content, accessibility, hardware, staffing, and success conditions defined.

02 / Delivery

Prototype and production

Key interactions tested early, then interface, media, software, and device integrations developed together.

03 / Handoff

Installation and operating package

Deployment, device setup, content procedures, testing, recovery, documentation, and support prepared.

Practical value

What Interactive Experiences should improve

The intended outcomes are active participation, story and technology aligned and a workable installation. Success measures are agreed around the organization's objective.

01 / People

Active participation

Visitors explore, choose, learn, or contribute instead of only receiving a presentation.

02 / Operations

Story and technology aligned

Interaction supports the message rather than becoming an isolated novelty.

03 / Leadership

A workable installation

Reset, recovery, accessibility, staffing, connectivity, and maintenance are planned.

Governance and context

Governance considerations for Interactive Experiences

Projects can define consent, cultural review, content ownership, visitor data, recording, language, accessibility, hardware access, moderation, and update authority.

Before you start

Common questions about Interactive Experiences

What can Asban build?

Scope can include touch displays, kiosks, installations, maps, data stories, learning tools, browser interactives, and presentations.

Do we choose hardware first?

Not necessarily. The experience should inform device choice, lifespan, accessibility, maintenance, and replacement.

How is it tested?

Key interactions are prototyped, then tested with representative hardware, content, users, connectivity, and recovery scenarios.