Open James-E-A opened 8 years ago
weechat is more likely to be unloaded from memory. This notification can be removed when we'll implement proper work with FCM notifications.
Users also get a handy and reliable indicator to show connection status. Isn't it cool?
Weechat and surespot both also use their perma-notifications to prevent themselves from being unloaded from memory—however, theirs are much less obtrusive.
They are “background”, whereas Xabber gives off more of a “foreground” impression, it shows up on the lock screen, etc.
Why is Xabber's so much more obtrusive than those other chat programs'? Could it be made like theirs?
We experimented with notifications as you suggest and found that app is much more likely to get unloaded. True solution would be possible by augmenting background work with correctly implementing FCM. And we really like notification with connection status right in tray!
(actually we prefer pre-Android 5.0 notifications, liked old tray notifications much better than these intrusive things that always block my app bar - especially bad whey you are typing url in browser)
Some applications, such as Weechat-Android and surespot, create a persistent notification that keeps the application from being unloaded from RAM. The notifiations sit discreetly below all other notifications and do not show up on the lock screen (of an LG Vista VS880, anyway).
Xabber has the same system: "use a persistent notification to keep the program in RAM", but it seems to be using a different system for this, one which is arguably less suitable for an always-running background messaging service:
Xabber seems to be using a notification API more suited to "active" tasks, rather than the out-of-the-way "passive" system used by weechat-android and surespot. Could this be changed, or at least added as a setting?