[FLGMwt]

I'm surprised there's not much mention of the different app architecture for Pebble vs Apple Watch.

For Apple Watch, all application code lives on the phone and every interaction on the watch requires a round trip to the phone and back. This contributes to the shoddy battery life, sure but I'm mostly concerned about latency. When writing your app, you really only use a designer in Xcode.

For the Pebble, code for watch-specific behavior lives and executes on the watch itself, along with two options for logic on the phone: 1) a native companion app which the watch talks to (more like the way Apple Watch apps work, but with code split across devices) and 2) arbitrary javascript which runs in a execution sandbox that all the Pebble watch apps share.

Anyone think that the Apple Watch approach is a better idea? Tempted to get one to compare.

[TazeTSchnitzel]

> For Apple Watch, all application code lives on the phone and every interaction on the watch requires a round trip to the phone and back.

IIRC this is just for now, and they're going to have native apps soon, but the SDK for that isn't ready yet.

I wonder if the (current) Apple Watch approach is better battery-life wise, given that it avoids any data syncing and does any and all heavy processing on the iPhone rather than the watch.