Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Persistent notification for in-progress events #82

Open
gingerbreadassassin opened this issue Nov 1, 2024 · 1 comment
Open

Persistent notification for in-progress events #82

gingerbreadassassin opened this issue Nov 1, 2024 · 1 comment

Comments

@gingerbreadassassin
Copy link

gingerbreadassassin commented Nov 1, 2024

Would be nice to have a persistent notification for feedings, pumping, tummy time in progress

Extra points for lockscreen notifications

Apologies for the curt nature of my issues as I am writing them with one hand while holding an infant in my other

@MrApplejuice
Copy link
Collaborator

Hey! Yes, I would like to have those as well. But, unfortunately, this is a very complicated feature to add. Updating the timers requires persistent checks to the server and therefore this requires the mobile phone to poll the state of the babybuddy server. This, in turn, means that for correctly showing the state while the app is not open, it would need to remain open in the background.

And all of a sudden, I created a battery drainer-feature only for a, imo, slight convenience. This is why I did not add this feature yet, even though I would have loved it as well.

The problem here is that Babybuddy in its nature is a decentralized service, power to the users etc. Other services can get around this issue, if I understand it correctly, by implementing push notifications that are sent out via google services to the mobile phone which are way more power efficient. The app then can react to those notifications and update timers. This requires an active component in babybuddy though and then each and every installation of babybuddy needs its own API key for google push notifications (or whatever that feature was). A total mess for a decentralized app.

If you, or anyone else would have a good idea to avoid these issues, I am all ear!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants