Apple Watch Glucose Monitoring Project Gets New Leadership and a Glimpse of WatchOS 27 Support

---

---

watchOS 27 preview and the new project lead

In the latest Power On newsletter, Mark Gurman reported that watchOS 27, slated for release in the fall of 2026, will expose a set of low‑level sensor frameworks aimed at third‑party developers. Among the announced features are HealthKit 12 extensions for continuous optical sensing, a new BloodGlucoseKit preview, and tighter integration with the Secure Enclave for privacy‑preserving analytics.

At the same time, Apple has reassigned the internal non‑invasive glucose‑monitoring moonshot from platform‑architecture chief Tim Millet to Zongjian Chen, senior engineering leader of the Advanced Technologies Group (ATG). Chen’s résumé includes the rollout of 5G modems in the iPhone 15 series and the delivery of the Apple Vision Pro’s custom silicon. Within Apple, his reputation as “the guy who gets things shipped” has been widely reported.

The leadership change matters because ATG traditionally owns hardware‑first research that eventually becomes a consumer‑grade feature. By moving the project under Chen’s umbrella, Apple is effectively saying the effort has moved from speculative research to a stage where engineering resources, silicon design, and software integration are being aligned.

---

What the shift means for developers today

Updated SDK requirements

• watchOS 27 SDK – Minimum Xcode 15.4, Swift 6.0. The new BloodGlucoseKit is gated behind the com.apple.developer.healthkit.bloodglucose entitlement and requires a device running watchOS 27 or later.
• iOS 18 SDK – The companion iPhone app must target iOS 18 to use the paired‑device APIs that aggregate sensor data from the watch and perform on‑device ML inference.
• HealthKit 12 – Adds HKQuantityTypeIdentifierBloodGlucose for continuous readings, plus a new HKCorrelationTypeIdentifierGlucoseTrend that can be queried in real time.

Developers who have already built glucose‑tracking apps with external dongles can now prototype using the preview framework on a developer‑seed watch. Apple is providing a sample project on its GitHub repository (Apple/GlucoseDemo) that demonstrates how to request permission, start a sensor session, and read calibrated glucose values.

Cross‑platform considerations

If you maintain a health‑tracking app that runs on Android, the new Apple APIs do not affect your existing codebase, but they do raise a strategic question: should you wait for a comparable non‑invasive sensor on Wear OS, or focus on a unified cloud‑backend that can ingest data from both platforms? Apple’s approach of exposing raw optical data (rather than a high‑level “glucose value”) suggests that third‑party developers will need to implement their own calibration pipelines, similar to what many Android apps do with the Google Pixel Watch sensor suite.

For teams using Flutter or React Native, the upcoming BloodGlucoseKit will be accessible through platform channels. The Flutter community has already opened a flutter_blood_glucose plugin repository, and the first beta version is expected to land on pub.dev shortly after the watchOS 27 SDK ships.

---

Migration path for existing glucose‑monitoring apps

1. Update your Xcode version to 15.4 and set the deployment target to watchOS 27.
2. Add the new entitlement (com.apple.developer.healthkit.bloodglucose) in your project’s Entitlements.plist.
3. Replace external‑device SDK calls with BloodGlucoseKit APIs. The sample project shows a one‑to‑one mapping for start/stop sessions and data callbacks.
4. Implement on‑device calibration using the HKCorrelation APIs. Apple recommends a 7‑day calibration period where the watch reads a reference finger‑prick value entered by the user.
5. Test on a developer‑seed watch – Apple is distributing a limited number of watchOS 27 beta devices to health‑app developers. Sign up through the Apple Developer portal to request a unit.
6. Update your privacy policy to reflect the new data‑handling practices. The HealthKit privacy model now requires explicit user consent for continuous glucose monitoring, and Apple will enforce a UI prompt on first launch.

---

Outlook and timeline

While the leadership change and SDK preview are encouraging, Apple has not committed to a consumer‑grade glucose sensor in any upcoming product cycle. Analysts estimate that a first‑generation implementation could appear in a watch released in 2028, after a few more silicon iterations and extensive clinical validation.

For developers, the immediate benefit is early access to the sensor stack, which allows you to build calibration algorithms, UI experiences, and cloud‑sync pipelines well before the hardware is mass‑produced. Early adopters who ship a robust solution may gain a competitive edge when the feature finally ships to the broader market.

---

Stay tuned for the official watchOS 27 release notes and the Apple Vision Pro‑style developer sessions at WWDC 2026, where Apple is expected to demo the new health sensor APIs live.