There are many reasons why Google Wear OS as a smartwatch platform is so frustrating. It lacks the advanced health features you see at other wearable manufacturers, almost all watches available still rely on outdated chips, and historically, Google has not been the best at providing timely updates. Recent attempts to fix all of this have been encouraging, but still beautiful smaller. However, an Android developer blog notes that third-party tiles are coming to Wear OS, and for the first time, I’m excited about the possibilities.
Google Tiles introduced in 2019, in one of the most substantial updates to Wear OS platform. The theftcapable widgets were, at that point, long overdue, whereas Samsung has been offering something similar for years. The only problem was you were limited to the Google blocks themselves and those were just OK, at best. It was a little better experience, but one that still lagged behind the competition.
Opening blocks for the third party parties is great on two levels. First, it will allow you to exchange a Google block for a better of your favorite application. Google Fit? No, Thanks. Ideally, you get a Strava Tile or something a little less basic. Of course, that would depend on these companies paying attention to Wear OS again. This brings me to the second point: allowing developers to create their own blocks can encourage them to create for the Wear OS platform.
For a time, one of Wear OS ‘few strengths over Samsung’s Tizen OS was a more robust application ecosystem. And then the competing platforms started to diminish that leadership. Spotify struck an independent deal with Garmin and Samsung, but on Wear OS it remains a glorified remote. Damn, even Google put Wear OS in second when you created a First, the YouTube Music app for Apple Watch. That was in October, And here we are in March 2021 with no sign of a Wear OS version. Çoh shDo older developers prioritize Wear OS when Google doesn’t?
G / O Media can receive a commission
If customized Tiles sparks a growing interest in Wear OS and Google builds this third-party ecosystem, tchicken Wear OS may have a chance to fight. Çand we haven’t seen how Wear OS will work on a watch equipped with Qualcomm’s Snapdragon Wear 4100/4100 + SoC. Unlike Apple and Samsung offerings, Wear OS watches have been working with older processors. At the moment, only Mobvoi TicWatch Pro 3 has the latest chip and, although Mobvoi watches are good, it is not exactly the most well-known smartwatch brand.
However, the leap from the 3100 chip – which is in most Wear OS watches now – to the 4100 chip seems to be more substantial than the jump from 2100 to 3100. It promises 85% faster performance, 25% more battery life and better LTE connectivity – all of which can allow for more creative experiences on your wrist.
Then there is the fact that Google recently closed the acquisition of Fitbit. Although the two companies operate separately, for now, we’ve seen Google Assistant come to Fitbit watches. Fitbit’s know-how is not beyond the reach of Wear OS.
Maybe that’s why we heard rumors that Samsung is considering abandoning its proprietary Tizen OS software for Wear OS. If even a fragment of this is In fact, this would indicate that Google has real plans to your most neglected platform. Certainly, there is no way for Samsung to simply abandon all of the advanced health features introduced with the Galaxy Watch 3 if Wear OS cannot support the transition. (Currently, the best that Wear OS watches can do is monitor your heart rate.some have integrated GPS.)
There is a chance that even with the custom teeiles, developers won’t get involved because they don’t think it’s worth the effort. Now, custom Tfiles are in alpha test through the Jetpacks Tile Library, and Google said that the new options be available to users later this spring when “roll[s] updating the corresponding Wear OS platform. ”Many things have to work out, but for the first time in a long time, it doesn’t look like total disgrace and melancholy for Wear OS.