As an original Kickstarter backer to the original one and even the Early Bird for the Pebble Time, I was happy with the multitude of watchfaces, apps, and games. Even the Time was to be backwards compatible with many of the thousands of apps already out there. Remote control of music was my most used feature, especially as a commuter.
But notifications were its pain point, in my opinion. Limitations by Apple prevented replying to text messages, emails, or notifications. Android had far less limitations because they were able to send back much more control to the smartphone it was connected to.
Battery life didn't matter so much. I always topped off every night, though it was nice that I could forget a day or two and not even have to worry.
When WATCH was announced, I knew it would be more interactive, and it proved itself as such in the various demos. Speakerphone capabilities and Siri were icing on the cake. I immediately canceled my Early Bird pledge for the Time, and I don't regret the decision once I slapped on my WATCH on my wrist.
The one thing that I did recently realize is this: most WATCH apps won't run without it connecting back to the iPhone. To compare, this is what happens when you want to play a Video Poker app on the Pebble, versus a Video Poker app on the WATCH, both not connected to any nearby smartphone. Even if the WATCH app has no use of internet or network connectivity, it appears that every WATCH app acts like a remote session back to the app running in the background on iPhone. The app on the iPhone sends the image or data, the WATCH sends back touch responses back to the app on the iPhone, rinse, repeat. That's probably why there are no fluid or fast action games like Flappy Bird or Angry Birds, nor even any finger swiping for games like 2048 - only tap on a side of a screen.

But notifications were its pain point, in my opinion. Limitations by Apple prevented replying to text messages, emails, or notifications. Android had far less limitations because they were able to send back much more control to the smartphone it was connected to.
Battery life didn't matter so much. I always topped off every night, though it was nice that I could forget a day or two and not even have to worry.
When WATCH was announced, I knew it would be more interactive, and it proved itself as such in the various demos. Speakerphone capabilities and Siri were icing on the cake. I immediately canceled my Early Bird pledge for the Time, and I don't regret the decision once I slapped on my WATCH on my wrist.
The one thing that I did recently realize is this: most WATCH apps won't run without it connecting back to the iPhone. To compare, this is what happens when you want to play a Video Poker app on the Pebble, versus a Video Poker app on the WATCH, both not connected to any nearby smartphone. Even if the WATCH app has no use of internet or network connectivity, it appears that every WATCH app acts like a remote session back to the app running in the background on iPhone. The app on the iPhone sends the image or data, the WATCH sends back touch responses back to the app on the iPhone, rinse, repeat. That's probably why there are no fluid or fast action games like Flappy Bird or Angry Birds, nor even any finger swiping for games like 2048 - only tap on a side of a screen.
