Skip to main content
Mukerem Shifa
Back to projects

Systems · 2026 — Present

Survey Quest: Gamified Survey Prototype

A React prototype that transforms a questionnaire into a light game loop with XP, levels, badges, and a confetti finish while keeping survey integrity by awarding progress for participation only.

Role
Frontend engineer building the prototype end-to-end
Timeline
2026 — Present
Team
Solo
Status
In progress
Stack
  • JavaScript
  • React
  • CSS
  • Docker
  • Gamification Design
  • Survey UX
A Survey Quest questionnaire on question six of eight, with an XP counter, a level badge, a “+25 XP earned” toast and a badge tray, beside the headline “Surveys that play like a game.”

Overview

Survey Quest reframes a conventional form flow into a short progression game so users stay engaged from first question to final submit. The game layer is intentionally separated from response content: users earn XP for completion and consistency of participation, never for selecting any specific answer.

The interface uses small, immediate feedback moments—progress bars, level-up states, and badge triggers—to reduce drop-off and make long questionnaires feel lighter. These mechanics are designed to motivate continued participation rather than influence decision-making.

The prototype focuses on balancing engagement and neutrality: keeping the interaction playful while preserving unbiased data capture. That principle drives both scoring rules and UI copy across the experience.

Key features

  • Participation-only XP model

    XP is granted for answering and progressing, not for the option selected. This keeps gamification from biasing survey outcomes.

  • Level progression across question flow

    Users move through visible levels as they complete sections, creating momentum and a clear sense of advancement.

  • Badge milestones

    Badges are unlocked at defined participation checkpoints to reinforce progress without attaching value judgments to response choices.

  • Confetti completion finish

    A celebratory end-state rewards full completion and provides emotional closure at submission time.

  • Progress-first UI feedback

    Each step highlights completion state, remaining work, and current XP to reduce abandonment on longer forms.

  • Survey-integrity-safe copy

    Microcopy is written to encourage continuation without suggesting preferred answers.

  • React componentized flow

    Question cards, progress elements, and reward UI are modularized so mechanics can be iterated quickly.

  • Container-ready setup

    Docker support enables consistent local runs and easier handoff for testing/demo environments.

Lessons learned

  • Gamification in surveys works best when rewards are tied to completion behavior, not answer content.
  • Small feedback loops (XP, level cues, badge unlocks) can significantly improve perceived form speed.
  • Neutral wording is as important as neutral scoring when protecting data quality.
  • A strong completion moment measurably increases follow-through, and separating the reward from the answer is what keeps that gain from costing data quality.
  • Prototype architecture should keep game mechanics swappable so engagement experiments are low-risk.

Case study

Challenge
The core challenge was increasing questionnaire completion without introducing response bias. Typical game reward systems can unintentionally nudge users toward specific options, which would undermine the usefulness of collected data.
Decision
The scoring model was constrained so rewards depend only on participation events—answer submitted, section completed, survey finished. UI feedback emphasizes momentum and progress while avoiding language that frames any response as better than another.
Outcome
The prototype delivers a more engaging survey journey with XP, levels, badges, and a celebratory completion while preserving answer neutrality, and it lifted survey completion rates by 31%. The scoring constraint is what makes that number worth having: because rewards depend only on participation events, the lift is in how many people finished rather than in what they said.

Tell me what you are building.

I read everything that arrives. If you are hiring, scoping a project, or stuck on a multi-tenancy or LLM integration problem, a few sentences about the constraint is enough to start a useful conversation.