Google is preparing a significant update to its smartwatch operating system, and the details emerging from code teardowns and developer previews suggest a company rethinking what a wrist-worn computer should actually do. Wear OS 6.1, expected to arrive later this year alongside Android 16, isn’t a flashy consumer-facing rebrand. It’s an infrastructure play — one that addresses long-standing frustrations with Google’s wearable platform while laying groundwork for features that could reshape how smartwatches interact with phones, apps, and the cloud.
The update was first spotted through a developer preview that Android Authority examined in detail, uncovering a range of under-the-hood changes and new user-facing capabilities. Among the most notable: a revamped notification system, new watch face format support, enhanced health and fitness integrations, and what appears to be early-stage work on running large language model features directly on the watch. Taken individually, these are incremental improvements. Taken together, they paint a picture of Google trying to close the gap with Apple Watch while also carving out territory Apple hasn’t yet claimed.
Start with notifications. For years, Wear OS users have complained about the platform’s handling of alerts — they arrive late, display inconsistently, or simply don’t mirror what’s on the phone. The 6.1 update introduces what Google is calling “rich notifications,” which support inline images, progress indicators, and more granular action buttons directly from the watch. This isn’t cosmetic polish. It’s an attempt to make the watch a viable notification triage device, reducing the number of times a user needs to pull out their phone. According to Android Authority’s teardown, the notification stack also appears to gain better grouping logic, so a burst of messages from the same app won’t flood the tiny screen.
The watch face story is equally telling. Google has been pushing its Watch Face Format — an XML-based standard that lets developers build watch faces without writing full apps — since Wear OS 4. In 6.1, the format gains new complication types and animation support. More importantly, there are signs that Google wants third-party watch faces built in this format to gain feature parity with the proprietary faces that Samsung and Google ship on their own hardware. That matters because watch faces are the single most visible differentiator on any smartwatch. If third-party developers can build faces that look and perform as well as first-party ones, it strengthens the entire Wear OS value proposition against Apple’s comparatively locked-down Watch face environment.
Then there’s the AI angle.
Code strings discovered in the developer preview reference on-device Gemini Nano capabilities. This is Google’s smallest large language model, designed to run locally without a cloud connection. The implications for a smartwatch are significant. Imagine voice replies that are contextually aware, or health summaries generated on the fly without sending sensitive biometric data to a remote server. Google hasn’t confirmed specific Gemini features for Wear OS 6.1, but the groundwork is clearly being laid. And given that Google has already integrated Gemini Nano into the Pixel 8 Pro and Pixel 9 series phones, extending it to the Pixel Watch line would be a logical next step.
The health and fitness side of the update also deserves attention. Google’s acquisition of Fitbit was supposed to supercharge Wear OS health tracking, and while progress has been made — particularly with the Pixel Watch 2 and 3 — the software has lagged behind what Fitbit’s own dedicated devices offer. Wear OS 6.1 appears to introduce new APIs for sleep staging data, skin temperature trends, and cardio load metrics. These aren’t just vanity stats. They’re the kind of longitudinal health signals that insurance companies, corporate wellness programs, and clinical researchers are increasingly interested in. Google Health already partners with medical institutions on wearable data studies, and richer on-device metrics would make Wear OS watches more attractive for those collaborations.
Samsung’s role in all of this remains complicated. The Korean electronics giant is Google’s most important Wear OS hardware partner, and its Galaxy Watch series accounts for the vast majority of Wear OS devices in the wild. But Samsung has historically layered its own software — One UI Watch — on top of Google’s base, sometimes duplicating functionality and sometimes diverging from it entirely. The Galaxy Watch 7 and Galaxy Watch Ultra, both released in 2024, run Wear OS 5 with Samsung’s customizations. Whether Samsung will adopt Wear OS 6.1 features wholesale or cherry-pick from them remains an open question. Recent reporting from 9to5Google suggests Samsung is working on its own health AI features for the Galaxy Watch 8 series, which could either complement or compete with Google’s Gemini-on-wrist ambitions.
The competitive context here is Apple, obviously. WatchOS 11, released last fall, brought smart stacking for widgets, a new Vitals app for health trend monitoring, and deeper integration with Apple’s health records system. Apple also has the advantage of controlling both hardware and software across its entire watch lineup — no fragmentation, no partner negotiations, no compromises. Google’s counter-strategy with Wear OS has been to offer more openness: more hardware partners, more watch face customization, more third-party app flexibility. The question is whether that openness comes at the cost of the kind of tight integration that makes Apple Watch feel so polished.
Wear OS 6.1 suggests Google is aware of this tension and trying to address it. The update includes new system-level APIs for app-to-app communication on the watch, which should reduce the jankiness that sometimes occurs when, say, a workout app tries to hand off data to Google Fit. There are also improvements to the Wear OS tile system — those swipeable information cards that serve as the watch’s secondary interface. Tiles can now update more frequently and support richer data layouts, making them more useful as glanceable dashboards.
Not everything in the preview is polished. Some features appear to be in early stages, with placeholder UI elements and incomplete documentation. That’s typical for a developer preview — the final consumer release, likely timed to the Pixel Watch 4 launch, will look different. But the direction is clear. Google is investing in making Wear OS a more capable, more independent platform. One that doesn’t just mirror your phone’s notifications but actually processes information, generates insights, and acts as a standalone computing device on your wrist.
The developer angle shouldn’t be overlooked either. Google has struggled to attract app developers to Wear OS, partly because the install base was small and partly because the development tools were clunky. The new APIs in 6.1, combined with better Compose for Wear OS support and the expanded Watch Face Format, lower the barrier to entry. Google is essentially telling developers: build once, deploy across multiple watch brands, and your apps will look and feel native. That’s a pitch Apple can’t make, since WatchOS apps only run on Apple hardware.
Whether this matters to consumers depends on execution. The average smartwatch buyer doesn’t care about APIs or XML-based watch face formats. They care about battery life, health tracking accuracy, and whether their apps work reliably. Google’s track record on the first point has been improving — the Pixel Watch 3 gets roughly 24 hours on a charge — but still trails behind some competitors. Health tracking accuracy has been a mixed bag, with Fitbit’s algorithms sometimes producing different results than what third-party apps report using the same sensors. And app reliability on Wear OS, while better than it was three years ago, still can’t match the consistency of WatchOS.
So Wear OS 6.1 is a bet. A bet that better infrastructure will lead to better apps, which will lead to more users, which will attract more developers. It’s the classic platform flywheel argument, and Google has made it before — sometimes successfully (Android phones), sometimes not (Android tablets, at least until recently). The smartwatch market, estimated at roughly $50 billion globally by 2028 according to industry analysts, is large enough to justify the investment. But Google needs its hardware partners, particularly Samsung, to adopt these improvements quickly and consistently.
The timeline for Wear OS 6.1’s public release hasn’t been officially confirmed by Google. Based on previous release patterns and the alignment with Android 16, a fall 2025 launch seems likely. The Pixel Watch 4 would presumably ship with it out of the box, while existing Pixel Watch 3 and possibly Pixel Watch 2 devices would receive it as an over-the-air update. Samsung’s timeline, as always, operates on its own schedule.
For now, the developer preview offers a roadmap. And that roadmap points toward a version of Wear OS that’s meaningfully more capable than what exists today — smarter notifications, better health data, on-device AI, and a more inviting developer platform. Whether Google can deliver on all of it by fall is another question entirely. But the ambition is real, and the details suggest this isn’t just another incremental version bump dressed up in marketing language. It’s an attempt to make the Android smartwatch something people choose, not just something they settle for.
WebProNews is an iEntry Publication