watchOS — Continuous Core Motion monitoring in the background for independent fall detection

I'm developing an independent fall-detection application for Apple Watch using Core Motion (CMMotionManager) at 20 Hz.

The goal is to identify potential falls using accelerometer, gyroscope and orientation data, then notify nominated family contacts. The application is deliberately independent of Apple's built-in Fall Detection and Emergency SOS.

Test environment

  • Physical Apple Watch running watchOS 27.2
  • Xcode 27.2
  • Core Motion device-motion callbacks on a dedicated serial OperationQueue
  • Motion processing on the MainActor
  • Tests performed without the Xcode debugger attached

Observed results

With the Watch display awake:

  • 2,300 processed samples
  • Longest sensor timestamp gap: 0.05 seconds
  • Longest callback arrival gap: 0.66 seconds
  • Callback interruptions over one second: 0

With the Watch dimmed/backgrounded:

  • 3,229 processed samples
  • Longest sensor timestamp gap: 0.30 seconds
  • Longest callback arrival gap: 29.11 seconds
  • Callback interruptions over one second: 6
  • Maximum sample delivery lag: 29.065 seconds

The motion timestamps appear nearly continuous, but callback delivery becomes substantially delayed after the app enters the background.

The monitoring flag remains true, and no explicit call to stop motion updates occurs when the app becomes inactive.

Questions

  1. Is there an Apple-supported background execution mechanism or entitlement allowing a third-party watchOS app to continuously process accelerometer and gyroscope data for independent fall detection, without requiring an active workout session?

  2. Would CMBatchedSensorManager provide any useful background delivery capability for this application, or would its callbacks remain subject to normal watchOS suspension?

  3. Is there a recommended architecture for detecting a potential fall and initiating a timely family notification while the Watch app is backgrounded, without relying on Apple's built-in Fall Detection or Emergency SOS?

We understand that workout sessions and extended runtime sessions have specific intended purposes. We want to implement this correctly rather than use an unrelated background mode to prevent suspension.

Any guidance from Apple engineers or developers experienced with watchOS background Core Motion processing would be greatly appreciated.

There is no supported way for a third-party app to continuously process raw accelerometer and gyroscope data without an active (workout) session. The sensors still work, and the samples are cached, but the delivery (to other components, such as the callbacks) is delayed while your app is backgrounded, and that is as-designed. CMBatchedSensorManager doesn't change that behavior.

Regarding the "architecture for detecting a potential fall," your app is "deliberately independent of Apple's built-in Fall Detection and Emergency SOS," and that rules out the use of CMFallDetectionManager. I am curious how this design decision was made though, if you don't mind to share.

Best,
——
Ziqiao Chen
 Worldwide Developer Relations.