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

Android user should be prompted to enable background battery usage #2698

Open
holmesworcester opened this issue Jan 16, 2025 · 1 comment
Open

Comments

@holmesworcester
Copy link
Contributor

holmesworcester commented Jan 16, 2025

Quiet networks will be more reliable if Android apps can run continuously in the background. To do this, users need to give the app permission. (We might choose not to run in the background when the user is on mobile data and is using QSS, to save battery, but that's another issue!)

A user can trigger the dialog asking them to allow background battery use, but we need to prompt the user to do this.

We could do this with a notification in the settings, or with a prompt on first run.

"Would you like to enable background battery usage? This will make your notifications more reliable, and improve reliability for others in your community."

One thing that's tricky about this is that it's a global setting for Quiet, not a setting specific to any one community. We might need to make some section for global settings within the community settings. Or it could be another settings area in the community switcher... but this might be confusing.

@holmesworcester holmesworcester moved this to Design Backlog in Quiet Jan 16, 2025
@jgaylor
Copy link
Collaborator

jgaylor commented Jan 21, 2025

@holmesworcester, I dug it a little on this and it seems that Android has two separate concepts for this: Background activity and Battery Optimization.

On iOS it's all rolled into a single toggle: Background app refresh

So on Android, the first time flow might be something like this:

  1. App Launch
    • The user opens the app for the first time.

  2. Request Background Activity Permission
    • The app explains why background activity is needed (e.g., for reliable notifications or syncing).
    • The user is prompted to grant permission for Background Activity.

  3. Detect Battery Optimization
    • The app checks if Battery Optimization is enabled for it.
    • If enabled, the app explains why disabling it is important (e.g., for consistent notifications).

  4. Request to Disable Battery Optimization
    • The app directs the user to the system settings to disable Battery Optimization for the app.
    • The user makes the change and returns to the app.

Is the requirement for both concepts? Are we only doing this on Android?

@jgaylor jgaylor moved this from Design Backlog to Design Research in Quiet Jan 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Design Research
Development

No branches or pull requests

2 participants