Service · App development

Custom wearable app development.

A native watch app, AR glasses or medical wearable device with a companion app and cloud backend. We build wearable software for smartwatches, fitness trackers, industrial headsets and clinical sensors, with attention to battery life, privacy and reliable BLE integration.

watchOS & Wear OSBLE pairingHealth dataAR glasses

A wearable app is not a miniature version of your mobile app.

An Apple Watch has a tiny screen, a HoloLens can't see anything, and a continuous glucose sensor has a battery that has to last for months. So the design doesn't start with the UI. It starts with the question: which moment in the wearer's workflow should the wearable really improve? Which three actions may take no more than two taps? Which data may the wearable process locally and what goes to the cloud? What happens if the Bluetooth connection drops in the middle of a measurement?

Wearable development sits at an intersection. It resembles mobile development because it involves mobile operating systems (watchOS, Wear OS, stripped-down Android variants on industrial devices), but in practice it is closer to embedded development: small screens, limited processing power, low-power sensors and strict battery budgets. At the same time, a wearable is never an island. There is always a phone companion and a cloud backend behind it, and often a connection to a primary system such as an EHR, WMS or CRM.

We build wearable software for clients in healthcare, sport, industry and logistics. Native where it makes sense (watchOS in Swift, Wear OS in Kotlin, Garmin Connect IQ in Monkey C), cross-platform where possible, and always with a companion app and cloud backend so the wearable fits into a larger whole. A wearable project combines firmware thinking, mobile app architecture and API integration, and that is exactly where we stand out as an app developer.

Three categories of wearable apps we build.

Wearables differ greatly in function and target group. Based on your use case, we advise which type fits, and which wearable hardware suits it best.

Consumer wearables · sport, lifestyle, coaching

Smartwatch and fitness app

Native apps for Apple Watch, Wear OS devices (Samsung Galaxy Watch, Pixel Watch, Mobvoi TicWatch) and Garmin Connect IQ. Workout tracking, heart rate and recovery data, sleep analysis, coaching flows and complications that put the relevant metric on the watch face. With a companion app, accounts and cloud history so that trends can be followed by a coach, sports physician or the users themselves. For Fitbit, Whoop and Oura we build the companion app and cloud layer. Their devices are closed ecosystems on which third-party watch apps are not possible.

watchOSWear OSGarminComplications
Medical & clinical wearables · healthcare, RPM, elderly care

Medical-grade wearable app

Software for continuous glucose monitors, wearable ECG patches, heart-rate bands and fall-detection devices. Remote patient monitoring for primary or secondary care, medication reminders, alerts for abnormal readings and integration with EHRs via HL7 FHIR and Vecozo for clinical context. Privacy and regulation are central here, not an afterthought: a wearable app that supports treatment decisions falls under CE-MDR and requires demonstrable risk management, clinical evaluation and a software lifecycle in line with IEC 62304.

RPMHL7 FHIRNEN 7510CE-MDR
Industrial & AR wearables · warehouse, factory, field service

Industrial wearable and AR app

Hands-free apps for ring scanners and pick-by-voice in the warehouse, helmet-camera streaming for remote experts, and AR instructions on HoloLens, Magic Leap, Vuzix or RealWear. We build on the Android flavour of industrial wearables (often a stripped-down AOSP build with a device-specific SDK) and on Unity for AR headsets, with a direct integration to your WMS, MES or API layer. BLE tags and handheld scanners for retail also fall under this: proximity flows, mobile POS belts and assistant displays for shop staff.

HoloLensVuzixRealWearUnity / WebXR

What you get at the end of the project.

