easyChef Pro

What it is

easyChef Pro is a consumer health and nutrition platform combining meal planning, pantry management, grocery workflows, nutrition data, and personalised recommendations.

It is published on Google Play and on the Apple App Store, free, for iPhone and iPad, under Digital Galactica Labs. Same product, two platforms, two independent review processes.

It is a full consumer product rather than a demonstration: real users, store reviews, support requests, release cycles and running costs.

The engineering problem

Nutrition guidance is only useful if a person can act on it, and a person can only act on a number they are able to trust. That constraint shaped the architecture.

The scoring engine calculates rather than predicts. Given the same food and the same profile it returns the same result, and the reasoning can be shown. A model that produced a plausible but different answer each time would have been faster to build and impossible to stand behind.

That is the line we draw on every project, not just this one. AI is genuinely useful where interpretation helps - describing, suggesting, summarising, ranking. Calculation and data aggregation, where correctness is the whole point, are deterministic systems. Asking a language model to add up a day of nutrition is a category error, and it is an expensive one because the wrong answer looks exactly like the right one.

A registered dietitian owns the nutrition methodology and the boundary of what the product is allowed to claim. That is a governance structure, not a marketing line, and it constrains what engineering is permitted to ship.

Concept to store, and everything after

DGL took easyChef Pro the whole way: the original concept, the data and scoring architecture, the application itself, quality assurance, submission and review at both Apple and Google, release, and the operation of it since. No part of that was handed to someone else, which is why the detail on this page exists at all.

Mobile development, backend services, databases, APIs, analytics, deep linking, application releases and production infrastructure.

The parts that are easy to underestimate are the ones that recur: store review, staged rollouts, attribution that reconciles with what ad platforms report, deep links that resolve to the right screen rather than dropping someone on a store page, and lifecycle email that runs on its own.

Shipping the same product to two stores is not one job done twice. Each platform has its own review process, its own rejection reasons, its own release mechanics and its own identifiers - easyChef Pro carries a different package identifier on each, which is ordinary and is exactly the kind of detail that breaks a link if someone assumes otherwise. We have been through both.

This is the experience clients are actually buying when they hire us for mobile work. We have made those mistakes on our own product.