After building the API, the widget and the dashboard, we started onboarding more and more apps. The variation of what people are building on top of Terra today is crazy. From the fitness space, to the sleep space, to the wellness space, and even mental health. We are surprised on a daily basis.
There are apps building nutrition recommendations based on your glucose data, or apps giving you better cycling recommendations based on your performance, or even a sleep mattress that improves your sleep based on your HRV. Music apps that customise your music based on your heart rate.
However, with all this variation there emerged a challenge. Every app needs different data - and not all of it.
Let's run through a specific example. A Garmin Fenix 7 measures data such as respiration, heart rate, HRV, sleep, stress levels, GPS location, and even body temperature. In a high sampling rate, the GPS location data, and the heart rate data per activity is significant in terms of data size.
A music app making personalised song recommendations tailored to you would only need your heart rate. But a cycling app would need your location, sleep, recovery and so on.
Through the dashboard, we created data customizations. Any developer can now choose the type of data AND frequency through which they receive that data.
Here's how it works:
a) choose the scope of data you want to access. For example, if you only need sleep data, then simply enough you choose this from the dashboard.
b) choose the frequency of when to receive said data. You can go from instant, to 24 hours!
Are you building a music app? You can now avoid receiving bulk GPS data, since you don't need it. Do you have a machine learning app that needs a lot of data? We've got you covered.
