3 ms·
You're right, the public timeline API does require hitting our servers. However, the calendar pins we push from our mobile apps do not use that public API and
by fra 10y ago
You're right, the public timeline API does require hitting our servers.
However, the calendar pins we push from our mobile apps do not use that public API and thus do not - as far as I know - hit the cloud.
- TeMPOraL 10y agoAny plans on changing that? I mean, there doesn't seem to be anything in Timeline that inherently requires routing stuff through your server. That's the one thing that always perplexed me - you could do almost anything to Pebble without touching the outside world, and here there's that one thing that suddenly requires the cloud. If I may ask, what is the reason you built it this way?
- IanCal 10y agoYou can put things in the timeline from an external place, so I can push something to many timelines (e.g. sports scores) using pebbles API. That definitely requires going through pebbles servers.
- TeMPOraL 10y agoMakes sense, but it still shouldn't preclude my companion app from pushing pins to my watch's timeline completely off-line. The sane model seems to be a timeline stored locally on your Pebble app that can be synced to the Pebble cloud. What I understand from the current model is that Pebble app is just a dumb cache.