Fitbit Community,
As Fitbit recommends in their documentation, it's important to not entirely rely on the Subscription API to provide the data from Fitbit users flawlessly.
I would like to reach out to you to get best practices, expieriences and designs on on how to craft an application that can take advantage of near real-time updates (Subscription API) and also be resilient enough to get or pull data that got missed.
Questions I would like your input on:
- Besides the Subscription API, what other mechanism or reconcilliation process have you developed to get the missing data (due to network errors, etc.)?
- How did you make this reconcilliation process smart or intelligent enough to minimize the amount of data to pull?
I would love to hear experiences or ideas about this.
Thanks you all!
