<story><title>Pixel Watch 3</title><url>https://blog.google/products/pixel/google-pixel-watch-3/</url></story><parent_chain></parent_chain><comment><author>vially</author><text>For anyone considering buying the Pixel Watch 3, please keep in mind that Pixel Watch 2 has some long-standing issues where the GPS completely cuts out during runs or walks.&lt;p&gt;Some users believe it to be a hardware issue but it&amp;#x27;s still unacknowledged by Google and the forum thread where people have been discussing it has just been locked recently. Just mentioning it for awareness and visibility.&lt;p&gt;- &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;community.fitbit.com&amp;#x2F;t5&amp;#x2F;Android-App&amp;#x2F;Google-Pixel-Watch-2-GPS-data-missing&amp;#x2F;td-p&amp;#x2F;5476172&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;community.fitbit.com&amp;#x2F;t5&amp;#x2F;Android-App&amp;#x2F;Google-Pixel-Wat...&lt;/a&gt;&lt;p&gt;- &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;support.google.com&amp;#x2F;googlepixelwatch&amp;#x2F;thread&amp;#x2F;242833127?hl=en&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;support.google.com&amp;#x2F;googlepixelwatch&amp;#x2F;thread&amp;#x2F;242833127...&lt;/a&gt;</text></comment>
<story><title>Pixel Watch 3</title><url>https://blog.google/products/pixel/google-pixel-watch-3/</url></story><parent_chain></parent_chain><comment><author>modeless</author><text>My Pixel Watch sucks and it&amp;#x27;s not because the screen isn&amp;#x27;t big or bright enough. The implementation of notifications is awful. It&amp;#x27;s actually faster and easier in many cases to whip out my phone to see a notification than to see it on the watch.&lt;p&gt;Why? Because notifications are not shown by default. The watch vibrates but nothing is there on the screen but the watch face. To trigger a notification to actually show, you need to rotate your wrist down (if it is up) and then up again (impossible if you are carrying something). Then you have to wait for it to recognize the gesture. Then you have to wait for a fade animation to an intermediate screen that shows half of the information about the notification. Then you have to wait for a fade animation to the final screen that actually shows the notification text. And if you lower your wrist at all during or after this process, the notification disappears instantly and won&amp;#x27;t come back without the use of both hands to activate the touchscreen or crown. And in many cases the information shown is useless, like &amp;quot;so-and-so sent a picture.&amp;quot; Show me the goddamn picture then!&lt;p&gt;It boggles the mind that anyone could think this is a good experience to ship at all, let alone for three generations! Especially when Pebble had it right 10 years ago. You show the notification on the screen &lt;i&gt;first&lt;/i&gt;, &lt;i&gt;then&lt;/i&gt; you vibrate the watch, then you leave the notification there for at least 30 seconds so it can be read. You show the whole notification at once (as much as possible on the small screen, of course), and you also show a small clock at the top so you can still see the time while the notification is shown. How hard is that?&lt;p&gt;Of course this isn&amp;#x27;t the only way the Pixel Watch software sucks. The whole UX is pretty terrible, like they had some ideas and went straight to final implementation, never bothering to iterate based on user feedback. Low information density, low customizability, feature-poor, unresponsive interactions, blocking animations. It&amp;#x27;s everything bad about modern UI in a tiny frustrating package.&lt;p&gt;I don&amp;#x27;t know what is wrong with all the tech reviewers that fail to call Google out on this stuff. Maybe it&amp;#x27;s better than Samsung or whatever but that doesn&amp;#x27;t make it good. At least the hardware is nice. Though, like all smartwatches except the Pebble Time Round, far too thick.</text></comment>