Reviews

Google Pixel Watch 4 hands-on: Dome wasn’t built in a day

The Pixel Watch 4's 'domed' Actua 360 display looks fantastic

Google Pixel Watch 4

While Google’s Pixel 10 line didn’t bring a ton of hardware changes, the same can’t be said for the company’s latest smartwatch, the Pixel Watch 4. Google made a few upgrades to the hardware and under the hood that should make this the best Pixel Watch yet, though I’ll need to spend more time with the smartwatch to say for certain.

First thing to note, however, is that the Pixel Watch 4 won’t be available alongside the Pixel 10 series. Instead, the Pixel Watch 4 will land on shelves starting October 9, 2025, so anyone looking forward to the new watch has a bit of a wait ahead of them.

When the Pixel Watch 4 does arrive, it will start at $479 for the Wi-Fi variant and $599 for the LTE version, while the Watch 4 XL costs $549 and $679 for the Wi-Fi and LTE versions, respectively. Those prices are mostly the same as the Pixel Watch 3, save for the XL LTE version, which costs $10 more.

From left to right: Pixel Watch 3 XL, Pixel Watch 4, Pixel Watch 2.

Perhaps the most significant change Google made with the Watch 4 is the new ‘domed’ display. Google calls it the ‘Actua 360,’ and in short, the company made the bezels 15 per cent smaller compared to the Watch 3 for a “nearly edgeless experience.” Moreover, the display is 50 per cent brighter with up to 3,000 nits of brightness, and Google claims the Corning Gorilla Glass used is more durable and scratch-resistant. I’m curious to see how that stacks up over time, as my supposedly scratch-resistant Pixel Watch 3 XL has quite a few unsightly scratches on it after nearly a year of daily use.

While a lot of testing needs to be done, my first impressions of the Watch 4 display are quite good. Part of Google’s original promise with the Pixel Watch was giving a water drop-like experience with the display and this is the closest Google has come to actually realizing that promise. I already throught the Pixel Watch was one of the better-looking smartwatches out there, and these small improvements continue to elevate the aesthetic.

Google Pixel Watch 4 new charging stand.

Another notable hardware change relates to the charger. Yes, Google changed its watch charger again, and I have mixed feelings about this new one. On one hand, the new charger connects to the side of the watch magnetically, instead of the bottom. This effectively turns the watch into a tiny clock when it’s charging. I like that a lot. But in order to make that work, Google now has an unsightly black bar on the left side of the watch with metal dots on either end for the charging contacts. The bar also houses an improved speaker. After a brief hands-on with the watch, I’m not sure I like this change, but I also don’t think it will be super noticeable when wearing it. Only time will tell if the charger improvements outweigh the design changes here.

Speaking of the charger, it’s also worth noting that Google improved the battery life. The company claims the Watch 4 now lasts up to 30 hours, while the Watch 4 XL now lasts 40 hours. Any improvement to battery life is welcome in my eyes, but I’d love to see Google get it all the way to 48 hours for true two-day battery life. Google boosted the charging speed by 25 per cent, and now promises a zero to 50 per cent charge in just 15 minutes, great for a midday top-up.

Other notable improvements include a more powerful co-processor that increases on-wrist AI computing without sacrificing power. Additionally, the Pixel Watch 4 boasts enhanced fitness features through Fitbit, like more accurate GPS route tracking for hikes and runs. The improved speaker mentioned above includes a haptic engine for clearer audio and stronger haptics, which Google claims should improve the feel and sound of interacting with Gemini on your wrist.

Overall, the Pixel Watch 4 sounds great on paper, and my first impressions are generally pretty good. However, you’ll have to wait until October for a full review of Google’s latest smartwatch.

MobileSyrup may earn a commission from purchases made via our links, which helps fund the journalism we provide free on our website. These links do not influence our editorial content. Support us here.

Related Articles

