Connected Health / Mobile
Eveia
The context
Eveia is a connected under-desk pedal paired with a companion mobile app. The pedal is patented French engineering — a 7 cm micro-amplitude motion that protects the knees and the psoas while you work — built to medical-grade quality with a 30-year service life.
The app pairs over Bluetooth, counts steps and calories from the pedal's motion, and syncs them into Apple Health, Google Fit, and Fitbit so users see the activity inside the health ecosystem they already use. The product is now used inside Enedis, Hennessy, the Ministère des Finances, CARSAT, Crédit Agricole, COVEA, SUEZ, and has been covered by TF1, France Inter, Europe 1, Le Parisien, and RMC/BFMTV.
My role
Full-stack and mobile lead. Led a cross-functional team of three developers (mobile, hardware, game) and one designer. Built the backend, the back-office, most of the mobile app, and the BLE integration myself.
What I built
-
React Native app, iOS and Android
Built most of the app personally, with one mobile developer supporting. End-to-end ownership of the user experience and the technical architecture on the client side.
-
BLE integration to the physical pedal
Wrote this layer myself with react-native-ble-plx. The hardest piece of the whole product — connecting a React Native app to a custom-firmware Bluetooth peripheral and keeping the link alive reliably across iOS and Android.
-
iOS background sync that doesn't get killed
iOS aggressively suspends background BLE to save battery, which is fatal when your job is to count steps while the user works. I wired Core Bluetooth background modes properly, paired with on-pedal buffering, so even when iOS suspended the app the data didn't disappear — it caught up on resume.
-
Wearable integrations: Apple Health, Google Fit, Fitbit
All three. Steps from the pedal flow into the user's existing health ecosystem instead of forcing them into a new silo. Native HealthKit, Health Connect / Google Fit, and the Fitbit Web API.
-
Backend and back-office
Node.js + GraphQL + MongoDB. User data, device pairing, history, and the admin tools the operations team used day-to-day.
-
Led a cross-functional team
Three developers and one designer, spanning hardware, mobile, and a game developer who built virtual world walking experiences inside the app — pedaling becomes a stroll through universes, integrated into the same step-count pipeline.
Tech stack
-
iOS + Android app.
-
Across mobile and backend.
-
Backend + back-office.
-
API for app and back-office.
-
Primary data store.
-
Pairing and data sync with the pedal.
-
iOS health sync.
-
Android health sync.
-
Third-party wearable sync.
Impact
-
shipped
iOS + Android
-
product ownership
E2E
-
enterprise clients on the product today
7
Trusted by
- Enedis
- Hennessy
- Ministère des Finances
- CARSAT
- Crédit Agricole
- COVEA
- SUEZ
The trade-off
BLE on mobile is a minefield. iOS in particular will kill a background connection the moment it decides battery matters more than your app — and the pedal is not allowed to die mid-step-count. We invested early in Core Bluetooth background modes, smart reconnection, and offline buffering on the pedal itself, so the data flow stayed correct even when the OS got in the way.