Who Builds Health Monitoring Companion Apps?

August 12, 2026

Companion apps for health monitoring devices are built by a mix of large consumer electronics companies, specialized health technology firms, and third-party developers. These apps are a critical component of the Internet of Medical Things (IoMT), connecting wearables to cloud platforms and clinical systems. Development must navigate a complex regulatory landscape, including FDA, HIPAA, and GDPR rules, especially if the app's intended use qualifies it as a medical device.

Key Players in Companion App Development

The development of companion apps for health monitoring devices is driven by a combination of established consumer electronics companies and specialized health technology firms. These entities create the software that interfaces with wearable sensors and other remote monitoring tools.

Consumer Electronics Giants

Many prominent consumer electronics companies are at the forefront of developing wearable devices and their accompanying mobile applications. These companies leverage their existing technological infrastructure and market reach to offer integrated health monitoring solutions.

Examples include:

Apple: Known for its smartwatches and integration with Apple HealthKit, a cloud platform for health data.
Fitbit: A key player in fitness trackers and smartwatches, offering companion apps for data visualization and analysis.
Garmin: Provides a range of wearable devices and associated apps for health and fitness tracking.
Huawei: Develops smartwatches and bands with companion apps for health monitoring.
Samsung: Offers smartwatches and other wearables that pair with mobile applications.
Withings: Produces various health monitoring devices, including smartwatches and blood pressure monitors, with companion apps.

Specialized Health Technology Companies

Beyond consumer electronics, companies focused specifically on health and medical devices also develop companion apps. These often cater to more specialized remote patient monitoring (RPM) systems and medical applications.

Examples include:

iHealth Labs Inc: Develops traditional pressure cuffs and pulse oximeters that transmit data remotely via companion apps.
Omron HeartGuide: Offers blood pressure monitoring devices with app integration.
Nonin Medical Inc (Onyx): Provides pulse oximeters that enable remote transmission of data.
Biofourmis: A cloud platform example that integrates with wearable devices for health data management.

The Internet of Medical Things (IoMT) Ecosystem

Companion apps do not exist in a vacuum; they are a central piece of a larger system known as the Internet of Medical Things (IoMT). This ecosystem involves four key roles that work together to get data from the patient to the clinician.

The Wearable Device: The sensor itself, which captures raw physiological signals.
The Connectivity Layer: The companion app on a smartphone, or a dedicated gateway, uses Bluetooth, Wi-Fi, or cellular data to transmit information securely.
The Data Platform: Cloud or on-premise services that receive, store, and process the data. Major platforms include Apple HealthKit, Google Fit, Microsoft Azure Health Data Services, and Amazon AWS HealthLake. This layer normalizes device-specific outputs into a standard format.
The Clinical Endpoint: The destination for the processed data, such as an Electronic Health Record (EHR) or a care management dashboard, where clinicians can review it and take action.

The companion app acts as the crucial bridge between the device and the data platform, attaching patient identifiers and timestamps before transmission. Successful integration across this ecosystem requires consistent data semantics, robust security, and clear workflow rules.

The Role of Companion Apps in Remote Patient Monitoring (RPM)

Companion apps are integral to the functionality of Remote Patient Monitoring (RPM) systems. They serve as a crucial link in the data journey, enabling the collection, transmission, and initial processing of health parameters from wearable devices.

Data Flow and Integration

The RPM pipeline relies on the companion app to facilitate a multi-step process that turns a sensor reading into a clinical action:

Signal Capture: Wearable devices use sensors (e.g., accelerometers, PPG sensors) to measure physiological parameters like SpO2 or heart rate.
Secure Transmission: The device or its companion app attaches timing and patient identifiers, then securely transmits the data via a smartphone or gateway to a cloud platform.
Normalization & Transformation: The platform converts device-specific outputs into a standardized observation structure suitable for a health record.
Event Flagging: The system analyzes the data, using rule-based logic or AI to compare new observations against baselines and flag potential health events.
Review & Action: A clinician reviews the flagged data on a dashboard or within the EHR, or an automated rule triggers an action, such as patient outreach or a medication adjustment.

Wearable Device Types and Monitored Parameters

Companion apps support a diverse range of wearable devices and monitor numerous health parameters, which are particularly valuable for managing chronic neurological and cardiovascular conditions.

