search

element-hq / element-android

A Matrix collaboration client for Android.
https://element.io/
GNU Affero General Public License v3.0
3.38k stars 726 forks source link

Update the wording of the persistent notification #5065

Open Claire1817 opened 2 years ago

Claire1817 commented 2 years ago

Your use case

The actual wording of the persistent notification is: "Listening for events" . Some tchap users have told us that the word "listening" does not give enough context and can be scary. Maybe we could use another word like: synchronize or recover ? Some propositions: "Element/Tchap synchronizes your messages", "Element/Tchap recovers your messages" ?

Have you considered any alternatives?

No response

Additional context

No response

bmarty commented 2 years ago

@daniellekirkwood any thoughts on that point?

daniellekirkwood commented 2 years ago

I'm sure we recently updated this but I'm struggling to find the wording we used or GH issue. @ouchadam do you recall this discussion that we had?

ouchadam commented 2 years ago

yep it's here https://github.com/vector-im/element-android/issues/4298#issuecomment-952995120 originally this copy said Listening for events but we've changed it to Listening for notifications https://github.com/vector-im/element-android/pull/4314

This persistent notification is a requirement of the android OS in order to keep the non google play version of the app running in the background and able to receive messages/notifications/events

originally the notification would briefly show each time a sync occurred (every 60 seconds or so) but the time in between syncs allowed OEM battery optimisations to kick in and shutdown the app until the next manual launch

bmarty commented 2 years ago

Thanks. notification_listening_for_events is still used for the notification channel name, which is less visible to the user but still visible from the setting (and from the notification when long clicking on it):

image

Anyway the wording for the notification itself has been changed in Element Android v1.3.7 (2021-11-04) @ClaireGizard

daniellekirkwood commented 2 years ago

If we have updated the content here, can we close this issue?

If no, what are we waiting for in order to move forwards?

ouchadam commented 2 years ago

I believe the intention of this issue was to see if we can avoid using listening, whereas the recent updates we've made were to swap events to notifications

lrq3000 commented 2 years ago

I would suggest Background notifications or Background events updates? The option is specifically to setup how background events are updated, not when Element is on the foreground, so IMHO it would be much clearer to state it like this.