Home / Case studies / A public science venue in a special administrative region

Public venues / multimedia interaction

Public Science Venue in a Special Administrative Region

Five interactive experience systems covering food, meteorology, epidemic prevention, school and transport.

Background

A public science venue whose visitors are mainly families and school groups, with a wide age range and short attention spans.

The difficulty with these venues is this: content must be understood at a glance, operation must be learned in one step, and knowledge points still have to stick. Plain display boards get ignored, and screens alone are no different from a phone.

The venue also required unified delivery across themes, so that each theme is not sourced from a separate supplier and operations do not fragment later.

Solution

Delivered five custom interactive experience systems: food safety interactive education, a lightning-safety sandbox, a campus safety sandbox, epidemic prevention and school bus safety.

Every system separates the control terminal from the display terminal: staff control it from a tablet while the large screen displays, preventing visitors from operating it by mistake.

Interaction format is chosen by theme: touch-screen quizzes for food safety, sandbox projection for lightning safety, a hazard-hunt game for campus safety, process simulation for epidemic prevention, and an immersive scenario for school bus safety.

The five systems connect to a unified central control back end, which can switch them on and off, monitor their status and export visitor data.

Technical composition

The table below lists this project's technical elements so clients can verify them independently.

Tech stack

Number of Systems5 sets, each with its own theme
ArchitectureControl / display separation
Interaction formatTouch quizzes · sandbox projection · hazard inspection · process walkthroughs · immersive scenes
Central controlUnified backend with centralized switching and monitoring
DataVisitor records and interaction data can be exported
MaintenanceEach system can restart independently without affecting the others

Outcomes

  • All five themes are delivered by one supplier, with consistent interfaces and maintenance standards.
  • Control is separated from display so staff can intervene at any time and the venue never runs out of control.
  • Visitor data can be exported to support operational analysis and reporting to superiors.
  • A failure in one system does not affect the whole, markedly improving availability.

Capabilities Used

Discuss a similar scenario

01 / Constraints

The constraints the project was built under

Project stories without constraints are fiction. This section sets out four constraints: time, site, staffing and compliance.

These constraints directly shape the solution; every problem under 'Key challenges' below is forced out by one of them.

Four kinds of constraint

VenueThe venue is a converted existing building: five themed zones spread over different floors, with irregular areas and shapes.
AudienceOpen to the public, with visitors ranging from preschoolers to the elderly, so one set of interactive content has to work for everyone.
MaintenanceVenues have no dedicated IT staff, so equipment problems must be diagnosable remotely or handled by security staff.
BudgetThe five systems share one central-control and maintenance framework; each cannot have its own back office.
02 / Key challenges

Where It Actually Gets Stuck

It is not “we worked hard”; it is “what the problem looked like, how we solved it, and what it cost”.

How one set of content can work for a 5-year-old and a 70-year-old

The first version was designed from an adult perspective: small type, deep hierarchy, instructions to read. In trial operation, elderly visitors could not see it and children could not reach it.
How we solved it: moved to 'zero-text guidance' — all actions are signalled by icons and motion, key buttons are enlarged beyond 60px, and interaction is compressed to two levels at most. Written explanations drop back to a second layer that appears only on tap.

How five systems share one central control

The five themed zones originally came from five separate suppliers, each with its own back office; venue staff had to open five browser tabs just to do a walkthrough.
How we solved it: unified central control — power on/off, content switching and fault reporting for five systems were abstracted into one set of interfaces, and the controller calls only those, not caring about internals. It took coordination with each vendor, but now one guard can patrol the whole venue.

What if there is no network

Public WiFi in the venue is unstable and visitors' mobile interactions frequently drop.
How we solved it: localised all interactive content — no external CDN, fonts or scripts. Everything sits on the local server, so with the network down all functions work normally except sharing.
03 / Reusable elements

What other projects can borrow directly

This section is for peers. If you are doing something similar, these points will save you a few detours.

Text-free guidance

For public exhibits, text instructions should be optional, not mandatory.

Unified Central Control Abstraction Layer

In multi-vendor projects, agree a unified interface in the contract, or coordination costs later will be extremely high.

Fully localised resources

Venue projects must assume the network is unreliable.

04 / Retrospective

If we did it again

Talking only about successes is unconvincing. This section covers what we got wrong or did too late.

Doing it again, we would put a unified control interface into the tender requirements instead of coordinating after all five systems were installed. That mistake cost an extra month.

We did not give enough thought to older visitors. Accessibility is not just a large-font mode; it also covers interaction habits, reaction time and contrast. The next version will include dedicated age-friendly testing.

The workload of content updates was underestimated. The popular-science content for five themes has to track policy and scientific progress every year, and there is no ongoing staffing for it — a latent risk.

← All case studies Back to home