Fitness app development cost in 2026: what drives it and what you'll pay every month
Fitness app build cost depends on scope, but the platform fees are public. The cost drivers, Apple and Google fees and commissions, which revenue pays commission, the end-of-2026 Google Fit migration, cloud free tiers, the privacy cost line and a step-by-step guide to making a fitness app.

Key takeaways
- 01A fitness app's build cost depends on platforms, wearable integrations, video, subscriptions and privacy work, so honest quotes start from a written scope, not a range.
- 02Fixed fees are public: Apple charges $99 a year and Google Play $25 once. Apple pays you 85% of a subscription after a subscriber's first paid year, or from day one in the Small Business Program.
- 03Digital workouts and subscriptions use in-app purchase; one-to-one live training may bill outside it; gym classes consumed in person must not use Apple in-app purchase.
- 04Google says the Google Fit APIs will be supported until the end of 2026, so Android apps need a migration to Health Connect, the Google Health API or Wear OS Health Services.
- 05Budget a privacy line: the FTC's Health Breach Notification Rule probably covers apps that sync with fitness trackers, and Washington's My Health My Data Act covers consumer health data.
A fitness app's build cost depends on platforms, wearable integrations, video, subscriptions and privacy work, so honest quotes start from scope. The fixed costs are public: Apple charges $99 a year, Google Play $25 once, and Apple's subscription commission falls to 15% after a subscriber's first year. Google Fit's end-of-2026 cutoff adds a migration line.
Most fitness app cost guides lead with a range like "$20,000 to $100,000" and never show where it comes from. Some still price "Google Fit integration" as a feature, even though Google has set an end date for those APIs. This guide does two things instead. It explains what drives the build cost, so you can scope and compare quotes. And it lists the fees every fitness app founder pays, each attributed to the platform's own page and checked on 23 October 2026. Elgrith doesn't publish prices; we give a fixed quote after scoping.
What drives the cost of building a fitness app?
| Driver | Why it adds cost | Ways to keep it in check |
|---|---|---|
| Platforms | iOS, Android, web and watch apps are separate surfaces to build, test and release | Launch on the platform your audience uses most, or use Flutter or React Native for shared code |
| Health and wearable data | HealthKit, Health Connect, Wear OS, Fitbit and Garmin each have their own APIs, permissions and edge cases | Start with one or two sources; read and write only the data types you need |
| Workout content and video | Encoding, streaming, offline downloads and a content admin | Use a video platform; keep the first library small |
| Plans and progress | Training plans, streaks, progress rings and charts | Model plans as data so coaches can edit them without releases |
| Live classes and coaching | Scheduling, video calls, chat and payments for coaches | Integrate scheduling and video providers instead of building them |
| Subscriptions and billing | StoreKit, Google Play Billing, trials, upgrades and entitlement sync across devices | Use one entitlement service as the source of truth |
| AI features | Personalized plans, form feedback or a coach chatbot, plus evaluation and safety checks | Add after core retention works; see AI agent vs chatbot |
| Privacy and compliance | Consent flows, data minimization, breach planning, store declarations | Design it into the data model from the start |
The biggest swing factor is usually wearables and video, not screens. A workout logger with no device data is a much smaller build than an app that syncs heart rate from three platforms and streams classes.
What do Apple and Google charge to publish a fitness app?
| Fee | Amount | Source (read 23 Oct 2026) |
|---|---|---|
| Apple Developer Program | "99 USD per membership year" | Apple |
| Apple Small Business Program | "reduced commission rate of 15% on paid apps and Apple In-App Purchases" for developers with up to "1 million USD in proceeds" | Apple |
| Apple auto-renewable subscriptions | 70% of the price in a subscriber's first year; "After a subscriber accumulates one year of paid service, your net revenue increases to 85%" | Apple |
| Google Play developer account | "US$25 one-time registration fee" | Google Play Help |
| Google Play service fees | A new fee structure took effect on 30 June 2026 for the EEA, UK and US, and on 30 September 2026 for Australia and Japan | Google Play Help |
Apple's subscriptions page adds that Small Business Program members receive 85% of the subscription price at each billing cycle, regardless of whether the subscription has a year of paid service. Google's service fees now vary by market, product type and date of install, so read the live table for your countries before you model revenue rather than relying on a single headline rate.
Illustrative example (not a quote): a $9.99 monthly subscription sold through Apple. A developer outside the Small Business Program receives about $6.99 a month (70%) during a subscriber's first year and about $8.49 (85%) after it, before taxes. A Small Business Program member receives about $8.49 from the first month. Over a subscriber's first 12 months that is a difference of about $18 per subscriber.
Do subscriptions and gym classes both pay commission?
No. Apple's App Review Guidelines split fitness revenue three ways:
| What you sell | Apple's rule | Payment method |
|---|---|---|
| On-demand workouts, plans, premium features (digital) | 3.1.1: to unlock features or content, "you must use in-app purchase" | Apple in-app purchase |
| One-to-one live coaching or personal training | 3.1.3(d): real-time person-to-person services such as "fitness training" may use other purchase methods; "One-to-few and one-to-many real-time services must use in-app purchase" | Your choice for one-to-one; in-app purchase for live group classes |
| In-person gym classes, memberships and physical products | 3.1.3(e): goods or services "consumed outside of the app" must use purchase methods other than in-app purchase | Your own payment provider |
This matters for the business model. A studio app that books in-person classes keeps that revenue outside Apple's commission, while an app selling a library of video workouts pays it. Apple also changed its US storefront rules on 1 May 2025 to allow links to outside purchasing, and related litigation was still ongoing in October 2026, so take advice before you design checkout around link-outs. Google Play has its own billing rules; check its policy for each product type.
What does the Google Fit migration add to the cost?
Google's migration guide (last updated 10 September 2026) says: "The Google Fit APIs will be supported until the end of 2026." Developers haven't been able to sign up for the APIs since 1 May 2024. Any Android fitness app still using them needs a migration in its 2026–27 plan.
| If your app uses | Move to |
|---|---|
| Fit History and Session APIs (cloud data) | Google Health API |
| Step tracking on the phone (Fit Recording API) | Health Connect |
| Fit APIs on Wear OS | Health Services, available on Wear OS 3 and higher |
| Fitbit Web API | Google Health API |
| Goals API | "No replacement API available": manage goals in your own app logic |
The cost line comes from new permission flows, different data models, re-testing on devices and moving users' history. Treat a quote that still lists "Google Fit integration" as a feature as out of date. On iOS, Apple HealthKit remains the source of health data, and Apple's guideline 5.1.3(ii) says apps "may not store personal health information in iCloud".
What are the cloud, maps and other running costs?
Many fitness apps can launch on free tiers, then pay as they grow:
| Service | Free tier (read 23 Oct 2026) | Source |
|---|---|---|
| Firebase Spark plan | "No payment method needed"; Firestore "up to 50K reads/day" and "20K writes/day"; Authentication "No-cost up to 50K MAUs" | Firebase pricing |
| Mapbox Mobile Maps SDK | Free "Up to 25,000" monthly active users | Mapbox pricing |
Running and cycling apps that draw routes can stay inside a maps free tier for a while; workout video usually becomes the largest running cost, so pick a video provider early and model storage and streaming at your expected month-12 audience. Other recurring lines are push notifications, email, analytics, crash reporting, subscription management, customer support and the developer time to keep up with yearly iOS, Android and watchOS releases. For a full backend comparison, see Supabase vs Firebase.
What should you budget for privacy and compliance?
Fitness data is health data in the eyes of several regulators, even when HIPAA doesn't apply. This is general information, not legal advice.
- FTC Health Breach Notification Rule: the FTC's compliance guide (July 2024, edited January 2025) says that if your app "can sync with a consumer's fitness tracker", "you're probably a vendor of personal health records", and breach notices are due "within 60 calendar days". The FTC's 2024 amendments "underscore its application to health apps and similar technologies not covered by HIPAA".
- Washington My Health My Data Act: under RCW 19.373.010, consumer health data includes "Bodily functions, vital signs, symptoms, or measurements", which covers much of what fitness apps collect.
- Google Play Health apps declaration: Google says "All developers that have an app published on Google Play must complete the Health apps declaration", including closed and open testing tracks (Play Console Help).
- HIPAA applies when you build for a covered entity or business associate, such as a clinic-prescribed rehab app. That is a different scope; see healthcare app development.
The cost here is design and process work: consent screens, a data inventory, encryption, a breach response plan and store declarations. It is far cheaper to build in than to retrofit.
Does native or cross-platform change the cost?
Usually, yes. A cross-platform framework such as Flutter or React Native shares most screens and business logic between iOS and Android, so one team ships both apps. Native development, such as an iOS app in Swift, means separate codebases but the most direct access to platform features.
For fitness apps the deciding factor is device data:
| Feature | Cross-platform works well | Consider native code |
|---|---|---|
| Workout plans, video, progress and subscriptions | Yes | Rarely needed |
| Reading steps, workouts and heart rate from HealthKit or Health Connect | Yes, through plugins or a thin native bridge | If you need unusual data types |
| Live workout tracking on Apple Watch or Wear OS | Partly: watch apps are usually written natively | Yes, for the watch app itself |
| Background sensor tracking and Bluetooth devices | Possible, with native modules | Often, for reliability and battery life |
A common pattern is a cross-platform phone app plus small native watch apps. It keeps most of the build shared while the parts that touch sensors use each platform's own tools.
How do you compare fitness app quotes?
Give every developer the same written scope: platforms, data sources, content, monetization, privacy needs and launch features. Then ask each quote to separate the build from the recurring costs above, to name the health APIs it will use (a quote that still says "Google Fit" is out of date), and to say who owns the code. Comparing three quotes against one scope tells you far more than any published range.
How do you make a fitness app, step by step?
- Validate the idea. Pick one audience (runners, studio members, strength beginners) and one job the app does better than the alternatives. Talk to ten people who would pay.
- Choose your data stack. Decide which health data you read and write, from which platforms: HealthKit on iOS, Health Connect on Android, Health Services on Wear OS. Don't start on Google Fit.
- Pick a monetization model the stores allow. Digital subscriptions through in-app purchase; one-to-one coaching or in-person classes through your own payments, as the table above shows.
- Scope an MVP. One platform or a cross-platform build, one core workout flow, progress tracking and subscriptions. Leave AI features and social feeds for later. Our MVP development cost guide covers how to scope it.
- Build privacy in. Consent, data minimization and the Health apps declaration, from the first sprint.
- Run Google Play's closed test. New personal developer accounts created after 13 November 2023 need "a minimum of 12 testers who have been opted in continuously for at least 14 days" before production, per Google Play Help. Plan your beta around it.
- Launch, measure retention and iterate. Watch week-one and week-four retention before you add features.
How can Elgrith help?
Elgrith has delivered 1,000+ projects for 250+ clients since 2015, from our New Delhi headquarters and client-partnership centers in New York, London and Shanghai. Our fitness app development team builds workout, coaching and class-booking apps with HealthKit, Health Connect and Wear OS, and moves apps off Google Fit. For the wider build, see app development, Flutter app development and healthcare app development for HIPAA-covered work. You own the code and IP, and you get a fixed written quote after a free call. Book a call or start a project.
FAQ
Frequently asked questions
Sources 14 linked
- 01Apple — Developer Program, what's includeddeveloper.apple.com(opens in a new tab)
- 02Apple — App Store Small Business Programdeveloper.apple.com(opens in a new tab)
- 03Apple — Auto-renewable subscriptions (read 23 Oct 2026)developer.apple.com(opens in a new tab)
- 04Apple — App Review Guidelines (3.1.1, 3.1.3(d), 3.1.3(e), 5.1.3)developer.apple.com(opens in a new tab)
- 05Google Play Help — Developer account registration feesupport.google.com(opens in a new tab)
- 06Google Play Help — Testing requirements for new personal developer accountssupport.google.com(opens in a new tab)
- 07Google Play Help — Service fees (read 23 Oct 2026)support.google.com(opens in a new tab)
- 08Google Play Help — Health apps declarationsupport.google.com(opens in a new tab)
- 09Android Developers — Migrate from Google Fit (last updated 10 Sep 2026)developer.android.com(opens in a new tab)
- 10Firebase — Pricing (read 23 Oct 2026)firebase.google.com(opens in a new tab)
- 11Mapbox — Pricing (read 23 Oct 2026)mapbox.com(opens in a new tab)
- 12FTC — Complying with the Health Breach Notification Rule (Jul 2024, edited Jan 2025)ftc.gov(opens in a new tab)
- 13FTC — Finalizes changes to the Health Breach Notification Rule (26 Apr 2024)ftc.gov(opens in a new tab)
- 14Washington State Legislature — RCW 19.373.010 definitions (read 23 Oct 2026)app.leg.wa.gov(opens in a new tab)


