watchOS · planned
Swift · Swift Package Manager- SwiftUI views and async/await APIs
- Core ML model, designed to run on the watch
- HKWorkoutSession for background sessions
We're building native SDKs for watchOS and Wear OS, with a React Native bridge on top. The model is designed to run on the watch, work offline, and hand your app finished sets as typed events.
$npx expo install @efferens/react-native
Illustrative package names. Nothing is published yet; final names will be set before release.
# React Native (Expo or bare)npx expo install @efferens/react-nativenpx expo prebuild# Bare React Nativenpm i @efferens/react-nativecd ios && pod install
Illustrative API, not the final surface.
Detection is designed to happen on the watch, so it can work without a signal. Your app will receive structured sets, not sensor streams. With user consent, sensor recordings go to Efferens to improve the models.
Inference is designed to run on the watch with no network calls during a workout. Sets will queue locally and sync when the phone is back in range.
The design goal: adaptive sampling and the platform's own workout session APIs to keep the watch efficient through long sessions. Battery impact hasn't been measured yet.
Every set is designed to arrive with the same schema on every platform: TypeScript types, Swift Codable and Kotlin data classes.
type DetectedSet = { exercise: "back_squat" | … reps: number confidence: number startedAt: Date durationSec: number }
Planned drop-in confirm views for low-confidence sets on watchOS, Wear OS and React Native: "Was that a row?" Native on each platform, themeable, or build your own.
Planned: exercise catalogue, confidence thresholds and rollout flags update over the air, with no app release needed.
You'll record a session once on a real watch, then replay it in the simulator, in unit tests and in CI, so your detection code gets the same events every time.
Something else? We'd rather answer it on a call with your team.
That's the plan. The config plugin is designed to add the watch target, entitlements and permissions during prebuild, so there's no manual native setup.
That's the plan. The bridge is designed as TurboModules and to also work with the legacy architecture during migration.
It's designed not to. The model is designed to run on the watch, with sets queued locally and synced to the phone when it's in range.
Detection is designed not to need it: the model is designed to run on the watch and your app will receive set events. Separately, sensor recordings, with the user's age, height and weight, will be uploaded to Efferens only with the user's consent and used to improve the models. How consent is collected is still being defined.
We're targeting Apple Watch on watchOS and Wear OS watches with accelerometer and gyroscope access. We plan to publish a tested-device list once there's a release.
We plan to offer custom models. Your catalogue would then ship through the Console like any other update.
The plan is to use recorded sessions: replay them in the simulator, in unit tests or in CI and assert on the events you get back.
We're looking for early partner workout-tracking apps. Tell us about your stack and we'll share where we are.