02-20-2013 01:59 PM
BB is looking into providing "headless" apps in the future (apps without a GUI). Consider them background apps, but BB does not want these apps to run all the time if they do not need to (wasting resources and providing the user with a less of a positive experience). The idea is to have these headless apps be triggered by invocation, do their task and then exit when done. BB is looking for a list of use cases and trigger events that anyone can think of would occur for current or planned apps. Triggers like:
Please add you triggers that you would like to see that would allow an app (real or headless) to be invoked.
02-21-2013 09:16 AM - edited 02-21-2013 09:16 AM
Don't know which or if any of these are already implemented:
02-22-2013 08:32 AM - edited 02-22-2013 08:36 AM
Also not sure what is already implemented, but:
02-22-2013 08:57 AM
02-22-2013 09:25 AM - edited 02-22-2013 09:27 AM
In regards to GPS speed thresholds, I think it might need to be an average speed for some time threshold. For example, > 30m/s for 30 seconds. If not, you will be getting apps starting pretty violently because of erratic GPS updates and driver behavior.
Totally agree ... things like GPS and accelerometer data need to filtered appropriately per the application.
Sounds like you're talking about making a hysteresis curve for the raw datafeed; makes sense for thermostats, and makes sense for this application.
02-24-2013 08:29 PM - edited 02-24-2013 08:32 PM
Limiting headless apps to predefined use-cases like this probably will stiffle innovation. Look how limited background apps on IOS are, and the stick that Apple has had for it...
But it's a start, I guess. I'll add:
Apps should also have the ability to enable/disable/pause/resume/configure these notifications via an API, not just statically in their manifest file.
02-25-2013 12:10 PM