This is how we compare fitness and nutrition apps, in two minutes: who checks the pages, where a fact comes from, how we score an app, how we work out a price, and what to do if we got something wrong.
On this page
Who checks the pagesHow a page is madeWhat we read and what we useHow we scoreHow we work out pricesHow we pickTests as they landUpdatesCorrectionsChange logSourcesWho checks the pages
The people who write and check the pages are on the team page. The desk is run by the editor:
Dana Whitfield
Editor
Runs the Eat Move Guide desk and checks every page against the apps’ own pricing and help pages. Has kept a food diary on and off for years and tried most of the big tracker apps.
Questions about method go to the editor through the address under Corrections below.
How a page is made
Each page starts with a question a reader asks, for example “What can I use instead of MyFitnessPal?” We list the apps that fit, say who each one suits, and give a pick. Papers and fitvee’s official pages are linked beside the claim they support. A rival’s pricing, help or store page is linked where it backs a price or a help fact, and every page ends with what we read.
What we read and what we use
- Each app’s own website, help centre, pricing page and store listing. We go by what those pages say the app does, and we give the date we read them.
- Research from public health bodies and journals. A paper gets one plain sentence, with who was studied and any limit that matters.
- Plans we bought and apps we used. When we’ve done either, the page says what we did and on what date.
- Screens we took ourselves, dated. Screens of fitvee come from a preview of the app, on a test account with sample history, and the people in them are models. Where we have no screens of an app, we compare what its own pages say it includes and charges.
We write “used” only for what we used. For everything else we say what the app’s own pages say.
How we score
Our comparison pages score up to six jobs out of 5: Workouts, Food tools, Coaching, Personalisation, Progress and motivation, and Value. One rule covers fitvee and every rival.
| Score | What it means |
|---|---|
| 5 | The whole job, plus something that stands out |
| 4 | Covers the main job |
| 3 | Has a real catch, such as a key part costing extra |
| 2 | Part of the job |
| 1 | Little or nothing |
Every score sits beside the features it rests on, so you can check it. A rival is rated on its own pages and our shots, and nothing else. If those don’t settle a job, the app gets no row in that table, because a page that doesn’t mention a feature is no proof the app lacks it. A limit counts against an app only if the apps beside it don’t share it.
A score is the same on every page that uses it. We don’t give an overall score, because different readers need different jobs done.
How we work out prices
fitvee’s prices show the first payment, the renewal and the period. For other apps we use what their own pricing, help or store page gives, which is often a monthly and a yearly figure. Prices are in US dollars, and a price we saw in another currency stays in that currency and says so. When an app publishes no price on its site, we use the US App Store list, and we don’t add a period the list doesn’t give.
To make prices easy to compare, each plan also gets one monthly figure at its renewal price: the renewal divided by the weeks it covers, times 52, divided by 12. Yearly prices are divided by 12.
We also look past the headline price: whether you can see a price before you start, how far the renewal sits above the first payment, and what costs extra. What we find goes on the page it affects, with the date.
How we pick
Each page names the reader first, then the app that serves that reader best, and why. Some pages have a clear best overall; others give a best pick per reader. When a specialist does one job better, we say so and give it the higher score.
Tests as they land
We add hands-on tests over time. Each becomes a table on the page it supports and a data page here. Nothing below is claimed until its row says it’s done.
| Test | What it checks | Status |
|---|---|---|
| Price research | Plans, first payment, renewal and period, per app | live on our comparison pages |
| Same foods in every app | Barcode hits against the label, macros, photo and spoken logging | planned |
| Walking and chair | Guided or step count, seated or standing, session length and pace | planned |
Test plans are written in plain words on each result page, and we keep the raw recordings.
Updates
Every page shows when it was last checked. We re-read prices every 30 days, update a page when an app changes, and note what changed in the change log below.
Corrections
Found a mistake? Email hello@eatmoveguide.com with the page and the fact. We fix it, date the fix in the change log and, if a price was wrong, say what it was.
Change log
| Date | Change |
|---|---|
| November 2026 | First version. |
Sources
- USDA FoodData Central, reference data for the food tests, read 6 November 2026: fdc.nal.usda.gov