but then you are defeating the purpose of wearing a smartwatch, which I believe is to keep receiving notifications for calls, emails, messages and so on. If you only wake up the CPU every minute to check then it's far too slow to be useful.
Is the idea of a smartwatch to be your main phone, small enough to strap to your wrist? I imagined that it was more like a really good watch - primarily there to tell the time, but allowing you to use it as a phone when that would otherwise be inconvenient.
I played around with a prototype of an Android watch, and it just seemed too small to be useful. It seems like a remote control to a smartphone would be more useful - something that vibrated when I get a notification, and could send commands to Siri.
It is a remote control to your smartphone - the current Wear crop don't handle any of the phones' tasks, and it vibrates when I get a notification or phonecall...
So, for example, I could tell my phone to notify the watch when I receive a call or text message from my wife? Then when she calls, the watch vibrates.
Would that be expensive from a power consumption perspective? I know next to nothing about hardware, so perhaps I'm being naive.
Well, at the minute, it vibrates when anyone calls or texts, all Wear is is a little screen showing Android's notification system and replicating the alert structure on your device already (e.g. when I get an email, it sits in the notification bar on my phone, but I chose not to vibrate, and on Wear is opens a notification, but doesn't vibrate. Whereas for a text it vibrates on my phone, and so it vibrates the watch as well. Doesn't have sounds, so the watch doesn't ring). It does cost battery life, hence the discussion surrounding it elsewhere in the post.
