|
|
|
|
|
by dns_snek
405 days ago
|
|
Wear OS needs core development and an army of QA testers, not another redesign. The design is fine, but overall the functionality of the product feels like a beta test (and I think that's being generous), even on their own hardware. I answer a call on my phone and the audio is routed to my watch, or vice versa, the official weather app claims it can't get my location even though it has access to the GPS (and it's actively being used by Fitbit to track exercise) and wifi positioning. Google Maps on the watch doesn't load results half the time, the other half the time it'll get stuck on "starting navigation" - sometimes unstuck by launching Maps on the phone (despite having offline maps downloaded to the watch) and other times it's just stuck forever. Fitbit will display some static/mock/fake exercise values until the display is woken up when OS-level always on display is disabled but AOD is enabled in Fitbit during exercise. I could go on. |
|