Compilations not real time?

I think the app/complication shown at WWDC was for an electric Volkswagen. But it did show charge remaining which would have to be in real time since that is SUPER important. On the wOS 2 purview page Apple shows a CNN Top Story and flight info. Both of this would need to be very current. It as says:

"...So you can easily check your United flight times or keep an eye on home devices — lights, thermostat, sensors, cameras..."


EDIT found some info on it: http://www.macworld.co.uk/how-to/iosapps/how-make-apps-for-apple-watch-watch-os-2-3618195/

"...Complication that takes the form of a VW logo with a circular bar at the edge that gets closer to completion as the battery charges...."

 

OP, just fyi they care called complications

 

I think the developer may have a little more work to do...

https://developer.apple.com/library...h2TransitionGuide/DesigningaComplication.html

Note that a complication can be setup with the data for current and future times (and past as well.) So it could be pre-defined to have the data to display accurately. I think in the case OP mentions the developer could just calculate the wage and time for now, and 15 mins from now, and 30 mins from now. Then when the complication is rendered it can show the correct data. When WatchKit asks for updated data, the watch app can update those numbers again. That way the complication always has 'current' (if maybe a little bit of an estimate) data.

The multiple data points also help when the user scrolls in Time Travel mode to show past and future data.

 

3rd party complications are as real time as other complications.

Rudmentally paraphrasing the docs, devs should be prepared for the OS to reach out and check for updates at any time - regardless of app state.