--- title: "Apple Health Integration Without an App" description: "A ready iOS and Android app, under your brand, that brings Apple Health, Health Connect and wearable data into your own Open Wearables deployment." canonical_url: "https://openwearables.io/platform/connect-app" --- # Your own app for Apple Health and wearables, without building one Connect App A ready iOS and Android app for care programmes, remote monitoring and research teams with no app of their own. People join from an invitation, connect their phone and wearables once, and every reading lands in the deployment you run, under your name in the stores. [Book a demo](https://openwearables.io/book?tier=programme) [See pricing](https://openwearables.io/pricing#modules) Trusted by teams building on Open Wearables - Heart Monitor logo - Hundred logo - JustGains logo - Lifelong logo - MoveTogether logo - Suna logo - Yoboo logo Why it exists ## Apple Health and Health Connect have no web API, so the data needs an app on the phone For a team on a web portal or a care dashboard, that usually means a mobile team, store reviews and SDKs to keep current. Connect App is that app, already built and maintained by the team behind Open Wearables. ### On the phone People allow access once, on the phone's own permission sheet, and the app keeps syncing in the background. ### On your deployment Phone and wearable data land in one schema, in the cloud account you run. ### In your backend Webhooks and the REST API deliver it like every other source. How it works ## How the Apple Health integration works 01 Invite ### Each person gets a link or a QR code Send it by email or text, or hand it over at the first visit. One tap opens the app on your programme, with nothing to sign up for. 02 Confirm ### They see your name and choose what to share Your organisation comes first, then the phone's own permission sheet. Nothing is shared until they agree. 03 Connect ### Their phone and wearables, connected once Apple Health or Health Connect, plus any wearable accounts you enabled. After that, the app syncs in the background and they can forget about it. 04 Receive ### Readings arrive in your backend Each new reading reaches your webhook as it lands, and the REST API holds the full history for every person. What you get ## A patient app without a mobile team ### Your brand in the stores Your name, icon and colours on your own App Store and Google Play accounts, so people install an app from an organisation they know. - White-label - Your store accounts ### Joining without accounts People join from your invitation, with no sign-up form and no password to remember. Each invitation works once. - Link or QR - Single-use ### Provider passwords stay off the phone People sign in to Garmin or Oura on the provider's own page, and your deployment keeps the access tokens. - Provider sign-in - Tokens on your deployment ### One health data API Phone and wearable readings share one schema, so your backend handles a person rather than a device. - Webhooks - REST API Who it is for ## Teams that need phone health data and have no app to collect it Already have a mobile app? Add our Flutter, React Native, iOS or Android SDK to it instead. [Mobile SDKs](https://openwearables.io/platform/mobile-sdks) [For hospitals](https://openwearables.io/for/hospitals-telemedicine) ### Remote patient monitoring Readings from home for clinicians, in an app that carries the provider's name. [Learn more](https://openwearables.io/for/remote-patient-monitoring) ### Clinical research Participants enrolled with a QR code at the first visit, on infrastructure the sponsor has approved. [Learn more](https://openwearables.io/for/clinical-research) ### Employer wellness Members bring the devices they already own into a programme app in your colours. [Learn more](https://openwearables.io/for/employer-wellness) ### Care providers Care programmes that need their patients' phone and wearable data between visits, with no app of their own. [Learn more](https://openwearables.io/for/care-providers) Plans ## Start free, then put it under your name One person counts once, however many devices they link. [01] On every plan ### Connect App The app under the Open Wearables name, on every plan. - Up to 5 users on Core, no limit on Pro - Every source your instance enables - Same instance when you move to your brand [Book a demo](https://openwearables.io/book) [02] Your programme, your brand ### Connect App under your brand The same app published under your brand, $5,000 per platform. - Your App Store and Google Play accounts - Your name, icon and colours - No user limit [Book a demo](https://openwearables.io/book?tier=programme) How it compares ## Where the data goes, and whose name is on the app Two questions decide most choices here: where health data ends up, and what it takes to put an app in front of people. | | A hosted extraction app | Build your own app | Connect App | | --- | --- | --- | --- | | [01] Where the data is stored | In the vendor's cloud | In your cloud | In your own Open Wearables deployment | | [02] Name people see | The vendor's | Yours | Yours, on your own store accounts | | [03] What it takes | An account and the vendor's terms | A mobile team, store reviews and SDK upkeep | Open Wearables running, and the app set up with us | | [04] Choose this when | Speed matters more than where the data lives | The app is your product and the mobile team exists | You need phone data under your name without hiring for mobile | ## One app, whatever people wear The phone's health store plus the providers you switch on. Each lands in the same schema, so a reading looks the same whichever device took it. [Browse integrations](https://openwearables.io/integrations) - [Garmin integration](https://openwearables.io/integrations/garmin) - [Whoop integration](https://openwearables.io/integrations/whoop) - [Oura integration](https://openwearables.io/integrations/oura) - [Polar integration](https://openwearables.io/integrations/polar) - [Suunto integration](https://openwearables.io/integrations/suunto) - [Withings integration](https://openwearables.io/integrations/withings) - [Strava integration](https://openwearables.io/integrations/strava) - [Ultrahuman integration](https://openwearables.io/integrations/ultrahuman) - [SensorBio integration](https://openwearables.io/integrations/sensorbio) - [Google Health API integration](https://openwearables.io/integrations/google-health) - [Fitbit integration](https://openwearables.io/integrations/fitbit) - [Apple Health integration](https://openwearables.io/integrations/apple-health) - [Google Health Connect integration](https://openwearables.io/integrations/google-health-connect) - [Samsung Health integration](https://openwearables.io/integrations/samsung-health) ## Put Connect App under your name We set up an instance with you and walk through the full path: invitation, consent, first sync and the data arriving in your backend. [Book a demo](https://openwearables.io/book?tier=programme) [See pricing](https://openwearables.io/pricing#modules) FAQ ## What teams ask about the Connect App ### Does Apple Health have an API? Not on the web. HealthKit is an on-device framework: only an app on the iPhone, with the person's permission, can read it. Connect App is that app, and it sends the readings to your deployment. The [Apple Health integration](https://openwearables.io/integrations/apple-health) page covers the data types. ### What is Health Connect? Android's on-device store for health and fitness data. Apps and wearables write to it, and another app reads from it with the person's permission. Like Apple Health, it has no web API, so Connect App reads it on the phone. ### Can a web app access Apple Health data? Not directly, because the data never leaves the phone on its own. A web-only product needs an app on the phone to read it and pass it on, which is the job Connect App does. ### Can we publish it under our own brand? Yes. The Connect App under your brand carries your name, icon and colours on your own App Store and Google Play accounts, with no user limit. It costs $5,000 per platform, iOS or Android. ### Do people need to create an account? No. They open your invitation, see your organisation's name, pick their sources and tap Connect. ### Where does the data go? Straight from the phone or the provider to your Open Wearables deployment, in your cloud account and the region you choose. ### Is there a free version? Yes. The standard app, under the Open Wearables name, is free on Core for up to 5 users, and has no user limit on Pro. Teams often start with it before launching under their own brand. ### We already have a mobile app. Do we need this? No. Add our [mobile SDKs](https://openwearables.io/platform/mobile-sdks) to the app you have. ### What does registering our instance share? Registration is only needed for the app from the App Store and Google Play. It shares a random instance ID, a public key and, if you add one, an admin email. Never health data, user names or your server address. It is opt-in and you can withdraw it at any time.