Pixel Watch 5

Original Article ↗ Hacker News Discussion ↗

Google’s new Pixel Watch 5 draws interest for its advanced health features—like AI-driven trend reports on blood pressure, sleep breathing and insulin resistance—but is widely criticized for its ~30–40 hour battery life, which many see as incompatible with all‑night sleep tracking and multi‑day trips. Commenters contrast it with Garmin, Pebble, Amazfit and Fitbit devices that last a week or more, debate round vs rectangular designs, and question the trade‑off between rich smartwatch features, constant charging, and sending sensitive health data to Google’s cloud.

Battery life & charging expectations

  • Core objection: advertised 30–40 hours is seen as “utterly useless” for a watch marketed for sleep tracking and all‑day use.
  • Many want at least 3+ days; outdoor and endurance athletes want 24+ hours of continuous activity tracking without planning around a charger.
  • Users compare negatively to Garmin, Amazfit, Pebble, Withings, older Huawei, Casio, etc., which commonly last a week to a month.
  • Counterpoint: some say daily charging becomes a routine (e.g., during shower or evening downtime) and fast charging mitigates the pain, though forgetting even once is disruptive.
  • Concern that 30 hours will degrade further over time, making sleep + morning workout tracking unreliable.

Health features, AI, and trends

  • New “Health Coach” and monthly trends (blood pressure, sleep breathing quality, insulin resistance) spark both interest and skepticism.
  • Some see potential value for populations affected by metabolic issues; others question how meaningful or accurate these trends can be without direct glucose or BP measurement.
  • Several note “trends” language and monthly summaries likely reflect regulatory and accuracy limits; comparisons to CGMs and lab tests are unfavorable.
  • Fitbit users report current “Google Health Coach” as low quality, raising doubts about future Pixel Watch implementations.

GPS & cloud dependence

  • Location accuracy improvements (3D building models, advanced algorithms) are welcomed, and external test links are referenced.
  • Concern that cloud‑assisted GPS requires LTE or a paired phone, undercutting true standalone use.

Privacy, ecosystem lock‑in & openness

  • Significant discomfort with health data being continuously uploaded to Google; full functionality appears to require cloud processing.
  • Some want local data and use Gadgetbridge‑compatible devices (Garmin via 3rd‑party, Amazfit, Huawei Band, Xiaomi) or remain fully Google‑free.
  • WearOS dependence on Google Play Services is a blocker for privacy‑focused Android users; custom firmware options are still immature.

Form factor & UI

  • Ongoing debate over round vs rectangular: round is considered more “watch‑like” but awkward for text, lists, and widgets.
  • Some argue Apple’s rectangular design is functionally superior and commercially validated; others prefer round aesthetics and minimal interaction.

Use cases, alternatives & overall sentiment

  • Most actual usage clusters around: time, timers, notifications, payments, “find my phone,” fitness/sleep tracking, and sometimes navigation or calls.
  • Many feel WearOS/Pixel Watch over‑indexes on apps and AI while under‑delivering on battery and simplicity.
  • Garmin, Pebble Time 2, Amazfit Bip, Fitbit Air, Withings, and simple Casios are repeatedly praised as better matches for long battery life, basic health tracking, and fewer distractions.
  • Overall tone: wary to negative on Pixel Watch 5 for battery, cloud dependence, and feature bloat; modest enthusiasm for GPS advances, repairability, and AI‑driven health insights if they prove reliable.