All Posts
EngineeringiOSAndroid

Why Atomic Fast is the Smallest Fasting and Calorie Tracking App on the App Store

Most fasting and calorie tracking apps are 100–300 MB. Atomic Fast ships under 15 MB on both platforms with more features. Here's the engineering philosophy behind the difference.

May 13, 2026·5 min read
Why Atomic Fast is the Smallest Fasting and Calorie Tracking App on the App Store

Most fasting and calorie tracking apps weigh somewhere between 60 and 300 MB. Atomic Fast ships under 15 MB on both platforms — around 11 MB on iOS and 8 MB on Android.

That's not a stripped-down app with missing features. It includes fasting tracking with metabolic phase visualization, AI-powered calorie and macro tracking, a native Apple Watch companion, deep HealthKit integration with 24 read types and 11 nutrients written back, seven on-device intelligence engines, and full Google Health Connect support on Android.

Here's how the category looks:

AppiOS SizeAndroid Size
Yazio304 MB28 MB
MyFitnessPal273 MB51 MB
Cal AI240 MB45 MB
Fastic230 MB100 MB
Zero203 MB52 MB
Lifesum200 MB36 MB
Lose It!198 MB63 MB
Simple192 MB54 MB
Cronometer128 MB45 MB
Atomic Fast11 MB8 MB

Sizes checked on May 13, 2026 from the App Store and Google Play Store listings.

The size isn't the feature. It's the receipt for a specific set of engineering decisions.

Why most apps in this category are large

If an app that tracks fasting, meals, and calories weighs 200 MB, there are usually a few familiar reasons behind it.

Cross-platform frameworks. React Native, Flutter, and similar tools let teams ship one codebase to iOS and Android. The trade-off is that the framework itself ships with every app — typically 30 to 50 MB of base weight before a single feature is written. Convenient for velocity. Expensive in binary size and startup time.

Bundled food databases. Calorie trackers often ship cached copies of large food databases for offline search. That's millions of entries, sometimes with images. Useful, but heavy.

Embedded analytics SDKs. Most consumer apps include four to six third-party SDKs — Facebook, Mixpanel, Amplitude, AppsFlyer, Branch, Segment. Each adds 5 to 15 MB. They compound quietly.

Resolution variants. Image assets get bundled at multiple resolutions for every screen density. Multiply by every screen, and it adds up.

Bundled media. Onboarding videos, tutorial content, sample meal photos. All shipped in the binary regardless of whether a user ever views them.

None of this is inherently wrong. These are individually reasonable decisions that compound into something most users don't notice consciously — but feel in install time, cold starts, and storage pressure.

What Atomic Fast does differently

The goal was never "build the smallest app." It was to build the most efficient one. The size is a side effect.

Pure native on both platforms. SwiftUI on iOS, Jetpack Compose on Android. Two codebases. Slower to develop, but no cross-platform runtime shipping inside the binary. The result is smaller bundles, faster cold starts, and UI that respects each platform's conventions.

No massive bundled food database. Calorie apps often ship tens of millions of food entries inside the binary. Atomic Fast queries the USDA database via API at search time and caches entries locally as users log them — the database grows organically from actual usage rather than bloating the install.

Cloud-first AI scanning. Atomic Fast's meal recognition runs on Google's Gemini API rather than bundling any vision models inside the app. This keeps the binary at zero AI weight while accessing models that improve continuously without requiring an app update.

Intelligence engines are code, not model weights. The seven engines that correlate fasting with sleep, HRV, heart rate, and activity are deterministic algorithms. They're logic, not machine learning weights. They stay tiny because they're built as actual software — not as opaque 50 MB model files.

Minimal third-party SDKs. No advertising SDKs, no marketing analytics, no attribution trackers. The app uses platform-native tools for crash reporting and subscription management — the infrastructure essentials — and nothing else.

No bundled media. Educational content and help resources load from the web when needed. Nothing ships in the binary that a user didn't ask for.

The trade-offs

Every decision has a cost.

Two native codebases means every feature ships twice. Bugs reproduce differently on each platform. Development takes longer upfront — though the velocity gap narrows over time as the architecture stabilizes.

Network dependency for some flows. Food search and AI scanning require connectivity. The fasting timer, water logging, readiness scoring, and all core insights work fully offline. But the AI features need a connection.

Less analytics granularity. Without third-party attribution SDKs, some acquisition insights aren't easily accessible. The trade was deliberate: ship what matters for the user, add measurement when needed.

What a small binary actually buys

For most users, the difference between under 15 MB and 300 MB isn't something they consciously evaluate. But they experience its effects every day.

Speed. Smaller binaries load faster, cold-start faster, and update faster. This compounds across hundreds of app launches over months of use.

Privacy. Fewer embedded SDKs means fewer places user data flows. The closer an app stays to "first-party platform tools plus its own server plus nothing else," the simpler the privacy story becomes. Atomic Fast doesn't ship advertising or marketing analytics SDKs.

Battery. Less background activity from third-party SDKs. Difficult to measure precisely, but real.

Trust. A 300 MB fasting app implicitly says "a lot of code shipped that you didn't ask for." An 11 MB one says the opposite. Most people won't articulate this, but the feeling of a light, fast, responsive app builds trust over time.

The size is the receipt

Binary size isn't something that can be faked or marketed into existence. It's a direct output of architectural decisions made at every level.

The same philosophy that kept the binary small also shaped the rest of Atomic Fast:

  • Notifications that inform without nagging — no streak loss-aversion, no guilt
  • A free tier that's genuinely useful — not a trial dressed as a free version
  • On-device intelligence — fasting patterns and health correlations stay on the phone
  • No dark patterns — no fake urgency, no scarcity timers, no manipulative paywalls
  • Health data that flows back — nutrients and water write to Apple Health and Health Connect, not locked inside a proprietary silo

Lean code usually means someone said no to a lot of things. Being the smallest app in the category is hard to fake. And that's exactly why it matters.


Atomic Fast is available on the App Store and Google Play. Free to download.

Want to try Atomic Fast?

Download Free