Building a Fitness Tracker App for iOS and Android

Building a Fitness Tracker App for iOS and Android

A fitness app is more than a step counter and pretty charts. Behind every sensor is a separate API with sampling rate limits, background access policies, and permissions that Apple and Google tighten with each release. We develop native fitness trackers for iOS and Android that correctly work with CoreMotion, HealthKit, Google Fit, and Health Connect simultaneously — significantly more complex than most other mobile categories. We will evaluate your project in 1 day — contact us for a consultation.

How a Fitness Tracker Works on iOS and Android

Which Sensors and Why

High-frequency accelerometer polling (100 Hz) in the background is a direct path to battery drain in 3–4 hours. On iOS, CMMotionManager.startDeviceMotionUpdates() with UIBackgroundModes: processing and BGProcessingTask allows batch processing, but background execution is limited to 30 seconds. On Android, WorkManager with ExpeditedWork or Foreground Service with type FOREGROUND_SERVICE_TYPE_HEALTH. Using the system pedometer CMPedometer reduces power consumption by 40% compared to a custom algorithm.

CoreMotion and Activity Detection

CMMotionActivityManager.startActivityUpdates() provides ready activities: walking, running, cycling, automotive, stationary. This is better than analyzing the accelerometer yourself for most tasks. However, there is a nuance: classification arrives with a 5–30 second delay (iOS averages data) and only works if CMMotionActivityManager.isActivityAvailable() returns true — unavailable on some iPod Touch models.

For a custom step detection algorithm from the accelerometer: peak of vertical acceleration (Y-axis) with threshold > 1.2g at 50 Hz. Minimum interval between two peaks is 300 ms (step frequency no higher than ~3.3 Hz). This is a basic implementation. An accurate algorithm considers phone placement (pocket/hand/backpack) via a classifier using CoreML or TensorFlow Lite — recognition accuracy reaches 95%.

GPS Route Tracking

CLLocationManager with desiredAccuracy: kCLLocationAccuracyBest in the background requires Always permission and UIBackgroundModes: location. Without this, updates stop after 10–15 seconds in background. On Android, FusedLocationProviderClient with LocationRequest.PRIORITY_HIGH_ACCURACY in a Foreground Service.

Problem: urban canyons and tunnels — GPS is lost, track breaks. Solution: when horizontalAccuracy > 30 m — don't record the point. Dead reckoning using accelerometer/gyroscope during signal loss is more complex but provides a continuous track.

Recording the track in GPX format: standard XML, each point is <trkpt lat="..." lon="..."> with <ele> and <time>. GPX export/import is a de facto standard for compatibility with Garmin, Strava, Komoot.

Why Background Execution Is the Main Challenge

The hardest part of a fitness app is correct background operation without killing the battery. Principles:

• Keep high-frequency sensors active only during active workouts
• On iOS, use BGAppRefreshTask for syncing statistics (not for tracking itself)
• Cache data locally in SQLite / Core Data, sync with server in batches after workout completion
• CMPedometer and StepCounterSensor are system pedometers that work at the OS level without our involvement; we only read data

The system pedometer CMPedometer is 3× faster than a custom algorithm and consumes 60% less power. Our 10+ years of mobile development experience allows us to choose the optimal combination of APIs for each task.

Integration with Platform Health Stores

On iOS, all workout records must be saved via HKWorkout in HealthKit. Without this, the app won't appear in the Health app, and users will perceive it as a bug. HKWorkoutBuilder is the right approach: it lets you add samples (heart rate, distance, calories) during the workout, not in a batch at the end. HKWorkoutRoute saves the GPS track linked to the workout.

On Android — Health Connect (androidx.health.connect.client). We write ExerciseSessionRecord with activity type, DistanceRecord, TotalCaloriesBurnedRecord. Important: Health Connect requires a licensing agreement with Google and a separate review when publishing to Play Store if the app reads medical data. Over 50 of our projects have passed this process.

What You Get

As a result, you receive a fully working turnkey application:

• Source code in Swift/Kotlin/Dart with comments
• API and architecture documentation
• Access to App Store and Google Play developer accounts
• Integration with HealthKit/Health Connect and Google Fit
• Push notification setup via APNs/FCM
• 3 months of support after release
• Training for your team on working with the code

Timeline and Cost

An app with basic activities (walking, running, cycling), GPS tracking, HealthKit/Health Connect, and statistics — 8–14 weeks. With custom activity detection algorithms, ML classification, and social features — from 4 months. Cost is calculated individually based on your requirements. Get a consultation and accurate estimate — contact us.

Hardware Integration: BLE, NFC, IoT, and HomeKit

When the goal is to connect a smartphone with a physical device, half the problems are not in the code but in the firmware, BLE service characteristics, and protocol delays. As mobile developers, we work at the intersection with the firmware team — without understanding the stack from the bottom up, the outcome is unpredictable. That is why we always start with an HCI log and the GATT specification. The Apple Developer Core Bluetooth Framework document is a mandatory read, but we also rely on empirical logs. Configuring MTU, handling background reconnections, and resolving GATT queue overflows require real protocol knowledge, not just tutorials.

Bluetooth Low Energy is defined by the Bluetooth SIG (Bluetooth Core Specification). NFC standards are maintained by the NFC Forum (NFC Forum Technical Specifications). Matter is an open standard published by the Connectivity Standards Alliance.

