Responding to Raduque's questions/concerns from the other thread:
I don't take watch apps seriously. There's very little use I have for apps beyond what's included with Android Wear (notifications, answering calls is pretty much it) and anything more complicated is unusable on a small screen.
It's more the accessibility and priority than anything. In Android Wear, you have to either speak out the name of your app (which is usually a terrible idea) or scroll all the way to the bottom of a menu before you can even start
browsing apps. On an Apple Watch? Tap the crown. Watch apps can only be so sophisticated, but it'd nice to have an OS that actually encourages you to start tasks from your watch instead of Google's "oh, if you must" attitude.
I'm not sure what you mean by this contextual menus). If you mean more options on the long-press menus, I'm sure it's going to be in the next update for AW.
On the Apple Watch, a "force touch" (basically, a hard press) brings up a contextual menu for the app at hand. You can tell the music app to stream to your TV, for example. True, Android Wear could get something like this soon... but it doesn't have that now.
Typing on a 1.x" screen (as opposed to live voice dictation)?! No thanks!
Apple's not asking you to type. If you get a text message on the Watch, you can also use a pre-selected text response (if someone asks "A or B," for example, you can respond with A or B) or record a short voice message. There's also a walkie talkie mode that lets you have a back-and-forth voice chat, although you'll need Apple Watches on both sides for that to work.
How are you going to show content on a tiny screen, and have it be readable, without obscuring part of the screen?
That's what the crown is for. You can zoom and scroll in apps without having to put your finger on the screen and obscure what you're looking at.
Point of this (Wi-Fi)? Other than draining the battery?
There's a couple of reasons. First, it allows for high-bandwidth tasks that wouldn't work so well over Bluetooth. I'm not sure how often that'll crop up, but it's there. The more important one is that you're not limited by Bluetooth's 33-foot range -- you could still get data without having to be close to your phone.
Motorola 360 does this (inductive charging) now.
This was a specific gripe with the ZenWatch, not Android Wear stuff in general. Although it is true that a lot of Android Wear devices sadly resort to cables and cradles.
It's subjective whether or not it (the ZenWatch) looks good on thin wrists. Now, if you had said it fits better on thin wrists, I might have agreed with you if I knew what the Apple Watch looked like on a thin wrist.
The general rule is that you don't want an oversized watch on your wrist -- otherwise, you look like the smartwatch equivalent of Flavor Flav. The real issue, I'd say, is that most of the current Android Wear crop basically doesn't acknowledge that you exist if you either have thin wrists or prefer relatively subtle wristwear. Here's what the smaller 38mm Apple Watch looks like on an average man's arm (via Hodinkee
http://www.hodinkee.com/blog/hodinkee-apple-watch-review ):
See what I mean? That looks more like a watch and less like a giant screen strapped to your arm. A subtler design like this makes smartwatches more accessible, more socially acceptable.