Education & Family Tech

Mcookie

Turns daily chores into a reward game that works for parents and kids.

Mcookie turns the weekly chore argument into a game. Parents set the tasks and pick the rewards, kids choose a hero character, finish their tasks, earn cookies and level up, then spend those cookies in an in-app shop on rewards a parent has approved. A six-letter family code keeps every household private, so no child ever fills out a sign-up form. We built the mobile apps on React Native, with Swift and Kotlin for the native parts, and a Laravel backend handles tasks, approvals, cookie balances and the shop.

Mcookie task list home screen
Mcookie family shop screen
12Hero characters
6Letter family code
2Native platforms
How it works

Three steps every family follows

It is one loop, from the first chore to the first reward. Parents set, kids earn, the shop delivers.

01

Parent assigns a task

A parent sets a chore from their phone in under ten seconds and picks a cookie reward for it. The whole point is that adding a task is quick enough to actually do in the middle of a busy day.

02

Kid ticks it off

The kid taps done, cookies drop into their balance, and their hero character levels up. The reward is immediate and visible, which is what makes a child want to do the next one.

03

Kid redeems from the shop

The kid picks a reward the parent has added, the parent approves it, and the item unlocks. The loop closes from doing the chore to getting something real for it, which is the whole deal Mcookie makes with a family.

Two roles, one app

Built for parents and kids at the same time

Each role sees the screens that fit their age and their goal, but everything runs on the same family account.

For parents

  • Create and manage the family account
  • Assign tasks and set cookie rewards
  • Approve tasks and hand out bonus cookies
  • Curate the reward shop and set cookie prices

For kids

  • Join the family with a six-letter code
  • Pick a hero character and level them up
  • Tick off today's tasks and watch cookies pile up
  • Claim rewards from the shop
Built With

One shared UI, two native shells, one Laravel backend

React Native ships the shared UI to both iOS and Android, while Swift and Kotlin handle the parts that need real native behaviour, such as push notifications and the small animation details kids notice. A Laravel backend on AWS manages tasks, approvals, cookie balances, hero levels and the reward shop. It is a pragmatic mix: shared code where it saves time, native code exactly where it matters.

Mobile
React NativeSwiftKotlin
Backend
LaravelMySQL
Cloud & Hosting
AWS
The tough parts

And how we shipped them

Five problems the app had to solve cleanly before it felt right for families. Each challenge is paired with what we actually did.

01

Parents add tasks, approve them and curate the shop, while kids pick a hero, see their tasks, tick them off and claim rewards. The app had to feel right for a busy adult and a six-year-old at the same time, which are very different users to please.

02

A family had to stay private, and most kids do not have email, so the usual sign-up flow was out. The invite flow needed to let a parent bring children in without any of them creating an account or handing over personal details.

03

Rewards had to feel real rather than generic. Some parents buy toys as rewards, like a video game or a building set, while others offer experiences, like extra screen time or the pick of the Saturday film. The system had to handle both kinds through the same shop flow.

04

The claim flow had to feel instant. A kid taps claim, the parent gets a push notification, the parent approves, the cookies move out of the balance, and the item lands on the kid's shelf. If any of those steps lag, the small bit of magic is gone.

05

Kids needed a reason to come back every day. A cookie counter is fun for the first week, but something more was needed to keep a child engaged into the second month, when novelty alone wears off.

How we shipped it

What we actually did

Every challenge above gets a direct answer below. Same order, same focus.

01

We watched real families use chore charts before designing a single screen. Parents wanted to add a task from a phone in under ten seconds, and kids wanted bold visuals and a cookie counter they could see fill up. That research shaped the role split, the colours and the motion, so each side of the app fits the person using it.

02

A six-letter family code keeps setup fast. A parent creates a family, shares the code, and each child joins in under a minute, with no email for the child and no extra account. Only the parent who owns the code can add or remove members, so every permission sits in one trusted place.

03

The reward shop runs on a flexible item model. A parent can add anything, a toy, an outing, a screen-time ticket, a game, and set a cookie price for it, and the same engine handles physical products and one-off experiences alike. That flexibility is what lets each family make the rewards mean something to their own kids.

04

We used native push notifications and a backend tuned for this exact loop, built with React Native app development and backend development, so the claim, the approval and the reward all happen quickly and in order. Keeping that flow snappy is what makes the reward feel earned and immediate rather than like filing a request.

05

Hero characters turn daily tasks into a long game. Kids pick from twelve heroes, and finishing tasks levels their hero up, while the level, balance, and earned-and-spent stats on the profile screen turn effort into visible progress. That sense of a character growing is what keeps a child coming back well past the first week.

A look around

Every screen on brand

The same visual system runs from the first tap to the reward shelf: hero selection, the task list, the family shop and the profile with levels and stats all share one consistent, kid-friendly look. Consistency here is not just polish, it is what makes the app feel trustworthy to a parent and fun to a child at the same time.

Mcookie hero selection
Pick a hero
Mcookie task list
Tasks
Mcookie family shop
Shop
Mcookie profile stats
Level & stats
FAQ

Frequently Asked Questions

Common questions founders ask before building a family, kids or chore app. Costs, tech, design, safety, timelines and what actually keeps kids coming back.

It depends on scope, but as a guide, a family or kids app like Mcookie in the Netherlands typically runs from around EUR 20,000 to EUR 50,000 or more, depending on the gamification, the reward shop and whether parts are built natively. We give a fixed estimate after a short discovery call rather than quoting blind.

A strong approach is React Native for the shared UI, which ships most of the code to both platforms at once, combined with Swift and Kotlin for native parts like push notifications and animation details, and a backend such as Laravel on AWS. We used exactly this for Mcookie because it balances shared code with native feel where it matters.

By treating them as two genuinely different users on one account. We research how real families behave, then split the experience so parents get fast, practical task and approval screens while kids get bold visuals and instant rewards. Everything runs on the same family account, but each role only sees what fits their age and goal.

They turn effort into visible, immediate progress. In Mcookie, finishing a task drops cookies into a balance and levels up a chosen hero character, and cookies are spent in a parent-curated shop. A flexible reward model handles both physical items and experiences, and the hero progression is what keeps children engaged beyond the first week.

By collecting as little as possible and keeping parents in control. Mcookie uses a six-letter family code so children join without email or accounts, a parent approves and manages every member, and only the data the app genuinely needs is stored. Designing privacy in from the start is how a kids app stays compliant and trustworthy.

A cross-platform family app like Mcookie typically takes around four to six months from concept to launch, including research, design, build and testing with real families. We work in two-week sprints with working software throughout, so progress is visible rather than going quiet until launch.

Usually through subscriptions for premium features, family plans, or optional in-app purchases, rather than ads, which sit poorly in a kids app. The right model depends on the audience, and we help choose one that fits how families actually use the app rather than forcing a model that undermines trust.

Through progression, not novelty. A counter is fun briefly, but a character that levels up, visible stats, and rewards that feel real give a child a reason to return for months. In Mcookie the twelve hero characters and the profile stats turn daily chores into a long game, which is what sustains engagement well past the first week.

Start your project

Thinking about a family or kids app?

We build apps that work for both kids and the adults around them, native on iOS and Android, with React Native or a mix, backed by servers that handle real families without breaking. If you are planning something like Mcookie, tell us what you have in mind and a senior engineer will reply within one business day with an honest view of what it would take.