Add "alive app" in notification bar

[JGG-Apps]

Please agree to the following

• I have searched existing issues for duplicates
• I agree to follow this project's Code of Conduct

Summary

Let easier to keep password database open in the current session

Motivation

First, I'm not sure if this feature could work with iOS, but I known it's possible for Android. I understand you try to have unique development for both mobile platform.

My request:

Like some other apps that we want to keep alive in background (othe password manager), VPN client, etc.

1. When we reduce the app in background, nothing give an easy access to switch on the password database, nothing inform we had keep our database open. Adding a persistent icon in the notification bar can really be useful.

2. In the same way, a password manager should be able to stay open in background to help us with our needed passwords in other apps. This app should not be "easly closed" like regular app like "Close All" or slide the screen to close the app. The notification icon could be the way to keep app persistant and give the "fully close" option.

This could be a "optional setting" for those who prefer this method and let people choose.

Considered Alternatives

No response

Anything else?

No response

[jeyasankar]

Hi @JGG-Apps ,

Thanks for the suggestion.

Based quick research:

• Android: feasible. It would be implemented as a foreground service with an ongoing notification (the same approach VPN clients use), behind an opt-in setting.
• iOS: not feasible in the way described. iOS has no persistent "ongoing notification" and tightly restricts background execution, so an app can't keep itself resident or its database session alive in the background. This would realistically be an Android-only feature.

The important trade-off:

OneKeePass today is intentionally built to do the opposite of staying alive: when the app is back grounded or idle, it auto-locks the database (and optionally the app) so that decrypted secrets don't sit in memory while you're away. A "keep the database open in the background and resist Close All" feature directly relaxes that protection.

That's not a blocker, but it does mean the feature has to be:

1. Strictly opt-in (off by default), and
2. Clear about the consequence — while it's on, an unlocked database stays decrypted in memory in the background until you explicitly lock/close it.

For users who want maximum security, the current auto-lock behavior stays exactly as it is.

So this will be then an Android-only enhancement if I could implement it in a future release