Healthtech Software Development: Apps, Devices and Backends

Software around medical and wellness devices

A medical product is usually several products at once: the device, the patient app, the doctor’s system and the backend that connects them. We build all of it with one team, from device firmware to the apps in the App Store and Google Play. Our work in this field covers a therapy device with its own app and doctor CRM, two native apps for an ECG watch, and two public-health prototypes.

Who we build for

• Device makers who have hardware and need the app, the cloud and the firmware updates around it.
• Health startups that need a patient app and a doctor-facing system as one connected product.
• Public-health bodies that need a working prototype before they commit to a full build.

Work we have shipped

PulseV: therapy device, patient app and doctor CRM

A client in Kazakhstan had therapy tables and no software. We built the patient app for iOS and Android on Kotlin Multiplatform, which controls the device over BLE. We built the doctor CRM on Angular with a Kotlin backend, and the ESP32 firmware with OTA updates. The first stage took 15 days and the doctor CRM one week. The system has 100+ users and 6 interface languages.

ECG watch: two native apps completed for an EU manufacturer

The manufacturer had started iOS and Android apps. We took them over and completed them: SwiftUI and Jetpack Compose, Bluetooth pairing, firmware updates, ECG, heart rate, SpO2 and AFib results, with health data kept in the EU and consent and account deletion built in. We do not name this client.

Public-health prototypes for an Estonian tender

For our bid in an Estonian public tender we built a self-help app in three languages with four accessibility modes, aimed at WCAG 2.2 AAA, and a CMS with four roles. Both prototypes are live.

What we build

• Patient apps for iOS and Android: Kotlin Multiplatform, SwiftUI, Jetpack Compose.
• Device connection: BLE pairing, measurements, OTA firmware updates.
• Doctor systems: web CRM on Angular, Kotlin backend, PostgreSQL, live updates over WebSocket.
• Device firmware: ESP32 and STM microcontrollers, written by our electronics lead.
• Accessible interfaces: several languages, accessibility modes, PWA.

Stack, next to where we used it

• Kotlin Multiplatform + BLE + ESP32 OTA: PulseV.
• SwiftUI + Jetpack Compose + BLE: the ECG watch apps.
• Angular + Kotlin + PostgreSQL + WebSocket: the PulseV doctor CRM.
• PWA + CMS with four roles: the Aitab prototypes.

Who works on this

• Anatolii Turovskyi (lead electronics and firmware engineer, PhD). Boards and firmware for ESP32 and STM; the device side of PulseV.
• Serhii Pavliuk (senior front-end and mobile engineer). iOS and Android apps in SwiftUI and Compose, and the App Store and Google Play review.
• Vasyl Lukinchuk (senior full-stack engineer). Kotlin Multiplatform apps and the web side.
• Svitlana Spinatiieva (tech lead). Before GPO she built healthcare software under HIPAA and GDPR.

We are six people. The same engineers work across these projects; there is no separate “healthtech team” behind a sales page.

Data and regulation

On the ECG apps we kept health data in the EU and built consent and account deletion into the apps. We do not hold ISO 27001. Certification of a medical device, such as CE marking under the MDR, stays with you and your regulatory consultant; we build to the requirements you document.

How to start

Most healthtech work starts as a dedicated squad or a fixed-scope MVP. A short paid discovery maps the device, the data and the risks first. You get an architecture and an estimate before the build.

Questions we get

Do you write firmware as well as the apps?

Yes. On PulseV the same team wrote the ESP32 firmware, the app and the doctor system, so there was no hand-off between vendors.

Can you take over apps another team started?

Yes. For the ECG watch we took over two native apps and completed them. We start with a review of what exists and what is missing.

How fast can a first version be ready?

On PulseV the first stage took 15 days and the doctor CRM one week. That depends on scope; we give a figure after discovery.

Where is the health data stored?

That is your decision, and we build to it. On the ECG apps the data is kept in the EU.