Space Explorer

The planetarium wanted exhibits that would:

• Be engaging for children, encouraging self-learning.

• Use cutting-edge technology — specifically gesture-based interaction.

• Complement school curricula on space and astronomy.

• Seamlessly integrate within the museum's physical space.

Key design questions

• Gesture intuitiveness How do we make gesture interactions intuitive for all age groups?

• Education vs entertainment How do we balance education and entertainment in the gameplay?

• Museum constraints What space constraints and visitor behaviours must be considered in a museum setting?

Key observations from visitor research

• Children are drawn to interactive exhibits like 'Did You Know?' and 'History of the Universe'.

• Text-heavy exhibits are largely ignored by younger visitors.

• Tangible interaction elements — buttons, sliders, quizzes, hands-on activities — significantly increase engagement.

• Broken or non-functional installations frustrate users and damage trust.

• Multiplayer and competitive elements increase engagement considerably.

Prototype 1 objectives

• Game engine selection Selecting the right engine for both this and future prototypes.

• Basic gesture definition Defining core gestures: moving forward, turning left, and turning right.

• Gesture mapping validation Ensuring accurate gesture tracking and mapping physical movements to digital controls.

After evaluating multiple options, Microsoft XNA Game Studio was chosen due to:

• Compatibility with Windows XP and later versions.

• Customisability through scripting and C# support.

• Seamless integration with Microsoft Kinect SDK, enabling precise gesture tracking.

• Kinect's depth sensor, RGB camera, and multi-array microphone enabled full-body tracking — making it ideal for gesture-based gaming.

• It could track up to six players and provide real-time motion recognition.

Prototype 1 — key findings

• Gesture tracking worked But movement felt rigid and unnatural — lacked fluid spaceship control.

• Latency issues Early testing revealed latency in gesture recognition — required refinements in sensitivity and tracking range.

• Age-specific challenges Younger children struggled with wide-arm gestures — adjustments in movement detection were needed.

Key changes in Prototype 2

• Expanded gesture controls for better spaceship movement.

• Transitioned from XNA to Unity 3D for better asset management and visualisation.

• Refined motion tracking for more realistic 3D space navigation.

Game world components

• Objects Sun, planets, spaceship, asteroids, space fog, background sky — each with defined properties.

• Attributes Each object had properties (e.g., the Sun was stationary and a light source; planets moved in fixed orbits).

• Internal Relationships Defined how objects interacted — the spaceship collides with planets if too close; asteroids create obstacles.

• Environment 3D space setting with starfield, nebulae, and galaxies — the Sun providing dynamic lighting across the scene.

Prototype 2 — findings and next steps

• Achievement Realistic spaceship movement achieved with new gesture mappings.

• Achievement Solar system simulation nearly complete — asteroid belt addition pending.

• Gap Players felt directionless in 3D space — mini-map feature needed.

• Gap Some gestures weren't intuitive for younger children.

• Gap No UI system for statistics — speed, time remaining, next target.

• Home Screen & Training Mode Users could now select Start (play the game) or Train (learn spaceship controls) — reducing onboarding friction.

• HUD — Heads-Up Display Real-time information: time remaining, speed gauge, next destination — all surfaced without cluttering the 3D view.

• Mission-Based Navigation Players followed diamond blips near planets to reach target destinations — solving the 'directionless' problem from Prototype 2.

• End Conditions Game ended when time ran out, spaceship was destroyed, or all objectives were completed.

• Bitshumishi Primary typeface — used for all game titles, menus, and body text throughout the interface.

• 7-Segment Secondary typeface — used exclusively for numeric in-game values: speed gauge, countdown timer, and distance.

• Colour Scheme Shifted from orange/yellow to blue — a colour analysis of sci-fi games and films confirmed blue as the dominant, authentic sci-fi palette.

Key findings from user testing

• Gesture learning Kids quickly learned and performed gestures — especially after observing others playing first.

• Engagement The realistic simulation and interactive elements kept kids engaged throughout the session.

• Educational value Kids remembered planet names and facts after playing — confirming the edutainment model worked.

• Mini-map underutilised Kids relied more on planet labels for navigation than the mini-map — layout needed rethinking.

Testing nuances

• Age differences Younger kids (7–9) struggled with the pitching gesture — requiring additional practice and simplified controls.

• Group dynamics Kids often collaborated, guiding each other through the game — highlighting the importance of multiplayer support in future iterations.

• Technical issues Some users experienced lag during peak usage — prompting performance optimisation work.

Design highlights

• Educational alignment Game content carefully curated to align with school curricula — ensuring relevance for teachers and parents.

• Accessibility Gestures designed to be inclusive, accommodating children of different physical abilities and age groups.

• Scalability Designed to run on low-cost hardware — making it accessible to other museums and educational institutions beyond Nehru Planetarium.

Lessons learned

• Simplicity is key Intuitive gestures and clear objectives are crucial for engaging young users — overcomplicated controls create barriers, not experiences.

• Balance education and fun Edutainment works best when learning is seamlessly integrated into gameplay — the moment education feels like a lesson, kids disengage.

• Iterate and test relentlessly Each of the three prototypes revealed something the previous one could not — user feedback is irreplaceable for refining interaction design.