6 ms·

Please, just deliver something that isn't just kinda shit first and then I'll be happy to hear about how you want a more coherent branding experience.

• ProAm 9y ago
  Android Wear Hangouts?
  • forgottenpass 9y ago
    Not to be confused with Android Hangouts Wear, a completely different google product.
• drewg123 9y ago
  +1 to this. I used a Polar M600 for the last year, and the long anticipated AW 2.0 update pretty much ruined it. After the upgrade, Play Music lost the ability to shuffle on-device content. The worst thing was that the watch was divorced from the phone, and my "google managed" gsuite account wanted to install Android Device Policy manager, which then wanted me to enable a PIN (annoying) and encrypt the watch (impossible), so I lost access to Google authenticatior on the watch, which was pretty much the only advantage it had over a non-Androidwear smartwatch. I just replaced it with a Garmin that also does BT music (which can shuffle!), and I"m loving week-long battery life vs the 1-day at most life. The notifications work just as well. I'm beginning to think that full-blown Android (or WatchOS) is just a bad idea for watches, and companies like Garmin and Fitbit have a much better platform.
  • jsight 9y ago
    Third party google authenticator applications worked (and continue to work) really well on the Pebble as well.
    • drewg123 9y ago
      The problem is that (AFAIK) there can be only one authentictor per account. So to move it to my watch, I'd have to remove it from my phone. And that makes me ... nervous.. The nice thing about the android wear authenticator was that it could be both on the watch and the phone at the same time.
      • jsight 9y ago
        I haven't set up the official Google Authenticator app in a while, but what I have done in the past is to seed the watch with the same value as the phone app. It marginally increases the risk, as I now have two devices that could be stolen, but the convenience was worth it to me. That may require using a third party app on the phone as well as the watch, though. I'm not sure if the official Google Authenticator app still makes this practical.
        • drewg123 9y ago
          Ah! That's a great idea. I had not considered that..
  • dmix 9y ago
    How is the Garmin SDK/app development ecosystem? I didn't know they had their own app store until today (https://apps.garmin.com/en-US/ https://apps.garmin.com/en-US/). Edit: wow they developed their own language called Monkey C for the platform? Speak about NIH, jeez. I thought making a new app store AND platform was brave enough, and they decided to throw a language on top of it. https://developer.garmin.com/connect-iq/monkey-c/ https://developer.garmin.com/connect-iq/monkey-c/
• Twirrim 9y ago
  Wear 1 wasn't bad. Had some warts, but wasn't bad. Wear 2 convinced me that the developers don't actually use the devices they're writing software for. I've lost count of the number of times I glance and my watch and discover the watchface has changed because something has rubbed up against the screen. Almost everything that happens as part of standard interaction with a device has been put multiple steps away from you.
  • ibdf 9y ago
    The watch face "swipe to change" is one awful "feature". I use my watch less and less because it's so annoying to get to the information you need to.
    • Twirrim 9y ago
      That's probably one of the most annoying changes between 1 and 2. I've made it so only one watch face shows up.