// REFERENCE

Glossary

Plain-English definitions of 8 tech-tester terms used in our calorie tracker app reviews. MAPE, food database architecture, photo recognition workflows, barcode scanning, freemium pricing, paywalled features, app versioning, and sync.

General

App Version

The app version is the specific release number of the calorie tracker app under test. Version-to-version accuracy can shift sharply when an app updates its photo model or database; we re-test on app updates and disclose the version every published number applies to.

Database

Barcode

Barcode scanning in a calorie tracker app uses the phone's camera to read a UPC code on packaged food and look up the matching database entry. Quality depends on database breadth (does it know the SKU?) and verification (is the calorie value right?).

Food Database

A food database is the indexed collection of foods, with per-portion calorie and macro values, that a calorie tracker app uses to convert your logged meal into a calorie number. Database quality (USDA-aligned vs. crowdsourced) drives accuracy more than database size.

Pricing

Freemium

Freemium is the pricing model where a calorie tracker app's basic tier is free but advanced features are gated behind a paid 'Premium' or 'Pro' subscription. Most major calorie trackers in 2026 are freemium; the question is whether the free tier is genuinely usable or a paywalled trial.

Paywalled Feature

A paywalled feature is one that's gated behind the app's paid (Premium/Pro/Plus) subscription tier. In 2026, the most commonly paywalled calorie tracker features are barcode scanning, gram-level macro breakdown, custom recipes, and data export.

Accuracy

MAPE

Mean Absolute Percentage Error (MAPE) is the standard metric for measuring how accurate a calorie tracker app is. It's the average percentage gap between what the app says about a meal and what the meal actually contains. Lower MAPE means a more accurate app.

Photo AI

Photo Recognition

Photo recognition (in calorie tracker context) is the technology that converts a photograph of your meal into a calorie estimate. Two architectures dominate: dish-classification (recognize the dish, look up calories) and per-component portion estimation (estimate each visible component's portion directly).

Platform

Sync Conflict

A sync conflict happens when a calorie tracker app's data on different devices (phone, watch, web, tablet) gets out of sync — typically because of offline edits, simultaneous edits across devices, or background-sync failures. Quality of sync conflict resolution varies sharply across calorie tracker apps.