Device Type	Common Parameters Monitored	Examples of Brands
Smartwatches	Acceleration, heart rate, SpO2	Apple, Samsung, Garmin
Wristbands	Acceleration, activity, sleep	Fitbit, Huawei, Misfit
Armbands	Heart rate, activity	Garmin
Straps	Various, depending on sensor	Generic, specialized
Blood Pressure Cuffs	Blood pressure	iHealth, Withings, Omron
Pulse Oximeters	SpO2, heart rate	iHealth, Onyx

Navigating the Regulatory Landscape

Developing a companion app for a health device involves significant regulatory scrutiny. Because software can directly impact patient health, bodies like the FDA, along with data privacy laws like HIPAA and GDPR, impose strict requirements.

Defining Software as a Medical Device (SaMD)

The first and most critical step for developers is classification. An app becomes a regulated medical product—known as Software as a Medical Device (SaMD)—based on its "intended use." If the app's marketing or specifications claim it can be used to support diagnosis, treatment, or prevention of a disease (e.g., an algorithm that flags stroke risk or guides medication dosing), it will be treated as a medical device by regulators.

Key Regulations and Compliance

FDA (U.S. Food and Drug Administration): Treats health software as a medical device if it meets the SaMD criteria, requiring developers to provide evidence of its safety and effectiveness. The FDA is actively working to streamline the evaluation of software-based devices, including those using VR/AR, while maintaining safety checks.
HIPAA (Health Insurance Portability and Accountability Act): This U.S. law focuses on protecting patient health information (PHI). Apps that store or transmit PHI must implement safeguards like access controls, data encryption (in transit and at rest), and auditable activity logs.
GDPR (General Data Protection Regulation): In the European Union, GDPR mandates the lawful and transparent processing of personal data. This includes obtaining user consent, minimizing data collection, and upholding user rights to access or delete their information.

The Regulatory Pathway

For apps classified as SaMD, the development process must follow a formal regulatory pathway. This typically includes establishing a robust quality management system, generating clinical evidence to support the app's claims, and conducting post-market monitoring to ensure continued safety and performance after release.

Challenges in Development and Adoption

While companion apps significantly enhance health monitoring, developers and users face several challenges.

Medical Certification: Most consumer-grade wellness devices and their apps lack formal medical certification, limiting their use in clinical decision-making.
Data Quality and Standardization: Data accuracy can vary between devices, and connectivity issues can create gaps in monitoring. Integrating data from multiple sources into a single, standardized format for EHRs remains a major technical hurdle.
User Adoption and Engagement: For RPM to be effective, patients must consistently and correctly use their devices and apps. Challenges in usability, motivation, and technical literacy can lead to poor adoption and engagement, undermining the system's value.

Frequently Asked Questions

What is the primary function of a companion app for health monitoring devices?

A companion app's primary function is to collect, transmit, and often analyze health data from wearable devices, making it accessible for users and, in RPM systems, for healthcare providers.

Which major companies develop these companion apps?

Major companies developing these apps include consumer electronics giants like Apple, Fitbit, Garmin, Huawei, and Samsung, as well as specialized health technology companies such as iHealth and Withings.

What makes a health app a regulated medical device?

A health app is regulated as a medical device based on its "intended use," specifically if it makes claims related to diagnosing, treating, or preventing a disease or condition.

How do companion apps integrate with healthcare systems?

Companion apps transmit data to cloud platforms like Apple HealthKit or AWS HealthLake, which normalize the data and route it to clinical endpoints like an Electronic Health Record (EHR) for provider review.

What types of health parameters do these apps help monitor?

These apps help monitor a wide range of health parameters, including acceleration, heart rate, blood pressure, peripheral oxygen saturation (SpO2), and activity levels, often using various sensors embedded in wearable devices.

Are all companion apps for health monitoring medically certified?

No, most consumer-grade wellness devices and their companion apps lack medical certification, though some specialized medical devices and their software are certified for clinical use.

Conclusion

Companion apps for health monitoring are built by a dynamic mix of consumer technology giants and dedicated health-tech firms. These apps are not standalone products but essential connectors within the broader Internet of Medical Things (IoMT) ecosystem, linking personal devices to powerful cloud platforms and clinical workflows. Their development is governed by a stringent regulatory environment, where the app's intended use determines its classification as a medical device subject to FDA oversight and data privacy laws like HIPAA. While challenges in data quality, user engagement, and system integration persist, these apps are fundamental to the evolution of remote patient monitoring and personalized healthcare.

Sources & References

Want to actually learn Who Builds Health Monitoring Companion Apps?

Curo turns topics like this into a personalized, guided learning board - built around what you already know. Free to start.

Try Curo