There are four important elements that a partner will need to address before triggering the MultiScan SDK.
To reduce the file size of our MultiScan SDK and ultimately your app, we delay the download of certain files essential to the SDK until they’re needed by your user. The download trigger for the Remote Assets will need to be implemented by a partner and is required for the scan to operate.
See Remote Asset Management for more information.
The BodyScan requires the following biometric inputs from your users in order to start.
- Height - Weight - Sex
- Chest Circumference - Waist Circumference - Hips Circumference - Thigh Circumference - Fat Free Mass
These inputs are the bare minimum for the BodyScan to operate and return the above results. You may want to ask additional questions before (or after) a scan to create contextual data, allowing for more in-depth insights about your user's health.
See Data Overview for more information on derived data and contextual data.
In the Technology Demo App, we show a scanning guide to users before they go through the BodyScan capture process. It explains important information that will assist in getting accurate, repeatable, and error-free results. The guide contains:
- Spacial and environmental requirements, like good lighting and 14ft/4m space.
- Clothing requirements, like to wear form-fitting clothes, avoiding anything baggy.
- Device placement requirements, like placing phone camera at hips height, propping it up against a solid object (pot plant, water bottle).
See Supporting Your Users During a BodyScan on how to educate users about the scan process.
An active network connection is required to download the remote assets and to trigger billing events.