Developed a Progressive Web App (PWA) for space education, listed in the published portfolio as receiving 1st Prize. Engineered a custom, performance-optimized game engine within React for the 'Space Shooter' module. Integrated a conversational AI agent powered by Dialogflow for interactive learning and implemented a rigorous reliability suite using Checkly to monitor API health and uptime.
Key metrics and achievements that define this project
Explore the live demo, check the code, or reach out to discuss it
Full Case Study
A space education build listed in the published portfolio as receiving 1st Prize, using a custom canvas game loop, an ISS tracker, Dialogflow support, and monitoring tooling to make the experience interactive without reducing it to a gimmick.
Building an educational platform that engages users through gamification while maintaining educational integrity. The space shooter game needed to run at 60 FPS on low-end devices without compromising learning outcomes.
Developed a custom game engine using HTML5 Canvas with optimized rendering loops and object pooling. Implemented progressive enhancement for PWA features and used service workers for offline capability. AI chatbot provides contextual learning assistance.
Deep-dived into game development principles, learned advanced PWA techniques including background sync and push notifications, and gained expertise in creating accessible interactive experiences.
A phase-by-phase record of how the work was scoped, built, and carried into production.
Set the product direction around making space education interactive enough to retain attention without turning the platform into a game-only experience.
The challenge statement in the project record already anchors the work around low-end device support and educational integrity.
Designed the Space Shooter module as a purpose-built rendering system inside the React application instead of relying on a heavyweight game framework.
The repository record already references a custom engine, optimized rendering loops, and object pooling as the core tradeoff for control and performance.
Integrated the educational UI, offline-ready PWA capabilities, and Dialogflow support into a single learning experience.
Service workers, progressive enhancement, and contextual AI assistance were implemented as part of the same product narrative rather than separate demos.
Tuned the gameplay path around the stated 60 FPS target on lower-end devices and kept the experience progressively enhanced where features were unsupported.
Optimization focused on the rendering loop and asset behavior rather than on cosmetic metrics that the project data does not currently substantiate.
Released the project as a complete educational PWA; the published portfolio lists a 1st Prize recognition claim.
The published portfolio lists the project as receiving 1st Prize; no independently linked verification source is provided here.
Key Decisions
A compact snapshot of the technical and product decisions that had the biggest impact on delivery.
The game experience needed direct control over rendering and update cadence, but the rest of the product still lived inside a standard web application.
I built the Space Shooter around a custom canvas game loop so the most interactive feature stayed tightly scoped and performance-aware.
Impact: The game became a differentiating module without forcing the entire product into a game-engine-first architecture.
Tradeoff: A custom loop gives more control, but it also means owning more of the gameplay architecture directly.
Visual Showcase
This screen captures the production-facing design language, layout rhythm, and overall polish of the experience.
Scroll to explore technologies →
A static space site is less compelling when users can reasonably expect real-world context such as ISS tracking.
I added an ISS tracker flow that polls an internal API and computes user distance in the interface layer.
Impact: The site feels closer to a living learning product than a static educational brochure.
Tradeoff: Polling adds moving parts and requires discipline around update cadence.
Interactive APIs and chatbot flows degrade trust quickly if they fail silently.
I included Checkly-based monitoring so the product had a reliability posture beyond basic deployment success.
Impact: The project demonstrates product stewardship, not just feature implementation.
Tradeoff: This added operational setup to what could have remained a purely feature-focused project.
