Sanitised project evidence · Family task and rewards platform
Little Questers
Children receive a clearer path to participate while parents retain oversight of missions, approvals and rewards.
Context
For whom
Designed for families that want household responsibilities to be easier for children to understand and easier for parents to coordinate.
- Child-friendly missions and progress
- Parent control over approvals, points and rewards
- Individual progress without comparing children
The starting point
Why it was needed
Repeated reminders and separate task or reward tracking made participation harder to sustain and parent follow-up harder to manage.
- Children could lose sight of what to do next
- Parents needed a reliable approval step
- Tasks, points, rewards and longer-term goals were disconnected
What changed
The solution
Eleva turned household responsibilities into a guided family workflow designed differently for children and parents.
- Missions with clear completion actions
- XP, points, levels and individual progress
- Rewards and savings goals
- Parent approval and management views
- English and Spanish experiences
Workflow comparison
Before and after
Before
- Parents repeated reminders and tracked outcomes separately.
- Children had limited visibility of progress and rewards.
- Approval and reward decisions depended on informal follow-up.
After
- Children see current missions and personal progress.
- Parents review completions before points are awarded.
- Rewards and goals connect participation to a visible outcome.
Evidence in context
Project walkthrough
01 · Family adventure overview
The public preview introduces the child-friendly mission loop and the separate parent role without showing family records.
02 · Mission board concept
Missions, habits and a longer-term goal are visible together so the next action and its purpose are easy to understand.
03 · For parents and children
The two audiences receive different responsibilities: parents configure and approve while children complete and progress.
04 · Completion and approval loop
The public walkthrough makes the control point explicit: parents confirm effort before rewards are redeemed.
Fit before fashion
Technology and why
Next.js
- Requirement
- Distinct child and parent experiences within one product
- Why it fit
- The App Router supports separate dashboard and administration areas with server-side workflow actions.
- Resulting benefit
- Each role receives a focused interface while sharing one maintained application.
Supabase
- Requirement
- Family-owned missions, approvals, rewards and progress
- Why it fit
- PostgreSQL relationships, authentication and row-level controls match the family ownership model.
- Resulting benefit
- Family records and parent actions remain within the authorised household.
TypeScript
- Requirement
- Reliable mission, point, approval and reward contracts
- Why it fit
- Typed models keep child-facing state and parent-side decisions consistent.
- Resulting benefit
- Workflow changes are easier to review without silently changing reward rules.
next-intl
- Requirement
- Equivalent English and Spanish family experiences
- Why it fit
- Shared route-aware messages keep both languages aligned across child and parent views.
- Resulting benefit
- Families can use the same workflow in their preferred language.
Framer Motion
- Requirement
- Clear, encouraging feedback for child actions
- Why it fit
- Purposeful motion can reinforce progress while respecting reduced-motion preferences.
- Resulting benefit
- Completion feedback feels responsive without changing the underlying rules.
Sanitised project evidence
Security and privacy
These images come from the synthetic public preview. No real child, family or account information is published.
- Family ownership checks on records
- Separate parent administration access
- Server-side guards around protected actions
- Synthetic public screenshots
Outcome
Clearer participation with parent oversight
The platform gives children an understandable participation loop while keeping approvals and family controls with parents.
- Visible next actions for children
- Controlled completion approval
- Connected points, rewards and goals
A similar process?
Start with the work that needs to become clearer
If Little Questers reflects a workflow your team is managing through spreadsheets, email or repeated follow-up, describe the process. No technical brief is required.
Talk through your process