Integrating HealthKit: Health and Workout Data in iOS

We develop iOS apps with HealthKit integration, and here's the real problem almost every client faces: after the first version, the app gets rejected in the App Store due to incorrect permission requests or violation of Guideline 5.1.1. About 30% of apps using HealthKit pass review only on the second attempt. HealthKit isn't just an API for reading data from the Apple Watch—it's iOS's central health repository with a rigid schema, granular permissions per type, and strict policies from HealthKit.

Over the years, we've completed more than 50 HealthKit integrations for clients in fitness, medicine, and insurance. Our engineers have developed a checklist that cuts the App Store approval timeline by an average of two weeks.

How App Store Review Affects HealthKit Integration

Apple manually reviews every HealthKit integration during each review. The main reasons for rejection:

• The app requests data types it doesn't use (HKObjectType must match actual functionality).
• Missing NSHealthShareUsageDescription / NSHealthUpdateUsageDescription in Info.plist—a trivial crash on first request.
• The app requests write permission for workouts but isn't a fitness app—rejection under Privacy (Section 5.1.1).

A quirk of HealthKit permissions: the user can deny access to a specific type, but the app never learns about it explicitly. HKHealthStore.authorizationStatus(for:) returns .notDetermined both when denied and when not yet asked. This is a privacy safeguard—you cannot infer the existence of data from the authorization status.

The practical consequence: you should never show an alert like "You denied access to steps." Instead, silently try to read the data, and if the array is empty, show a neutral message "data unavailable" with a button "Open Health."

Why Query Type Selection Is Critical

HKSampleQuery is suitable for raw samples: each heart rate measurement, each step. For an active user over a year, tens of thousands of records accumulate—a query without a limit and sorting will cause an OutOfMemory crash. Always use limit and sortDescriptors:

let query = HKSampleQuery(
    sampleType: HKQuantityType(.heartRate),
    predicate: HKQuery.predicateForSamples(
        withStart: startDate,
        end: endDate,
        options: .strictStartDate
    ),
    limit: 1000,
    sortDescriptors: [NSSortDescriptor(key: HKSampleSortIdentifierStartDate, ascending: false)]
) { _, samples, error in
    guard let samples = samples as? [HKQuantitySample] else { return }
    let bpmValues = samples.map {
        $0.quantity.doubleValue(for: .init(from: "count/min"))
    }
    // processing
}
healthStore.execute(query)

HKStatisticsQuery processes aggregated data 10 times faster than HKSampleQuery for tasks like total steps per day. For interval statistics (day, week) over a period, use HKStatisticsCollectionQuery:

let interval = DateComponents(day: 1)
let query = HKStatisticsCollectionQuery(
    quantityType: HKQuantityType(.stepCount),
    quantitySamplePredicate: nil,
    options: .cumulativeSum,
    anchorDate: Calendar.current.startOfDay(for: Date()),
    intervalComponents: interval
)
query.initialResultsHandler = { _, results, _ in
    results?.enumerateStatistics(from: startDate, to: endDate) { stat, _ in
        let steps = stat.sumQuantity()?.doubleValue(for: .count()) ?? 0
    }
}

HKAnchoredObjectQuery is for background updates: the app receives only the delta since the last query.

How to Record a Workout: HKWorkoutBuilder in Real Time

For recording an active workout—always use HKWorkoutBuilder, not the old HKWorkout(activityType:start:end:). The builder allows adding samples in real time:

let config = HKWorkoutConfiguration()
config.activityType = .running
config.locationType = .outdoor

let builder = HKWorkoutBuilder(healthStore: healthStore, configuration: config, device: .local())

builder.beginCollection(withStart: Date()) { success, error in
    // workout started
}

// every 5 seconds add heart rate
let heartRateSample = HKQuantitySample(
    type: HKQuantityType(.heartRate),
    quantity: HKQuantity(unit: .init(from: "count/min"), doubleValue: 142),
    start: Date(), end: Date()
)
builder.add([heartRateSample]) { _, _ in }

// finish
builder.endCollection(withEnd: Date()) { _, _ in
    builder.finishWorkout { workout, error in
        // workout saved to HealthKit
    }
}

Common Mistakes with HealthKit Integration

• Calling HealthKit API on the main actor without async/await—blocks the UI on slow queries to large datasets.
• Not checking HKHealthStore.isHealthDataAvailable()—HealthKit is unavailable on iPads without an Apple Watch.
• Reading heart rate in count/min units instead of HKUnit(from: "count/min")—results will be incorrect.

What's Included in the Work: Deliverables

• Integration code for reading and writing required data types.
• Permissions request screen with informational text.
• Handling of all edge cases (no data, denial, empty results).
• Background synchronization with the server via HKAnchoredObjectQuery.
• Documentation on working with HealthKit for your team.
• Consulting on passing App Store review.

Estimated Timelines

Cost is determined individually after analyzing your project. Order a consultation—we'll evaluate the scope and prepare a commercial proposal. Contact us to discuss the details of HealthKit integration into your app. We guarantee App Store review approval.

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.