Local timeline generation

[matthewwardrop]

(cross-posting from coredevices/mobileapp#3 by request)

Historically the Pebble timeline was generated and stored off-the-device in the cloud, which allowed for external data pushes. In modern mobile APIs, though, it would be somewhat convenient to just let libpebble3 (or its Android app shim) generate the timeline locally (perhaps stitching in additional pins from the external API). This has multiple benefits, including increased performance, privacy, and reduced dependence on external services (which means we can keep our Pebble devices fresh for even longer without external REST APIs).

I'd actually really love for watch faces to be able to access the timeline data, perhaps gated by permissions, so that we don't have to set up our own authentication with Google Calendar or other services... especially since the timeline is already curated and available.

I'm curious if there has been development or thought along these lines?

Thanks for all your work here!