Open samuelgrigolato opened 9 years ago
Hello,
This is a very good idea, there already is a mechanism for pulling for the widget, you may reuse that. Actually there's a lot of room for improvment all over the app..
We plan to make a sprint during the 31C3 adding feature and overhaul the app quality in general.
Regards.
Could you please enlighten me what the meaning of "31C3"?
Just to proper credit the idea: it first appeared in Garoa Hacker Clube (Brazilian hackerspace) mailing list.
it's a hacker cutlure conference in Hamburg, see https://events.ccc.de/congress/2014/wiki/Main_Page
That's a nice idea. I started implementing a prototype using the JobScheduler API.
Note however that at least on newer Android versions, the check interval must be at least 15 minutes. I would also add the constraints that it may only run if battery is not low, and if the user is on an unmetered network (that could be made configurable).
Does the feature still sound useful if the notifications are not immediate, but may take a few dozen minutes until they trigger?
Any real-time notifications would need to be done server-side using push notifications. We can't do that in MyHackerspace.
Hmm, prototype is already kind-of-working:
However, the scheduled jobs do not survive an app upgrade: https://stackoverflow.com/questions/42983357/do-android-scheduled-jobs-survive-an-app-upgrade
That means that we would need to store the jobs somewhere else as well, and to re-schedule them on app start if there are no scheduled jobs... This is getting a bit more complex than I expected.
I still think it would be nice to have though.
I was thinking about the following feature:
Any considerations? I'm willing to put some effort on this matter.