The recently released Windows 10 Insider Build 15007 finally brought GATT server support, important for notifications from some wearables, to Windows 10, and now Build 15003 of the Windows 10 Preview SDK is available to get developers started on implementing support for the feature.

The update actually brings 3 new Bluetooth LE improvements:

GATT Server

This allows Bluetooth client devices to read data from your smartphone, such as notifications, and has long been the reason why Fitbit devices did not support call and other notifications on Windows Phones.

This allows Bluetooth client devices to read data from your smartphone, such as notifications, and has long been the reason why Fitbit devices did not support call and other notifications on Windows Phones. Bluetooth LE Peripheral

Via the Bluetooth s Generic Access Profile (GAP) Windows 10 devices are now able to advertise as connectable, meaning users are able to pair more easily as client devices with devices such as other PCs or smart locks.

Via the Bluetooth s Generic Access Profile (GAP) Windows 10 devices are now able to advertise as connectable, meaning users are able to pair more easily as client devices with devices such as other PCs or smart locks. Unpaired Bluetooth LE device connectivity

Windows 10 devices are now able to connect to other Bluetooth devices without pairing first, which is useful for some devices such as smart trackers for example.

Microsoft notes with Peripheral role and GATT Server combined, Windows can operate in all four combinations of GATT and GAP roles:

The update also brings Call Control API support to desktop which means your VoIP apps can natively take advantage of Bluetooth headset functionality like pick up, hang up, hold, call waiting, etc. Users will also experience higher-quality audio for voice, thanks to Wideband speech.

Microsoft notes that were working directly with Fitbit, Garmin and other device manufacturers to develop the APIs, which hopefully means we will see apps which support the features arrive sooner rather than later.

Read how to get started with your own app at Microsoft here.