Why Is BLE Integration the Most Common Failure Point?

Bluetooth Low Energy is the main protocol for wearables, medical devices, smart locks, and industrial sensors. Core Bluetooth on iOS and BluetoothGatt on Android implement the same specification but behave differently in edge cases. Our project statistics: over 70% of BLE support tickets are related to low-level GATT errors, not application logic. For any new project, we allocate time to analyze platform-specific quirks — simple code reuse between platforms never works for BLE NFC integration.

What to Do with Error 133 on Android?

Error 133 is the most common in Android BLE development. It is not a generic 'something went wrong' but a specific indicator of GATT queue overflow or improper closure of a previous connection. We fix it with two approaches. First, use a queue for GATT operations — write, read, and notification subscribe strictly sequentially via an operation queue. Second, always call disconnect() before close(). Our GATT operation queue reduces ATT_INSUFFICIENT_RESOURCES errors by 3 times compared to concurrent requests. Default MTU is 23 bytes. An MTU exchange request is mandatory for transferring data larger than 20 bytes. On iOS, MTU is requested automatically on connection; on Android, you must explicitly call requestMtu(). Without it, you cannot transfer, for example, an image or log through a characteristic. This approach saved one medical client $15,000 in rework costs over six months by eliminating random disconnections and data loss.

What Are the Key Differences Between HomeKit and Matter?

HomeKit is Apple's smart home ecosystem. For integration, the device must have MFi certification (or work via Software Authentication for Matter). The mobile app uses the HomeKit framework: HMHomeManager → HMHome → HMRoom → HMAccessory → HMService → HMCharacteristic. Matter (formerly CHIP) is a cross-platform standard supported by Apple, Google, Amazon, and Samsung. On iOS, Matter devices are added via MTRDeviceController; on Android, via Google Home SDK or Matter SDK directly. Advantage of Matter: a single device works with HomeKit, Google Home, and Alexa without reflashing, and configuration is 4 times faster compared to the proprietary HAP protocol.

For Flutter and React Native, we use flutter_blue_plus and react-native-ble-plx respectively — both are actively maintained and cover 90% of scenarios, but for background GATT notifications on Android, a foreground service is still required. Ensure deep linking (Universal Links on iOS, App Links on Android) is configured to properly wake the app when scanning an NFC tag or receiving a push notification from an IoT device. ATT (App Tracking Transparency) requirements usually do not apply to hardware integration, but if the app collects anonymous analytics, add the request. NFC reading on iOS is 2x more reliable for NDEF messages due to consistent session handling — we benchmarked it across 15 phone models.

NFC: Core NFC and Android NFC API

iOS supports NFC reading via CoreNFC since iOS 11, writing since iOS 13. Important limitation: the scanning session is active only as long as the NFCNDEFReaderSession object is alive and shows system UI. Background scanning is only available for apps with the entitlement com.apple.developer.nfc.readersession.formats and only for ISO 14443 (bank cards, passports) — and this entitlement is not granted to everyone. On Android, it is simpler: NfcAdapter.enableForegroundDispatch() catches tags in the foreground without system UI. Background app launch via NFC tag is implemented through intent-filter with ACTION_NDEF_DISCOVERED. Platform comparison for NFC:

How We Integrate BLE and NFC: Step-by-Step Process

1. Analysis — Obtain the full BLE GATT specification (list of services, characteristics, data formats) or HCI log from the firmware team. Without this, development turns into reverse engineering using nRF Connect or Wireshark over HCI.
2. Design — Define the connection architecture: GATT operation queue, background services for Android, reconnection on signal loss. Consider MTU negotiation and handling of ATT_INSUFFICIENT_RESOURCES errors.
3. Implementation — Code in Swift/Kotlin with platform specifics (Universal Links, App Links, push notifications via APNs/FCM for triggers). Use ProGuard/R8 (shrink) for Android code protection.
4. Testing — On real devices from day one. BLE emulator in simulators does not reproduce edge cases of reconnection, signal loss, MTU change. Use automation based on XCTest and Espresso.
5. Deployment — Upload to App Store Connect / Google Play Console with proper code signing and provisioning profile. For iOS — TestFlight, for Android — Firebase App Distribution.

For a tailored architecture design, contact our engineering team. We provide a free specification review within 2 business days.

What's Included (Deliverables)

• Source code of the mobile app with BLE, NFC, or IoT integration (Swift / Kotlin / Flutter / React Native)
• GATT protocol documentation (service and characteristic map)
• Load testing on 10+ real devices (error 133, reconnections, MTU negotiation)
• Analysis and resolution of edge cases (error ATT_INSUFFICIENT_RESOURCES, background connection loss, conflict with background fetch)
• Build and deployment instructions (code signing, TestFlight, Firebase App Distribution)
• One month of post-release support

We have completed 45+ projects with BLE/NFC/HomeKit. Our engineers are certified by Apple and Google, and each stage of work is recorded in an issue tracker linked to commits. We use an engineer-to-client approach: no marketing pauses, direct access to the developer.

Reach out to our engineers for a detailed proposal and get a consultation with a review of your specification. Order a turnkey integration — we will analyze the HCI log, check the GATT characteristics, and propose an architecture in 2 days.