A wearable app is never a standalone piece of software. We deliver a complete stack that you can manage and develop further yourself.

  • The native wearable appFor watchOS, Wear OS, Connect IQ or your chosen industrial/AR flavour. With complications, quick actions and an offline mode where the hardware allows it.
  • Companion phone appiOS and Android app for onboarding, BLE pairing, settings, data history and alerts. The place where the wearer configures what the wearable does.
  • Cloud backend & data pipelineIngestion of sensor data, time-series storage, analytics and, where needed, ML models for pattern detection or anomaly alerts. Including an admin dashboard.
  • Integrations with your systemsEHR or care-system integrations via HL7 FHIR and Vecozo for clinical context, or WMS/ERP/CRM for industrial wearables. We document every integration.
  • Source code, store listings and runbookFull code in your repository, App Store and Google Play set up on your developer accounts, plus an operational runbook for your IT or DevOps team.
  • Maintenance contract (optional)Ongoing monitoring of crash rates, BLE reliability and backend uptime, plus security patches and further development on a fixed sprint cadence.

When a wearable app is the right choice.

Four patterns in which a wearable adds significantly more value than a mobile app or dashboard. If you recognise your situation, we'd be happy to talk further.

Healthcare

Remote patient monitoring

Chronic patients, oncology aftercare or postoperative pathways where you want to see vital signs daily without the patient having to come back in. A wearable plus RPM platform reduces outpatient pressure, flags deterioration earlier and gives the care team a continuous picture instead of a snapshot per consultation. Important for adherence: minimal patient interaction, automatic sync, and alerts that don't lead to alarm fatigue.

Sport & fitness

Coaching backed by data

You provide training guidance, recovery coaching or medical sports care and want objective workout, heart-rate and recovery data from your clients, rather than relying solely on self-reporting or generic consumer apps. With your own wearable app, data, branding and coaching flow stay within your platform, and you can offer new services such as recovery monitoring or progression coaching based on reliable measurements.

Industry & logistics

Hands free in the workflow

Warehouse pickers, factory technicians and field engineers need their hands free for the physical task. A ring scanner, helmet camera or AR headset replaces the mobile scanner or paper work order without interrupting the workflow. Pick-by-voice on a Wear OS device, AR instructions in a HoloLens, or remote-expert sessions where someone watches along through Vuzix glasses: we can build all of these. Pairs well with our field service apps.

Safety & elderly care

Detecting risk moments

Fall detection for the elderly, lone workers with an alarm button on their smartwatch, or helmet-mounted sensors in defence and security. The wearable becomes a passive safety layer that makes manual reporting unnecessary: the wearer doesn't have to do anything, the system detects it itself. For situational-awareness scenarios, we connect the sensor data to a central dashboard so a commander or care coordinator has real-time insight.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

How a wearable project works with us.

1

Introduction & hardware choice

A conversation in which we work out who will be wearing the device, which data matters and which wearable hardware suits that best. Apple Watch, Wear OS, Garmin, a medically approved device or an industrial headset: this choice has a big impact on the rest of the project.

2

User research & technical scope

Field observations with 3-5 future users, a workshop with your team, and a technical deep dive into BLE protocols, battery budget and the cloud architecture. At the end you get a concrete scope, a plan and the first interaction flows on the wearable screen.

3

Sprint-based build

We work in short sprints, with a testable build on real hardware in every iteration. You test along, and so do end users. We start with the most critical flow and build outwards from there, so we can validate early what works and what doesn't.

4

App store, certification & rollout

Submission to the App Store, Google Play or the relevant MDM distribution for industrial devices. For medical wearables: CE-MDR or CE-IVDR preparation together with a notified body. After that, a phased rollout to your user group with support on standby during the first sprints.

5

Maintenance & further development

Ongoing monitoring of crash rates, BLE stability and backend performance. We keep up with new watchOS and Wear OS versions so the app doesn't drop out of the store. Continued development on a fixed sprint cadence.

Frequently asked questions.

What clients typically ask us before we start a wearable project.