Fatal error: Uncaught Aws\S3\Exception\PermanentRedirectException: Encountered a permanent redirect while requesting https://ms-staging-baselayer-static-assets.s3.ca-central-1.amazonaws.com/?list-type=2&delimiter=%2F&prefix=uploads%2Fwpcf7_uploads%2F. Are you sure you are using the correct region for this bucket? in /var/www/html/vendor/aws/aws-sdk-php/src/S3/PermanentRedirectMiddleware.php:49 Stack trace: #0 /var/www/html/vendor/guzzlehttp/promises/src/Promise.php(209): Aws\S3\PermanentRedirectMiddleware->Aws\S3\{closure}(Object(Aws\Result)) #1 /var/www/html/vendor/guzzlehttp/promises/src/Promise.php(158): GuzzleHttp\Promise\Promise::callHandler(1, Object(Aws\Result), NULL) #2 /var/www/html/vendor/guzzlehttp/promises/src/TaskQueue.php(52): GuzzleHttp\Promise\Promise::GuzzleHttp\Promise\{closure}() #3 /var/www/html/vendor/guzzlehttp/guzzle/src/Handler/CurlMultiHandler.php(163): GuzzleHttp\Promise\TaskQueue->run() #4 /var/www/html/vendor/guzzlehttp/guzzle/src/Handler/CurlMultiHandler.php(189): GuzzleHttp\Handler\CurlMultiHandler->tick() #5 /var/www/html/vendor/guzzlehttp/promises/src/Promise.php(251): GuzzleHttp\Handler\CurlMultiHandler->execute(true) #6 /var/www/html/vendor/guzzlehttp/promises/src/Promise.php(227): GuzzleHttp\Promise\Promise->invokeWaitFn() #7 /var/www/html/vendor/guzzlehttp/promises/src/Promise.php(272): GuzzleHttp\Promise\Promise->waitIfPending() #8 /var/www/html/vendor/guzzlehttp/promises/src/Promise.php(229): GuzzleHttp\Promise\Promise->invokeWaitList() #9 /var/www/html/vendor/guzzlehttp/promises/src/Promise.php(272): GuzzleHttp\Promise\Promise->waitIfPending() #10 /var/www/html/vendor/guzzlehttp/promises/src/Promise.php(229): GuzzleHttp\Promise\Promise->invokeWaitList() #11 /var/www/html/vendor/guzzlehttp/promises/src/Promise.php(69): GuzzleHttp\Promise\Promise->waitIfPending() #12 /var/www/html/vendor/aws/aws-sdk-php/src/AwsClientTrait.php(58): GuzzleHttp\Promise\Promise->wait() #13 /var/www/html/vendor/aws/aws-sdk-php/src/ResultPaginator.php(151): Aws\AwsClient->execute(Object(Aws\Command)) #14 /var/www/html/vendor/aws/aws-sdk-php/src/functions.php(52): Aws\ResultPaginator->valid() #15 /var/www/html/vendor/aws/aws-sdk-php/src/functions.php(69): Aws\map(Object(Aws\ResultPaginator), Object(Closure)) #16 [internal function]: Aws\flatmap(Object(Aws\ResultPaginator), Object(Closure)) #17 /var/www/html/wp-content/plugins/s3-uploads/inc/class-stream-wrapper.php(695): Generator->valid() #18 [internal function]: S3_Uploads\Stream_Wrapper->dir_readdir() #19 /var/www/html/wp-content/plugins/contact-form-7/includes/file.php(362): readdir(Resource id #734) #20 /var/www/html/wp-includes/class-wp-hook.php(322): wpcf7_cleanup_upload_files() #21 /var/www/html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array) #22 /var/www/html/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #23 /var/www/html/wp-includes/load.php(1280): do_action('shutdown') #24 [internal function]: shutdown_action_hook() #25 {main} thrown in /var/www/html/vendor/aws/aws-sdk-php/src/S3/PermanentRedirectMiddleware.php on line 49