Thanks jabol20 for this suggestion. Yes, using URL schemes makes sense for me.
Also, we need support for other another source of external control: smartwatches (to display basic parameters and start/stop recording).
I think it would be great if we could add 3 new features in the next release:
- URL schemes to control Run.GPS from other apps
- Smartwatch support
- Support for BLE speed and cadence sensors
22.10.2013 11:05:05 UTCgeändert am 22.10.2013 11:06:18 UTC
I wrote about AutomateIT, beacuse I use it to turn off wifi and screen lock, when RunGPS starts. But you can take opposite way: register custom url scheme for RunGPS with commands within them.
URLs can be easily written on NFC tag (or launched from email or sms ;)). In this way we can write on tag urls like:
rungps://start
rungps://stop
rungps://selected-sport=cycling
and so on
Should not be too difficult to define an "Intent" (this is the Android term for triggering actions) inside the Run.GPS app that allows for starting/stopping a training.
One problem though: In AutomateIT you can only start an app, but you cannot provide parameters, so it won't be possible to send commands like "start" or "stop" or "setsport 'cycling'" to the app. Any ideas? Do you know an NFC app that can send an Intent with parameters to an app?
It would be very nice if Run.GPS would provide some form of API so it would be possible to start some functions from other applications. I'm thinking about way to start/stop training by NFC tag.
My dream solution would be to put NFC tag on bicycle and write script (for AutomateIT for example) which would:
- launch Run.GPS
- select cycling sport
- start training