Meal plans built from food you actually eat

Most nutrition apps were written in one food culture and exported everywhere else. Open them in Accra, Nairobi or Karachi and you get a shopping list that doesn't match your market, your kitchen or your budget — so you improvise, the macros stop meaning anything, and the plan dies quietly in week two.

SnapFit starts from the opposite end: your targets are the constraint, and the food is whatever is normal where you are.

How the localisation works

You choose your country during onboarding. Plans are then generated around that region's staples, cooking methods and portion shapes — not a global menu with a local dish bolted on. Jollof with the rice portion sized to your carb target is a different thing from "chicken and rice, 200 g".

If you're in…	Plans are built from
Nigeria	Jollof rice, egusi soup, suya, moi moi, beans and plantain
Ghana	Waakye, banku and tilapia, kontomire, light soup
Kenya	Ugali, sukuma wiki, nyama choma, githeri
South Africa	Pap and chakalaka, bobotie, braai meats, samp and beans
United Kingdom	Porridge, jacket potatoes, roast chicken and veg
United States	Burrito bowls, overnight oats, grilled chicken and rice
India	Dal, roti, paneer bowls, idli and sambar
UAE & Saudi Arabia	Kabsa, shawarma, hummus, grilled kofta
Philippines	Adobo, sinigang, rice bowls
Brazil	Feijoada, açaí bowls, grilled chicken and rice

A sample, not the full list — SnapFit ships in 170+ countries and builds around the cooking of each.

Where the numbers come from

Calories and macros are derived from your goal, body stats and activity level, then adjusted as real data arrives: logged sessions, weight entries, and — if you connect a watch — actual steps and active calories. An AI body scan sharpens the starting estimate, because body composition changes what a sensible target looks like at the same bodyweight.

Restrictions are constraints, not filters

Vegetarian, vegan, halal, allergies, foods you simply don't like: these go in during onboarding and the plan is generated around them. The difference matters. A filter removes the offending meal and leaves a hole in your day's macros; a constraint produces a different plan that still adds up.

Common questions

How does SnapFit know what food is normal where I live?

You pick your country during onboarding, and the plan is generated around the cooking of that place — the staples, the cooking methods and the portion shapes people actually use. You can change it any time if you move or simply eat differently.

What if I am vegetarian, vegan, halal or avoid certain foods?

Dietary preference is part of onboarding and constrains every plan generated afterwards. Allergies and dislikes can be excluded too, and the plan regenerates around them rather than quietly swapping one restricted ingredient for another.

Are the macros adjusted to me or are they generic?

They come from your goal, body stats and activity, and shift as the picture changes: train harder for a week, or log a stretch of sessions, and the targets move with it. A body scan sharpens the starting estimate.

Can I see calories and macros per meal?

Yes. Every meal in the plan carries its calories and macro split, and logging it counts against the day. Water is tracked alongside it.

Metric or imperial?

Both — pick one during onboarding and the whole app follows it, including weights, heights and portion sizes.