Personalized restaurant meal planningFoodTechCompletedFoodTechNutritionMobile

MyEatPal

Goal-aware meal plans built from the restaurant dishes you already love.

Project snapshot
Client
MyEatPal
Type
Startup
Region
North America
Engagement
End-to-End Delivery
Duration
7 months
Started
Q2 2025
MobileBackendAPIData
Objective

Deliver a crave-worthy planning experience that feels like a concierge — not a calorie spreadsheet — by weaving real restaurant menus into weekly plans users actually follow.

Audience
Busy professionals who order out often but want structureFitness-focused eaters tracking macros without giving up flavorCouples and families juggling different tastes and schedulesAnyone burned out on generic meal-prep templates
Platform
MobileBackendAPIData
Problem

People love restaurant food but hate the guesswork: macros drift, favorites scatter across apps, and 'healthy' plans ignore what they actually want to eat. The result is abandoned subscriptions and guilt-heavy dashboards.

Solution

We built a taste-first planner that ingests dishes you already love, scores them against your goals, and assembles balanced weeks with swaps, portions, and one-tap grocery or order handoffs.

Showcase

A closer look at MyEatPal

Selected screens across the product — from marketing surfaces to in-app flows.

Mobile
Native iOS & Android flows
Onboarding & promise
Home & daily snapshot
Discover dishes
Build your week
Goals & nutrition view
Taste & preferences
Features

What we built

The core capabilities shipped as part of the engagement.

Goal-aware plans: muscle gain, fat loss, maintenance, or flexible balance
Restaurant dish library with filters for cuisine, price, and prep time
Preference memory: allergies, dislikes, spice level, and dietary patterns
Drag-and-week calendar with automatic macro and calorie guardrails
Smart substitutes when a day runs high on sodium or saturated fat
Shareable household plans and duplicate week flows for routine eaters
Architecture

How it's built

The stack and architectural layers powering the product.

Core stack
FlutterNode.jsPostgreSQLAWS

Backend

Node.jsExpress

Mobile

Flutter

Data

PostgreSQLRedis

Infrastructure

AWS ECSS3CloudWatchGitHub Actions

Integrations

Restaurant menu APIsNutrition estimation serviceStripe
Compliance & security
Transparent nutrition disclaimersPII encryption and least-privilege accessRegion-aware data residency options
Delivery

Timeline & team

How the engagement was structured across 28 weeks of work.

Phase 1
4w
Discovery
Phase 2
18w
Build
Phase 3
6w
QA
Team on this engagement
Product ManagerUI/UX DesignerFlutter EngineerBackend EngineerData AnalystQA Engineer
Impact

Results that mattered

Measurable outcomes tracked against the KPIs that drove the build.

Plan adherence
52% more completed weeks vs. control
Time to first plan
Under 4 minutes median
Subscriber NPS
+38 after onboarding refresh
Outcomes

What changed for the business

Shipped iOS and Android apps with a shared menu and planning engine
Onboarded pilot restaurant partners with structured dish ingestion
Enabled experiment-driven ranking for swap and suggestion quality
Nepmind made 'eat what you love' technically possible. Our retention finally matches how excited people are on day one.
Maya Chen
Co-founder, MyEatPal

Have a project like MyEatPal?

Tell us what you're building — we'll help you ship it with the same rigor.