An offline exhibit should open with its required content available after a device restart and with the network disconnected. Agree on the target hardware, browser, content package, startup procedure, and recovery steps before building the visual experience. A web page that happened to load once online does not establish that behavior.
Write the device and venue brief
Record the screen model, resolution, orientation, computer, operating system, browser, and touch input. Confirm whether speakers, headphones, a physical keyboard, or a separate operator display are part of the installation.
Ask the venue or AV integrator who starts the device, who can change its settings, and who receives an error report. Agree how updates will be transferred if the device remains offline.
These details let a content team test a defined setup. A screenshot at the same resolution cannot establish touch accuracy, graphics performance, or behavior after the device wakes.
Make the visitor's first action clear
Give a new visitor something understandable to look at before they act. Use a small set of visible controls and provide a clear route back to the start. Important explanations should be available without requiring a precise gesture or relying on sound alone.
For longer content, consider reading distance, text size, seated access, captions, and an alternative way to reach information that depends on dragging. Review the installation's accessibility needs with the exhibition team. W3C's page structure guidance is a useful foundation for the browser content; the physical installation needs its own review.
Package everything the experience needs
List images, fonts, audio, video, data, and any libraries required at runtime. Decide how the application is launched locally and which browser capabilities it depends on. An external font or a hidden data request can make an apparently complete package depend on the venue's connection.
If the content uses dated data, show the relevant date and explain the update process. Keep source information with the delivered package so future editors know what can be changed and which rights apply.
Agree on acceptance checks
| Check on the target setup | What to record |
|---|---|
| Start after a full reboot with the network disconnected | Launch steps, missing assets, and any external requests |
| Complete a visitor task using touch | Unreachable controls, accidental gestures, and reading problems |
| Leave midway and start a new visit | The agreed reset behavior and whether stale selections remain |
| Use the agreed busiest scene | Responsiveness and any overheating or resource issues observed |
| Close and reopen the application | Whether it returns to a usable starting state |
| Install a content update | The update steps and how to restore the prior package |
Choose the duration of a continuous run with the venue and record the actual result. Keep the tested device and software versions beside it. Include the results in the handover.
Divide delivery responsibilities
Ask for the application package, source and content files, licenses, launch instructions, update procedure, and support contact. Identify who supplies and installs the hardware, configures kiosk access, and checks the completed installation on site.
LifeVen designs and builds interactive content and can work with an exhibition designer or agency. The partner or AV integrator handles hardware and installation; we agree on device testing and remote installation support as part of the project.
For an early brief, send the theme, target device, venue conditions, available assets, and the one thing a visitor should understand. If the format is still open, compare an interactive experience with a video first.