Service · App development

Custom wearable app development.

A native watch app, AR headset 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 sees nothing, and a continuous glucose sensor needs a battery that lasts months. The design therefore does not start with the UI; it starts with the question: which moment in the wearer's workflow does the wearable really need to improve? What are the three actions that must take no more than two taps? Which data may the wearable process locally, and what goes to the cloud? What happens when 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, frugal sensors and tight battery budgets. At the same time, a wearable is never an island. There is always a phone companion, a cloud backend and often an integration with a primary system such as an EHR, WMS or CRM behind it.

We build wearable software for clients in healthcare, sport, industry and logistics. Native where it matters (watchOS in Swift, Wear OS in Kotlin, Garmin Connect IQ in Monkey C), cross-platform where that makes sense, 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 precisely where we distinguish ourselves as an app developer.

Three categories of wearable apps we build.

Wearables differ greatly in function and audience. Based on your use case, we advise which type fits best, 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 surface the relevant metric on the watch face. With a companion app, accounts and cloud history so trends can be reviewed by a coach, sports doctor or the user themselves. For Fitbit, Whoop and Oura, we build the companion app and cloud layer, as 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 and secondary care, medication reminders, alerts for abnormal readings, and integration with the EHR 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 software lifecycle processes 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 direct integration into your WMS, MES or API layer. This also covers BLE tags and handheld scanners for retail: proximity flows, mobile POS belts and assistant displays for shop staff.

HoloLensVuzixRealWearUnity / WebXR

What you receive 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 the chosen industrial/AR flavour. With complications, quick actions and offline mode where the hardware allows.
  • 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 any 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 setup 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 where a wearable adds significantly more value than a mobile app or dashboard. If you recognise your situation, we would be happy to talk further.

Healthcare

Remote patient monitoring

Chronic patients, oncology aftercare or post-operative pathways where you want to see vital parameters 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 rather than a snapshot per consultation. Important for adherence: minimal interaction required from the patient, automatic sync, and alerts that do not lead to alarm fatigue.

Sports & fitness

Coaching with data evidence

You provide training guidance, recovery coaching or sports medicine 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 a dedicated wearable app, data, branding and the 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 or field engineers need their hands for the physical task. A ring scanner, helmet camera or AR headset replaces the handheld scanner or paper work order without interrupting the workflow. Voice-directed picking on a Wear OS device, AR instructions on a HoloLens, or remote expert sessions where someone follows along through a Vuzix headset: these are all things we can build. Connects with our field service apps.

Safety & elderly care

Detecting risk moments

Fall detection for older people, lone workers with an alarm button on the smartwatch, or helmet-mounted sensors in defence and security. The wearable becomes a passive safety layer that makes manual alerts unnecessary: the wearer does nothing, the system detects on its own. For situational-awareness scenarios, we link the sensor data to a central dashboard so a commander or care coordinator has real-time insight.

Not yet sure about a large project?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we turn your idea into something tangible in one day for €1,150, so you can see whether further development is worth the investment. Decide to go ahead with the full build? Then we credit the full cost.

Explore OneDayBuild →

How a wearable project works with us.

1

Introduction & hardware selection

A conversation in which we establish who will be using the wearable, which data matters, and which wearable hardware best suits that. Apple Watch, Wear OS, Garmin, a medically approved device or an industrial headset: this choice shapes much of the rest of the project.

2

User research & technical scope

Veldobservaties met 3-5 toekomstige gebruikers, een workshop met uw team, en een technische verdieping op BLE-protocollen, batterij-budget en de cloud-architectuur. Aan het eind een concrete scope, planning en de eerste interactie-flows op het wearable-scherm.

3

Sprint-based build

We work in short sprints, with each iteration producing a testable build on real hardware. You test along with us, 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: preparation for CE-MDR or CE-IVDR certification together with a notified body. Followed by a phased rollout to your user group, with support on call during the first sprints.

5

Maintenance & further development

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

Frequently asked questions.

What clients usually ask us before starting a wearable project.

Apple Watch or Wear OS: which is the better platform to build on?
It depends on your target audience and your existing mobile app. Apple Watch has a strong health framework (HealthKit), a loyal user base and better integrated complications, but only works with iPhones. Wear OS (Samsung, Google, Mobvoi) has a growing market 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, its own language. For AR wearables such as HoloLens or Magic Leap we work in Unity, and sometimes WebXR for lighter experiences. Cross-platform Flutter for wearables has limitations around complications and background sensors, so for health or industrial apps we generally recommend a native approach.
We want to bring a medical wearable product to market. What do we need to arrange?
Software on a medical device falls under the CE MDR (Medical Device Regulation) or, for in vitro diagnostics, the CE IVDR. The software class determines the level of effort: a wellness tracker is very different 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 are inseparable 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?
Battery budget is a design decision, not an afterthought. We measure early on real hardware which features cause the biggest drain: continuous BLE connection, GPS, screen wake-ups, sensor polling. The typical techniques: intermittent syncing instead of a continuous stream, low-power modes with cached state, sensor fusion so we need to sample less often, and moving work to the phone where possible. For clinical devices, we also build hardware-side firmware recommendations into the design.
How reliable is BLE connectivity between a wearable and a phone?
BLE is robust but not always predictable. Disconnects happen in lifts, in MRI environments, when hands are full or batteries are low. 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 about connection state. For industrial and care settings, we add explicit reliability tests on location.
Can you also work with AR glasses such as HoloLens or Magic Leap?
Yes. For AR wearables we work in Unity, using Microsoft's MRTK toolkit or the respective SDKs from Magic Leap and Apple Vision Pro. Use cases we encounter often include AR work instructions for engineers or operators, remote expert sessions where a specialist sees what the wearer sees through the glasses, and visualisation of 3D data from an ERP system or digital twin. We treat Vuzix and RealWear as Android devices with a custom UX for voice control, which is a different category from immersive AR.
How do you handle health data and privacy?
Health data is special category personal data under the GDPR and requires strict processor agreements. We apply privacy by design: minimising what the wearable stores and transmits, end-to-end encryption wherever possible, explicit opt-in flows, and logging that complies with 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 timeline?
The main factors are: the number of wearable platforms (watchOS only is cheaper than watchOS plus Wear OS plus Garmin), whether a new companion app needs to be built or an existing app extended, how many sensor types and cloud integrations are involved, and whether certification (CE MDR) is part of the scope. A 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 several sprints. We are happy to give you a first indication during an introductory conversation.
An existing wearable from the market, or designing your own hardware?
In most cases, we recommend first checking whether an existing wearable — an Apple Watch, a Garmin, a certified medical sensor from Withings or Cardiomo, or an industrial headset from RealWear — covers your use case. Hardware development is a specialist discipline with its own risks. Only when existing products genuinely fall short do we look into custom hardware 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 thirty-minute introductory call. We listen to your use case, the wearer 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.

Edit content