Contact person: Cross-Platform Health Data SDK

Phone:Show

Email:Show

Location: Redmond, United States

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"I want a lightweight, production-ready SDK that gives any iOS or Android app instant, secure access to the user’s native health store and then ships that data straight to my backend. On iOS this means seamless HealthKit integration; on Android it must plug into Google Health Connect. Configuration on the host app side should be minimal—ideally a few lines of code plus an API key—while the SDK handles permission prompts, background sync, error handling, and offline queuing automatically.

The SDK must be able to both read and write the following record types:

• Activity and fitness data
• Heart rate and other vitals
• Nutrition and dietary information

Core expectations
• One common, well-documented API surface that feels native in Kotlin and Swift/Objective-C.
• Automatic mapping of platform-specific units to a unified schema before transmission.
• Configurable sync interval with sensible defaults, plus a manual “force sync” method.
• End-to-end encryption for data in transit and local-store encryption at rest.
• Clear handling of user consent and revocation in line with Apple and Google policy guidance.
• Built-in logging that can be toggled for debug or production modes.

Deliverables
1. Android artefact (.aar) distributed via Maven/Gradle and an iOS xcframework distributed via Swift Package Manager.
2. A sample app for each platform showing integration, custom permission flows, and data visualisation.
3. Comprehensive README / API reference covering setup, configuration options, and troubleshooting.
4. Unit and instrumentation tests with ≥80 % coverage plus CI workflow scripts.
5. Postman collection or curl examples for the server endpoints the SDK hits.

Acceptance criteria
• A test app can obtain read-write permissions, log 10 000+ records offline, and sync them once connectivity returns with zero data loss.
• Switching a single feature flag disables write operations while preserving reads without app rebuild.
• Apple App Store and Google Play pre-check tools show no privacy or permission warnings.

Tech preferences
• Kotlin, Coroutines, Jetpack libraries on Android; Swift 5+, Combine (where useful) on iOS.
• HTTP layer built on OkHttp/Ktor (Android) and URLSession (iOS) with protobuf or JSON selectable at compile time.

Once these pieces are in place I’ll run a brief beta with two partner apps; after their feedback I may ask for a follow-up milestone to add additional data types, so writing modular code from the start is essential." (client-provided description)