How It Works

This page follows one data point all the way through the system. It covers nearly every aspect of this package (delayed arrival, bursts, data appearing while the app was closed).

​

The layers

​

1. Watch configuration

When CAMS connects the AppleWatchDevice, the device manager calls configure with the settings from the protocol. On the phone this creates the AWARE AppleWatchSensor, which activates the WatchConnectivity session. The watch app asks the phone for its configuration on startup (and whenever it calls applyiPhoneSettings()). The phone answers with the settings derived from AppleWatchDevice.toWatchSettings(). The exact keys are listed in Settings Sent to the Watch.

​

2. Watch database

The AWARE sensors write rows into a SQLite database on the watch. This happens whether or not the phone is nearby, and whether or not your Flutter app is running. The only requirement is that the watch app holds a background runtime session (see backgroundSessionType).

​

3. Data transfer

On a timer, fileTransferInterval, 15 minutes by default, the watch exports the database in pages, compresses each page with zlib, and sends each as a file over WatchConnectivity.

​

4. Phone decoding

The AWARE sensor on the phone decompresses and decodes each file into raw AWARE rows. AppleWatchController receives them tagged with the AWARE table they came from, and sends each batch over the records platform channel as an AppleWatchRecords.

​

5. Probes

AppleWatchDeviceManager re-broadcasts the batches. Every probe listens to the same stream and takes only the records from the AWARE table that holds its own data type:

​

Platform channels

For anyone extending the package or building a debug screen: The Dart side of all three is AppleWatchService, a singleton described in the API Reference.