You will need to choose a "client name" for your app. A "client name" is used to identify data in the Tidepool Platform that your app has created. We recommend using reverse DNS notation to identify your app/service. For example:
com.mycompany.TidepoolUploader(company)com.github.pazaan.600SeriesAndroidUploader(personal project)
Your client will also need to provide a Semantic Version to identify which version of your app/service is uploading data.
Platform has two data upload modes:
You will need to determine which mode is the best to use for your upload implementation.
A normal upload session is used for "bulk" uploads.
An example of this is the Tidepool Uploader: When you use Tidepool Uploader, you are connecting a device to your computer, and using the Tidepool Uploader to read a large set of historical data from the device. Tidepool Uploader will create a normal upload session, and close that session when all data for that diabetes device has been uploaded.
Subsequent uploads for the same device will create a new normal upload session, and this data will be deduplicated against any previous sessions.
A continuous upload session is used for devices that have the ability to connect to the internet (either directly or via a tethered device), and frequently upload data to the Tidepool platform.
An example of this is Tidepool Mobile, which uploads updates from the Dexcom or Loop apps (via HealthKit) every 5 minutes.
You are still able to use a continuous upload session to upload a large amount of historical data.
TODO: Section on deduplicators goes here.