1. Building IoT apps with Microsoft Band and Xamarin
STEFANO TEMPESTA

2. AGENDA
USE CASE
AZURE IoT & ML
XAMARIN
MICROSOFT BAND

3. ABOUT ME @stefanotempesta www.tempesta.space Stefano Tempesta
VP of
@stefanotempesta

4. 1 3 2 PRODUCTS PARTNERS CRM LIFESTYLE USER PROFILE TARGET PRODUCTS
ASK FOR ADVICE
RECOMMENDATION 3
PARTNERS
PRODUCT SAMPLES
EXTENDED PROFILE
CRM 2
LIFESTYLE
COLLECT POINTS
IDENTIFY PATTERNS
USER PROFILE
TRENDS & INSIGHTS
AGE
GENDER
LOCATION
SKIN TYPE
SEASON
TARGET PRODUCTS
OPTIMIZE CHANNELS

5. Microsoft Band
Windows Phone
Android
iOS

6. AZURE IoT

7. AZURE IoT Internet of Your Things www.internetofyourthings.com
Starter Kits
Windows 10 IoT Core
Azure IoT Certified
Azure IoT Suite
Solutions
Predictive maintenance
Remote monitoring

8. AZURE IoT Azure IoT Hub Azure Machine Learning
Device identity registry
Block unsolicited network information
Authorization and authentication are based on per-device identities
Bi-directional communication
Communication between device and service is secured
Maintains device specific queues for all sent commands
Azure Machine Learning
Building and deploying predictive analytics solutions.
Models
Experiments
Sentiment analysis
Demand estimation
Outcome prediction
Recommendations
DATASET
TRAIN MODEL
ALGORITHMS
SCORE MODEL
EVALUATE MODEL

9. XAMARIN & MICROSOFT BAND

10. XAMARIN & MICROSOFT BAND
Microsoft Band SDK
Sensors
Accelerometer
Gyroscope
Distance
Heart Rate
Pedometer
Skin Temperature UV
Device Contact
Calories
Microsoft Band 2 only
Altimeter
Ambient Light
Barometer
Galvanic Skin Response
RR Interval
Access Sensors
Use a range of sensors including heart rate, UV, accelerometer, gyroscope, and skin temperature, as well as fitness data, to design cutting-edge user experiences:
Accelerometer Provides X, Y, and Z acceleration in meters per second squared (m/s²) units.
Gyroscope Provides X, Y, and Z angular velocity in degrees per second (°/sec) units.
Distance Provides the total distance in centimeters, current speed in centimeters per second (cm/s), current pace in milliseconds per meter (ms/m), and the current pedometer mode (such as walking or running).
Heart Rate Provides the number of beats per minute, also indicates if the heart rate sensor is fully locked onto the wearer’s heart rate.
Pedometer Provides the total number of steps the wearer has taken.
Skin Temperature Provides the current skin temperature of the wearer in degrees Celsius.
UV Provides the current ultra violet radiation exposure intensity.
Device Contact Provides a way to let the developer know if someone is currently wearing the device.
Calories Provides the total number of calories the wearer has burned.
Altimeter (Microsoft Band 2 only) Provides current elevation data like total gain/loss, steps ascended/descended, flights ascended/descended, and elevation rate.
Ambient Light (Microsoft Band 2 only) Provides the current light intensity (illuminance) in lux (Lumes/m²).
Barometer (Microsoft Band 2 only) Provides the current raw air pressure in hPa (hectopascals) and raw temperature in degrees Celsius.
Galvanic Skin Response (GSR) (Microsoft Band 2 only) Provides the current skin resistance of the wearer in kohms.
RR Interval (Microsoft Band 2 only) Provides the interval in seconds between the last two continuous heart beats.

11. XAMARIN & MICROSOFT BAND

12. XAMARIN & MICROSOFT BAND
The SDK provides support for Band sensors as subscriptions.
Callback that delivers data at specific intervals
Each sensor requires a power draw!
On Windows and iOS, constant connectivity is required to maintain a subscription.
Some sensor subscriptions require user consent.
Heart Rate and RR Interval
Granted on a per-sensor basis
The SDK provides support for Band sensors as subscriptions. The subscriptions are managed by the Band Sensor Manager on the Band Client. For each hardware sensor, the Sensor Manager allows the application developer to create a subscription.
A subscription is essentially a platform-specific callback mechanism. It will deliver data at intervals specific to the sensor. Some sensors have dynamic intervals, such as the Accelerometer (on Android and Windows), that allow developers to specify at what rate they want data to be delivered. Other sensors deliver data only as their values change.
It’s important to understand that subscribing to sensor data effects the battery life of the Band. The use of each sensor requires a power draw (some more than others). Developers should subscribe to sensor data only when the data is absolutely necessary for their applications.
On Windows and iOS, constant connectivity is required to maintain a subscription. If the Band loses connectivity with the phone, the subscription is stopped and it’s not automatically enabled upon reconnection.
Some sensor subscriptions require user consent. The subscription permission model is as follows.
1. Permission is granted on a per-sensor basis.
2. Applications can request the permission status of a particular sensor. The status can be Granted, Declined, or Not Specified. If permission is Granted, applications can simply start the subscription.
3. Applications can request to show the permission dialog to ask the user for permission if the permission is Not Specified or Declined.
4. If the permission is Not Specified or Declined and the application requests that the subscription be enabled the subscription, the request to enable the subscription will fail.
Note: At this time, only heart rate and RR Interval sensor subscriptions require an explicit user consent before they can be started.

13. REFERENCES Xamarin Components > Microsoft Band SDK
Microsoft Band Developers Page
Azure IoT Hub

14. THANK YOU
Stefano Tempesta
@stefanotempesta