- the "Always active" watchfaces (kind of a marketing term, as users have been able to see a watchface at any time on garmins, and really a "1hz update with watchfaces" so always on seconds, and 1 hz update of other things on the display!)
- The whole background process part (WAY cool!)
- The debugger ("lions, and tigers, and breakpoints, oh my!" - Hey, Garmin is in Kansas! :) )
Initial reaction:
- 1hz - Once you learn the technique, doing seconds on a digital WF is fairly straightforward. When to clip, and when to clear the clip!. Analog watch faces with a second hand, a bit more is involved, but the Analog sample in the SDK shows you how... The thing to note here, is while a WF can update parts of the screen at 1hz, the underlying data is still changing at the same rate as before, For example,if you update the HR on the watchface at 1hz, it doesn't change that getHeartRateHisory() still will only changed every minute or two.
- background processes are VERY COOL. No more details on what I'm trying so I can publish my apps first! :)
- Debugger - still a bit green IMHO, but this is a beta and garmin is looking for feedback. I have used it a number of times to set a breakpoint and check out what's in certain variables, and avoid the Sys.println() that never seem to be commented out when building for the store!