Skip to main content

Requirements

The torch is used, not required. The SDK uses the rear camera’s torch for the whole reading whenever the system allows. Without one (hasTorch false, most iPads and many tablets) it reads in room light and completes far fewer readings, so decide whether to offer readings there, and if you do, ask for a brightly lit environment (the flow’s noTorchBody). Simulators and emulators cannot take a reading, so test on a device.

Checking support at runtime

Call deviceSupport() before showing the feature. It never opens the camera, so it is cheap to call at any time.
reason is a short English string for your logs: On Android, a device whose camera characteristics cannot be read counts as supported, and the frame rate during positioning then decides. hasTorch is reported whether or not the device is supported. Session creation and start() throw unsupportedDevice(reason) on an unsupported device, so the check is for your UI, not a gate you must build.

Frame rate and power modes

  • iOS starts at the highest frame rate the camera reaches (60 fps on current iPhones). When the camera cannot hold it, usually in Low Power Mode, the SDK adjusts the capture, and a reading in progress restarts with cancelled(interrupted). If it still cannot keep up, lowFrameRate shows and the reading waits.
  • Android runs a fixed 30 fps. Battery Saver and thermal throttling can lower it, and then lowFrameRate shows and the start waits.
If users see lowFrameRate often, ask them to turn off Low Power Mode or Battery Saver, as the flow’s guidanceLowFrameRate does.

Excluding device models

deviceSupport() answers from the hardware alone, with no built-in list of excluded models. If a model misbehaves in your user base, exclude it in front of the SDK, from your own remote config, so the list changes without a new build. Match model tokens case-insensitively by containment, so an entry can be an exact model or a family prefix. The model is the machine identifier on iOS (iPhone14,2 style) and Build.MODEL on Android. In the wrappers, read it with your device-info library and match the same way.
When the check fails, do not start a session: hide the feature, or explain with the flow’s unsupportedBody. Keep the list short and dated, and remove entries once a fix ships.

What the validation covered

The validation study ran on 21 iPhone and 9 Android participants’ own phones (Consistent across groups).

Known limitations

  • Cases and lens protectors that separate the flash from the lens can weaken the signal. Suggest removing a thick case if readings keep restarting with weakPulseSignal (iOS) or unsteady guidance.
  • Cold fingers give a faint pulse. Suggest warming the hands first.
  • A device without an accelerometer still takes readings. Its breathing rate then comes from the pulse signal alone, so its tier is low or withheld, never high.