Skip to content
MobileEdTech

A meals app for parents at 120+ schools.

A mobile app for parents from HappyBee, FeelEat’s sister company. Parents browse the weekly menu, check nutrition details and see what each child ate during the school week.

84%Parent activation
−71%Allergen queries
120+Schools onboarded
HappyBee
ClientHappyBee (sister company of FeelEat)
IndustryEdTech · FoodTech
PlatformiOS · Android
DisciplinesMobile · Design · Platform
The brief

Parents wanted to know what their child ate.

ClientHappyBee · sister company of FeelEat
Reach120+ schools
Activation84% of parents
SurfacesiOS · Android

Most parents got a menu PDF in September and then heard nothing more about school lunch. HappyBee wanted them to see what each child eats, with the nutrition details, in an app they would keep opening.

We designed it for a quick look at the school gate. The app reads the same kitchen data FeelEat uses for production, so parents see what was really cooked.

The app does only a few things, and parents use it: 84% activated their accounts, and allergen questions to school offices fell by 71%. HappyBee now serves families at more than 120 schools.

The challenge

Parents only saw the planned menu.

They couldn’t see what their child was given, or check whether a dish was safe for them.

01 — The problem

Worried parents phoned the school.

Calling was the only way to get an answer about a dish.

  • No meal history: parents could not look back at what their child ate during the week.
  • Allergen worries: parents couldn’t check a dish against their child’s allergies themselves.
  • Data stuck in the kitchen: the kitchen had full details for every dish, but none of it reached parents.
  • Stale menus: parents stop opening an app once its menus are out of date.
02 — The solution

Kitchen records now reach parents.

We connected FeelEat’s kitchen data to the parents’ app and kept each screen short enough to read in passing.

  • Same-day meals: parents see what the kitchen cooked that day.
  • Per-child tracking: each child’s meals across the week, allergens flagged per profile.
  • Thirty-second check: the week’s food summed up for a quick look at the gate.
  • Shared backend: HappyBee reads from the existing FeelEat backend, so the data comes straight from the kitchen system.
What we built

Six features in a small app.

Built around what parents asked us in interviews.

01

Weekly menu browser

The school week, with dishes, photos and dietary flags for each day.

02

Meal history per child

What each child ate on each day of the week.

03

Nutrition & allergens

Detailed nutritional breakdowns and allergen flags from the production kitchen’s own data.

04

Multi-child households

One account for several children, even at different schools. Switching between them takes one tap.

05

Few notifications

Only menu changes and allergen alerts. Nothing else gets pushed.

06

Kitchen data integration

Live sync with FeelEat’s recipe and production systems, so menu changes show up in the app.

How we built it

We talked to parents and school administrators.

They told us what they wanted to know about school lunch.

1

Data model

A data model that links each parent and child to their school’s meal plan.

2

Screens for a quick look

Each screen makes sense at a glance and needs no instructions.

3

iOS and Android apps

Built on the FeelEat backend, with the menu, nutrition data and each child’s meal record.

4

Rollout to schools

Schools joined one after another, now more than 120, and parents were invited in stages.

Bring your version of the HappyBee problem. Four hours, free, with the team that shipped this one.

Book the free workshop
The hard parts

What kept us up at night.

Where a mistake would cost the parents’ trust.

01

Matching allergens to each child

A wrong allergen flag could make a parent trust a dish they shouldn’t. Allergen and nutrition data come from the production kitchen system and are matched to each child’s profile on the server.

02

Adoption by busy parents

We left out feeds and games and kept one job: answering “what did my child eat?” in two taps. 84% of parents activated their accounts.

03

Settings for 120+ schools

More than 120 schools have their own menus, terms and timetables. Each one is set up through settings in the same product.

Architecture

Tech stack.

The iOS and Android apps are native, and the backend is written in PHP on MySQL and Redis.

AndroidiOSPHPMySQLRedis
The outcome

Numbers the owners watch.

What happened once parents could see the meals.

84%Parent activation rate

A small app with one clear job helped get parents to sign up.

−71%Allergen queries to schools

Parents check the app instead of calling the school office.

120+Schools onboarded

Families at every school use the same app.

Parents had to trust HappyBee from day one: the menus, the allergens, what their child actually ate. Because CODT Technologies already knew the platform from FeelEat, we didn't start from zero. They told us plainly what to build first, and that kept our launch small and solid.
Marco Barboza
Marco Barboza
Co-Founder · HappyBee
Case FAQ

Frequently asked questions

Anything we missed?

Put it in a brief. A senior engineer reads it and replies within one business day.

What is HappyBee?

HappyBee is an app that shows parents what their children eat at school: the weekly menu, nutrition details and a record of each child’s meals.

Who built HappyBee and what did it achieve?

CODT Technologies built and operates the platform. 84% of parents activated their accounts across more than 120 schools, and allergen-related questions to schools dropped by 71%.

How does HappyBee handle allergens?

Every dish has nutrition and allergen data attached, and the app checks it against each child’s profile. Parents can look it up themselves instead of calling the school.

Your turn

Have a problem worth
solving well?

Tell us about your product, your timeline and your constraints. We reply within one business day with an honest read on fit, scope and the right team.