AliveCor and PulseAI partner to bring cardiac AI beyond Apple Watch to Galaxy Watch and Fitbit
AliveCor and PulseAI announced on Nov. 16 a partnership to extend FDA-cleared ECG rhythm determinations from Apple Watch to Samsung Galaxy Watch, Fitbit Sense and Withings ScanWatch, rolling out to KardiaCare subscribers in the first half of 2027.
AliveCor and PulseAI announced on Nov. 16 a partnership to expand clinical-grade cardiac AI across mainstream consumer wearables, according to a joint release carried by GlobeNewswire and syndicated independently by BioSpace. PulseAI's FDA-cleared PulseAPI SmartWatch engine already analyzes Apple Watch ECG recordings to flag sinus rhythm, premature ventricular contractions, atrial fibrillation and abnormal heart rates inside AliveCor's Kardia App. Under the new deal, those same determinations will extend to Samsung Galaxy Watch, Fitbit Sense and Withings ScanWatch for KardiaCare subscribers starting in the first half of 2027.
The expansion matters because Galaxy Watch and Fitbit don't share Apple Watch's software stack. Samsung's line runs Google's Wear OS, and Fitbit sits inside Google's broader Android health ecosystem. Both are built on sensor APIs, permission models and background-process limits that differ from watchOS in ways that go well beyond a UI reskin. A rhythm-detection algorithm validated on one platform's raw sensor output doesn't automatically produce the same signal quality on another; someone has to re-validate the data pipeline against each OEM's accelerometer and PPG sensor behavior before the same clinical claim can ship on a second platform.
Why multi-OEM wearable integration is an Android engineering problem, not a porting job
Teams that treat "add Android support" as a straightforward port tend to discover that Wear OS's background execution limits, Health Connect permission flow, and per-OEM sensor-fusion quirks on a Galaxy Watch behave nothing like iOS's HealthKit. Getting a continuous-monitoring feature to a clinical-grade device like Fitbit Sense without degrading battery life or losing samples during a dropped Bluetooth connection is the kind of problem that needs dedicated Android development expertise, not a shared cross-platform shim bolted onto an iOS-first codebase.
What this means for digital-health teams planning multi-device launches
AliveCor and PulseAI's staged 2027 rollout, Apple first and Android-ecosystem devices second, is a common pattern in consumer health tech, but it leaves a real gap for any team hoping to launch on both platforms at once. A clinic software vendor or device maker planning a Wear OS companion app should budget for a separate validation pass on sensor data quality and a native engineering track, rather than assuming the iOS build will simply recompile for Android hardware with a different chipset and sensor suite underneath it.
Building a companion app for a medical wearable? Talk to Epica →
More from the blog.
Native vs. Cross-Platform: Choosing the Right Stack for Patient Apps
How to weigh native iOS/Android against a shared cross-platform codebase for a connected health app.
HealthKit App Store Rejections: What Clinic Apps Get Wrong
Why Apple's health-app review process trips up clinic teams, and how to pass it the first time.
Building regulated clinical software?
From EHR integration to agentic workflows, we build the software layer that holds up under real hospital IT constraints.