WonderQuest
WonderQuest home

BUILT WITH CURIOSITY, TOO

From a small idea
to a shared adventure.

The making of WonderQuest: a learning project that grew into native iOS and Android experiences, with content and families at its centre.

Start with the learning idea

WonderQuest began as a personal educational project by Anupam Saha: use some screen time to introduce children to ideas beyond their textbooks. The first product question was how to make a small learning interaction feel like discovery rather than another piece of homework.

Early prototypes explored the Discover / Think / Answer loop. As the idea grew, the work expanded from presenting questions to building a connected experience around content, explanations, progress and family involvement.

Build the adventure in layers

  1. Content before complexity

    Develop a curated question bank and review questions, correct answers and explanations. Content quality gives every later feature something dependable to build on.

  2. Themes and challenges

    Organise topics into learning themes, then connect Micro-Quests, Missions and Boss challenges. Different activities move from recognition towards using and connecting ideas.

  3. A reward economy

    Add XP, Coins, Explorer Legacy, Daily Challenges, Power Ups and Accessories. Balance a playful sense of progress with the purpose of the learning activity.

  4. A family experience

    Bring Explorer profiles, parent controls and progress views together. Parents need a clear view without having to supervise every answer.

  5. Two native app experiences

    Build the iOS experience in Swift and SwiftUI, then extend the shared learning vision to Android with Kotlin and Jetpack Compose.

  6. Review and refine

    Continue testing content, voice interactions, progression, rewards and consistency across platforms. Development progress is not the same as a confirmed public release.

Different devices, a shared foundation

Swift + SwiftUI on iOS

The Apple app uses native interface tools so navigation, speech and audio features can fit the device experience.

Kotlin + Jetpack Compose on Android

The Android app has its own native interface, following the same underlying learning and progression model.

Supabase behind the apps

A shared backend supports authentication, stored learning information and server-side decisions. It helps the apps work from a consistent foundation.

Cloudflare for the website

The project website uses lightweight static pages. Visitors can read the story and policies without an app account or a large web framework.

Explanations, privacy and careful boundaries

AI-assisted educational explanations can enrich a learning moment. In the current architecture, a controlled server function can send educational context to OpenAI. The curated question bank remains the foundation for questions and correct answers; generated explanations are supplementary and may contain errors.

Child-focused design also shapes account controls and information handling. Parent-managed profiles, restricted access and the absence of public child profiles or open messaging are part of that approach. The Privacy Policy documents the actual practices and choices.

The next iteration starts with a question

The future vision includes richer learning worlds, thoughtful adaptive support and deeper family insights. These are directions for the project rather than a promised release schedule. Feedback about unclear explanations, difficult interactions or an idea worth exploring helps identify the next piece of work.

Visit the iOS and Android section for store-link status, or share feedback about the site or apps. Official download links will be added when verified; no public launch date is claimed here.