> Garmin, Polar, Suunto, Apple - you name it. I'm not a web health app developer, I'm a wearable developer: I name "Open Smartwatch GPS" [1] (currently in deve

> Garmin, Polar, Suunto, Apple - you name it. I'm not a web health app developer, I'm a wearable developer: I name "Open Smartwatch GPS" [1] (currently in development). There's not a lot of data yet, but how could I (or, more importantly, future users of Open Smartwatch, or future users of phone and apps that would want to serve health and movement data) connect to your service? Can an end user upload/push raw data as JSON, CSV, or as MQTT messages, and access it from an arbitrary health app that uses your service? > On our end, we deal with the providers' standards. Ha! Wearable hardware "standards". Good joke! Do you integrate with GPSBabel [2] on the backend? But a commendable effort; there's a lot of wonky hardware out there, so thanks for unifying the multitude of providers. Also, how does your service compare to Tapirik? [1]: https://open-smartwatch.github.io/ https://open-smartwatch.github.io/ [2]: http://www.gpsbabel.org/htmldoc-1.7.0/The_Formats.html http://www.gpsbabel.org/htmldoc-1.7.0/The_Formats.html [3]: https://tapiriik.com/ https://tapiriik.com/