Get in touch
Efferens Console · Planned

Ship exercise detection on your terms.

The Console is planned as one place for product, engineering and support to decide which of your users get automatic detection, watch how it performs, and switch it off if needed.

RolloutEnable auto-detection for 25% of watchOS users
console.efferens.com / example-fitness / production
RolloutAuto-detection
Save
10%
of users
4,960
users enabled
watchOSWear OSApp ≥ 4.2Canada
Sets detected · 7d18,240▲ 12%
Kept without edits94.1%▲ 0.8 pts
Detections per daylast 14 days

Illustrative mock-up. Example data.

Rollout path

From pilot to every user, one step at a time.

Start small, measure, then widen the audience. Each step is planned as a setting in the Console, not a new release of your app.

ef_test_••••
Test set received
01

Sandbox

You'll integrate against test keys and synthetic sessions before any real user sees detection.

Internal team12 users
Beta testers340 users
Power users1,200 users
02

Beta cohort

Turn it on for a named group first: your staff, beta testers or a list you upload.

50%of users
03

Gradual ramp

Widen the rollout by percentage while accuracy and adoption stay healthy.

100%
Kill switch
04

Everyone

Go to 100% when you're confident, with the kill switch one click away.

Control

The rollout controls we're planning.

Analytics

Adoption and accuracy, not just usage.

The Console is planned to show how many sets are detected, which exercises your users train, and how often they edit a detected set. That edit rate would come from your own users, which we expect to be a useful accuracy signal.

  • Detections by day, exercise and platform
  • Kept-without-edits rate per exercise
  • Compare rollout groups side by side
Kept without edits, by exercise30d
Back squat97%
Bench press95%
Deadlift93%
Bent-over row90%
Walking lunge86%
Illustrative mock-up. Example data.
Exercise catalogue

Choose what gets detected.

You'll be able to turn exercises on or off for your app and set how confident detection must be before a set is logged automatically. Below the threshold, your app can ask the user to confirm instead.

  • Per-exercise on/off
  • Confidence threshold per exercise
  • Ask-to-confirm fallback for borderline sets
Planned for teams

Safe defaults for production.

Environments and API keys

Sandbox and production will be separate, with keys you can rotate and revoke.

Roles and permissions

Roles will include viewers, editors and admins, so only the right people can change a rollout.

Audit log

Every change to a rollout, rule or key will be recorded: who made it, when, and what changed.

Webhooks

You'll be able to get notified when a rollout changes or accuracy crosses a threshold.

SDK version health

You'll see which app and SDK versions your users run, and spot devices that need an update.

Integration support

We plan to work with your team until you're live, with a two-month trial so you can test it with your users.

Who it's planned for

One console, three teams.

Product managers

Plan the rollout, pick target groups and watch adoption and accuracy before going wider.

Engineers

Manage environments and keys, check SDK versions and wire up webhooks.

Support

Look up why a user does or doesn't have detection, and turn it off for a segment if needed.

Console

Roll out detection step by step.

Tell us how you'd roll out detection. We'll show you how the planned Console would handle it.