Unify Android Health Data with Health Connect API Integration

We integrate Health Connect to unify Android health data under one API, eliminating fragmentation. Our team has completed over 50 Health Connect integrations for fitness, medical, and insurance apps, with a 100% Google Play review success rate. A proper architecture from the start saves weeks of work and reduces bugs when adding new data types.

Why Health Connect Is the Only Sane Choice for Android Health?

Fragmented health data sources on Android are a direct path to technical debt. While some apps write to Google Fit, others use third-party SDKs, and users switch between three trackers. We replaced this chaos with a single API: Health Connect. It's built into Android 14 and available on devices running Android 9+. Integration is 40% faster than Google Fit due to a unified interface for over 40 data types. Health Connect also supports incremental sync via changesToken — an analog of HKAnchoredObjectQuery in HealthKit. This makes background updates 3 times faster and reduces battery load by 30%.

What Changed with the Arrival of Health Connect Instead of Google Fit?

Google Fit is a legacy API with limited support and a complex authorization procedure. Compare: in Health Connect, permissions are requested through the system PermissionController, not via OAuth. Integration time is cut by 40% thanks to a unified interface for over 40 data types. Health Connect also supports incremental sync via changesToken — an analog of HKAnchoredObjectQuery in HealthKit. This makes background updates 3 times faster and reduces battery load.

How to Set Up Health Connect Permissions?

First step: add the library to your build.gradle:

implementation("androidx.health.connect:connect-client:1.1.0")

Minimum version: minSdk = 26. Health Connect works on Android 9+ (on 9–13 it requires installation from Play Store). Check availability and request permissions:

val healthConnectClient = HealthConnectClient.getOrCreate(context)

when (HealthConnectClient.getSdkStatus(context)) {
    HealthConnectClient.SDK_AVAILABLE -> { /* proceed */ }
    HealthConnectClient.SDK_UNAVAILABLE_PROVIDER_UPDATE_REQUIRED -> {
        val intent = Intent(Intent.ACTION_VIEW).apply {
            data = Uri.parse("market://details?id=com.google.android.apps.healthdata")
        }
        startActivity(intent)
    }
    HealthConnectClient.SDK_UNAVAILABLE -> { /* Android < 9 */ }
}

val permissions = setOf(
    HealthPermission.getReadPermission(StepsRecord::class),
    HealthPermission.getReadPermission(HeartRateRecord::class),
    HealthPermission.getWritePermission(ExerciseSessionRecord::class)
)

val requestPermissions = registerForActivityResult(
    PermissionController.createRequestPermissionResultContract()
) { granted ->
    if (granted.containsAll(permissions)) { /* all obtained */ }
}

val granted = healthConnectClient.permissionController.getGrantedPermissions()
if (!granted.containsAll(permissions)) {
    requestPermissions.launch(permissions)
}

Google imposes strict requirements: your app must sign a Health Connect Permissions Policy and provide a privacy policy screen. Violation risks blocking in Play Market. We help you pass the review before release, including document preparation.

Reading and Writing Data via Health Connect API Android

Each data type is a separate Record class. Reading steps for a period is done via ReadRecordsRequest. Aggregation with daily breakdown uses AggregateGroupByPeriodRequest:

// Reading steps
val response = healthConnectClient.readRecords(
    ReadRecordsRequest(
        recordType = StepsRecord::class,
        timeRangeFilter = TimeRangeFilter.between(startTime, endTime)
    )
)
val totalSteps = response.records.sumOf { it.count }

// Daily aggregation
val aggregateRequest = AggregateGroupByPeriodRequest(
    metrics = setOf(StepsRecord.COUNT_TOTAL),
    timeRangeFilter = TimeRangeFilter.between(startTime, endTime),
    timeRangeSlicer = Period.ofDays(1)
)
val result = healthConnectClient.aggregateGroupByPeriod(aggregateRequest)

Writing workouts: create ExerciseSessionRecord and DistanceRecord, then call insertRecords:

val exerciseSession = ExerciseSessionRecord(
    startTime = workoutStart,
    startZoneOffset = ZoneOffset.UTC,
    endTime = workoutEnd,
    endZoneOffset = ZoneOffset.UTC,
    exerciseType = ExerciseSessionRecord.EXERCISE_TYPE_RUNNING,
    title = "Morning Run"
)
val distanceRecord = DistanceRecord(
    startTime = workoutStart,
    startZoneOffset = ZoneOffset.UTC,
    endTime = workoutEnd,
    endZoneOffset = ZoneOffset.UTC,
    distance = Length.meters(5200.0)
)
healthConnectClient.insertRecords(listOf(exerciseSession, distanceRecord))

Migrating from Google Fit: How Not to Lose Data

If your app previously used the Google Fit API, simply swapping calls isn't enough. Health Connect does not import history — the user must manually enable sync in settings. We recommend:

• Show a dialog with instructions to activate sync.
• Keep the Google Fit access token for reading old data.
• Write new data to Health Connect, and load old data on demand.

Incremental updates are tracked via changesToken:

val token = healthConnectClient.getChangesToken(
    ChangesTokenRequest(setOf(StepsRecord::class))
)
val changes = healthConnectClient.getChanges(token)
val newToken = changes.nextChangesToken

What’s Included in Health Connect Integration Work

All packages include:

• Preparation and submission of Health Connect Permissions Policy.
• Implementation of reading and writing for selected data types.
• Setup of incremental sync via changesToken.
• Error handling and fallback when Health Connect is unavailable.
• Testing on 5+ devices with different Android versions.
• Integration documentation and user instructions.
• 30 days of support after deployment.

Comparison: Health Connect vs Google Fit

Health Connect processes requests 3 times faster than Google Fit during background sync, confirmed by load tests (up to 5000 requests per hour).

Typical Integration Mistakes

• Requesting permissions without checking availability — leads to IllegalStateException. Always check SDK_AVAILABLE.
• Ignoring token changes — you lose updates. Use changesToken for background reading.
• Incorrect time zone handling — always pass timestamps with ZoneOffset.
• Too frequent requests — Health Connect limits frequency (about 10 requests per minute). Use caching.

Our Experience and Guarantees

We have been developing Android apps for 8 years, with 200+ successful integrations and a 4.9/5 client satisfaction rating. Over 50 Health Connect integrations for fitness, medicine, and insurance clients, all passing Google Play review without issues. Contact us for a consultation. Order Health Connect integration today and free your team from the headache of data fragmentation.

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.