There's a big chance that Google's long-rumored smartwatch will be called the "Pixel Watch." The tech giant has filed paperwork with the United States Patent and Trademark Office to trademark "Pixel Watch," 9to5Google reports. In its application, Google wrote that the name is intended to "cover the categories of smartwatches," "wearable computers in the nature of smartwatches," as well as smartwatch cases, straps and bands.
The trademark application didn't contain additional details about the device. But based on previous rumors and rendering leaks, the company's first in-house-developed smartwatch will have a circular face with no bezel. It's expected to have a heart rate sensor and other features found in devices by Fitbit, which Google purchased in 2021, as well. The device will reportedly cost more than a Fitbit, though, and will be a veritable Apple Watch competitor. It's also expected to run Wear OS 3, the tech giant's upcoming wearable platform that will only make its way to a handful of current smartwatches.
Jon Prosser, who's known for leaking upcoming releases in tech, previously said that Google is planning to launch its first smartwatch on May 26th. That doesn't sound unlikely, since the date coincides with the tech giant's annual I/O conference that usually takes place in May. However, as 9to5Google points out, Google has to go through a few more regulatory hurdles before the device's launch. Since the device hasn't been spotted in listings at the Federal Communications Commission and the Bluetooth SIG yet, May 26th might be too soon for its unveiling.
Pixel Watch 👇
— Jon Prosser (@jon_prosser) January 21, 2022
I’m hearing that Google is planning on launching it on Thursday, May 26th — over year since we leaked it.
This is the first we’ve seen a set date on the device behind the scenes.
Google is known for pushing back dates — but if they do, we’ll know 👀 pic.twitter.com/Kk0D4Bom6d
from Engadget is a web magazine with obsessive daily coverage of everything new in gadgets and consumer electronics https://ift.tt/8PLy9HR
No comments:
Post a Comment