Designing for touch
The interface is designed around a kiosk rather than a traditional desktop website. Navigation, typography, spacing, horizontal timelines, and interactive areas are considered for touch interaction and fixed display environments.
A touch-first museum kiosk and content management system designed for an interactive visitor experience, with structured historical content, galleries, media management, and performance-focused delivery.
An interactive museum kiosk and CMS created for presenting Gurkha and historical content through a touch-first visitor experience.
A kiosk application has different constraints from a normal website. Visitors need immediate feedback, readable content, simple touch interactions, and reliable media delivery. At the same time, administrators need a practical CMS for managing structured historical content and media.
I worked on the public kiosk experience and the administrative CMS, with an emphasis on touch interaction, structured content, media management, and fast rendering. The architecture also considers caching because the kiosk should avoid unnecessary repeated work during visitor sessions.
The important parts of the project were not just the interface, but the systems and decisions behind it.
The interface is designed around a kiosk rather than a traditional desktop website. Navigation, typography, spacing, horizontal timelines, and interactive areas are considered for touch interaction and fixed display environments.
The CMS provides structured content that can be managed independently from the presentation layer. This allows historical pages, regiment information, galleries, and other sections to evolve without rebuilding the entire interface.
The system uses Cloudinary for media management and direct uploads, with upload constraints designed to prevent unnecessarily large assets from entering the system.
Unlike a normal website where users may visit once and leave, a museum kiosk can serve many consecutive visitors. Caching and efficient rendering therefore become part of the product experience rather than an afterthought.
Selected visual highlights from the QOGLR project.
Whether you're building something new or improving an existing system, let's talk about the problem and what it would take to build it well.
Start a conversation