You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Enhance the capabilities of the Appwrite Messaging API by incorporating support for Android push notification channels in conjunction with Firebase Cloud Messaging (FCM).
🎤 Pitch
Currently, it's not possible to specify a notification channel ID when using Appwrite's Messaging feature and FCM. This means that all notifications currently end up in the same channel, which is not ideal. Notification channels allow Android users to specifically control which notifications they'd like to receive.
Referring to the documentation located at https://firebase.google.com/docs/cloud-messaging/http-server-ref, it is possible to specify the channel ID by passing the android_channel_id or channel_id parameter to the notification section, as demonstrated below:
{
"to": "$device_token",
"notification": {
"title": "New Message",
"body": "You have a new message!",
"android_channel_id": "$channel_id", // For Android 8 and above
"channel_id": "$channel_id", // For Android versions prior to 8
},
"data": {
"message_id": "123456789",
"sender_id": "user123",
"message_text": "Hello, how are you?"
},
"priority": "normal"
}
Enhancing the createPush() method by adding parameters for android_channel_id and channel_id would enable the passing of a channel ID.
In my view, integrating support for push notification channels would greatly enhance the functionality of the Appwrite Messaging API.
👀 Have you spent some time to check if this issue has been raised before?
🔖 Enhancement description
Enhance the capabilities of the Appwrite Messaging API by incorporating support for Android push notification channels in conjunction with Firebase Cloud Messaging (FCM).
🎤 Pitch
Currently, it's not possible to specify a notification channel ID when using Appwrite's Messaging feature and FCM. This means that all notifications currently end up in the same channel, which is not ideal. Notification channels allow Android users to specifically control which notifications they'd like to receive.
Referring to the documentation located at https://firebase.google.com/docs/cloud-messaging/http-server-ref, it is possible to specify the channel ID by passing the
android_channel_id
orchannel_id
parameter to thenotification
section, as demonstrated below:Enhancing the
createPush()
method by adding parameters forandroid_channel_id
andchannel_id
would enable the passing of a channel ID.In my view, integrating support for push notification channels would greatly enhance the functionality of the Appwrite Messaging API.
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: