I am currently developing an android app that uses the sensor.community API
I’ve long wanted to display the sensors I need in a dashboard format.
Also, to have quick access to the values from my own sensor.
Sensors can be added to the app via the map or by manually entering the ID.
You can regularly share a summary of PM sensor data with your local community using the “Share” feature.
My application has now been accepted into the official F-Droid repository. If you use F-Droid, you can install it directly from there and receive updates automatically.
F-Droid: My Sensor | F-Droid - Free and Open Source Android App Repository
The source code is still available on GitHub: GitHub - saiinc/MySensorAirData: This app retrieves PM and Temperature/Humidity/Pressure data from sensor.community and displays it on an Android smartphone. · GitHub
I have also completed an iOS version of the application. At the moment it isn’t publicly available because distributing iOS apps requires an Apple Developer Program membership. If there is ever interest from the Sensor.Community project in providing an official iOS app, I’d be happy to discuss possible ways to make that happen.
Thank you very much for this great project! 
Hi! I have a question about the licensing and appropriate use of historical sensor data in my app.
Sensor.Community links to the Database Contents License (DbCL), which refers to the Open Database License (ODbL). I’m exploring a native chart using historical measurements served through the Grafana instance at api-rrd.madavi.de:3000.
The intended use would be user-initiated: the app would fetch data when someone opens a sensor’s chart or selects a different time range. It would store the fetched measurements only in a local database on the user’s device and request only the portions of the selected range that aren’t already cached. I don’t plan to run bulk downloads or background collection.
Would this use be permitted under the applicable data licence and any service-specific terms? If so, what attribution should the app display, and are there request-rate or caching limits we should follow? Also, could you point me to the person or team responsible for the historical-data service and its terms of use?
Thanks!