Apple Watch or Wear OS: which is the best platform to build on?
It depends on your target audience and your existing mobile app. Apple Watch has a strong health framework (HealthKit), a more loyal user base and better-integrated complications, but only works with iPhones. Wear OS (Samsung, Google, Mobvoi) has a growing share, covers Android users and offers more hardware choice. For consumer and lifestyle apps, we often recommend both. For a closed population (clinical research, a sports team, an internal workforce), a single platform is more efficient.
Which programming languages and frameworks do you use?
For watchOS, we build natively in Swift with SwiftUI and WatchKit. For Wear OS, we write in Kotlin with Jetpack Compose for Wear. Garmin Connect IQ requires Monkey C, a proprietary language. For AR wearables such as HoloLens or Magic Leap, we work in Unity, sometimes WebXR for lighter experiences. Cross-platform Flutter for wearables has limitations around complications and background sensors, so for health or industrial apps we tend to choose native.
We want to bring a medical wearable product to market: what do we need to arrange?
Software on a medical device falls under CE-MDR (Medical Device Regulation), or CE-IVDR for in-vitro diagnostics. The software class determines how demanding the process is: a wellness tracker is a different matter from a sensor that supports treatment decisions. We work with your regulatory team or an external consultant on the technical documentation (IEC 62304), risk management (ISO 14971) and the clinical evaluation. NEN 7510 and the GDPR go hand in hand if you process patient data. See also our healthcare software practice.
How do you make sure the battery doesn't run flat within half a day?
The battery budget is a design decision, not an optimisation after the fact. We measure early on real hardware to see which functions cause the biggest drain: continuous BLE connection, GPS, screen wake, sensor polling. The typical techniques: syncing intermittently instead of streaming continuously, low-power modes with cached state, sensor fusion so we need to sample less often, and shifting work to the phone where possible. For clinical devices, we also build hardware-side firmware recommendations into the design.
How reliable is the BLE connection between wearable and phone?
BLE is robust, but not always predictable. Disconnects happen in lifts, in MRI environments, when hands are full or batteries are weak. We design every wearable app on the assumption that the connection can drop at any moment: local buffering on the device, retry logic with backoff, conflict resolution when both sides have been updated, and clear UI feedback on the connection state. For industrial and healthcare contexts, we also run explicit reliability tests on site.
Can you also handle AR glasses such as HoloLens or Magic Leap?
Yes. For AR wearables, we work in Unity with Microsoft's MRTK toolkit or the respective SDKs for Magic Leap and Apple Vision Pro. Use cases we come across regularly: AR work instructions for technicians or operators, remote-expert sessions where a specialist watches through the glasses, and visualisation of 3D data from an ERP or digital twin. We treat Vuzix and RealWear as Android devices with a UX adapted for voice control, which is a different class from immersive AR.
How do you handle health data and privacy?
Health data is special category personal data under the GDPR and requires strict data processing agreements. We apply privacy by design: minimising what the wearable stores and sends, end-to-end encryption where possible, explicit opt-in flows and logging that meets NEN 7510. For healthcare organisations, we sign a data processing agreement and carry out a DPIA at the start. We do not store patient data in our own environments unless that is explicitly part of the scope.
What determines the cost and lead time?
The biggest factors: the number of wearable platforms (watchOS-only is cheaper than watchOS + Wear OS + Garmin), whether a new companion app has to be built or an existing app extended, how many sensor types and cloud integrations are added, and whether certification (CE-MDR) is part of the scope. A well-defined smartwatch app with a companion is a project of a few sprints; a full medical wearable stack with clinical integration is a project of multiple sprints. We're happy to work out an initial indication during our first conversation.
An existing wearable from the market, or design your own hardware?
In most cases, we advise first checking whether an existing wearable (Apple Watch, Garmin, a certified medical sensor from Withings or Cardiomo, an industrial headset from RealWear) covers your use case. Hardware development is a discipline of its own, with its own risks. Only if existing products truly fall short do we look at custom hardware together with a hardware partner, while we focus on the firmware interface, the companion app and the cloud platform.

Talk to us about your wearable app.

A free, no-obligation 30-minute introduction. We listen to your use case, who will wear the device and the data that matters — and give you direction on hardware, platform choice and architecture that you can act on straight away. Wearables often overlap with our work on IoT apps, so we bring that context along too.

Edit content