Kari and the Lost Shrines

01 The Call

Chose to build Kari as a full game — with 3D environments, puzzle mechanics, and a narrative progression system — rather than the lighter-weight formats Isha Foundation could have commissioned: a documentary-style app, a virtual tour, or a video content series. The "game" decision was the founding product call. It meant accepting Unity's complexity, a multi-discipline production pipeline (concept art → 3D modeling → game logic → mobile optimisation), and the longer timeline that entails. The alternative formats were safer and cheaper; a game was the only format that could create genuine player agency — letting someone physically explore a temple, solve puzzles rooted in its history, and collect relics that unlock deeper lore. Cultural education had to be woven into gameplay, not bolted on.

02 The Bet

Bet on Unity as the engine and mobile-first as the primary canvas — two decisions that locked the entire technical architecture. Unity's single-codebase cross-platform target (iOS + Android) was the right call for reach, but it required committing to C# as the sole scripting language and to mobile GPU constraints as the design ceiling. The temple-collection mechanic — relic hunting as the core loop — was the gameplay bet: that a collect-to-unlock progression would sustain engagement long enough for the cultural content to land. Each temple had to be its own self-contained world with unique puzzles, environment art, and historical beats, which multiplied the production effort per level but made the game replayable rather than linear.

03 The Trade-off

The depth-per-temple model traded breadth for quality — fewer temples, each richly detailed, rather than many shallow environments. This also kept the initial download size manageable through addressable asset loading. The model was free-to-play with no in-app purchases, which traded monetisation upside for frictionless reach — consistent with Isha Foundation's non-profit mandate. Cultural sensitivity was a hard constraint throughout: every architectural choice, every puzzle, and every piece of narrative had to be reviewed against the authentic heritage of the temple it represented. That constraint slowed iteration but protected the product's integrity in the eyes of Isha Foundation's global community.

04 The Outcome

50,000+ downloads across iOS and Android, 4.5+ rating on both stores — organic growth driven by Isha Foundation's volunteer network and community channels rather than paid acquisition. The App Store listing (id1561474376) remains live. The 4.5+ rating across both stores reflects sustained player satisfaction beyond the initial community push, which means the gameplay loop held up for players outside Isha Foundation's existing audience. Device testing was conducted across 50+ Android devices and multiple iPhone generations to ensure the mobile performance held at scale.

05 Coordinated

Worked directly with Isha Foundation stakeholders to align on cultural representation, narrative direction, and launch sequencing. The production pipeline required coordinating across art (concept art and 3D temple environments), audio (ambient and puzzle-state sound design), and game design disciplines — all feeding into Unity for integration. The community launch phase was coordinated with Isha Foundation's volunteer network and social channels, which was the primary acquisition channel. Isha Foundation's global community provided both the distribution surface and the cultural authority that gave the game its credibility.

06 Where this goes next

The natural roadmap is additional temples: India has thousands of architecturally and historically distinct sacred sites, and each one is a candidate level. A multiplayer or co-op relic hunt — where two players explore the same temple from different entry points — would extend the social dimension that Isha Foundation's community naturally supports. A curator mode, where Isha Foundation volunteers can contribute cultural annotations to each level's lore layer, would turn the game into a living cultural record rather than a static product. Seasonal events tied to real temple festivals (Diwali, Mahashivratri) would drive re-engagement without requiring full new levels.