Demo implementation to Schedule FCM Notifications on Android Device using AlarmManager + WorkManager.
MIT License
This is demo app to implement FCM On Device Push Notification Scheduling using AlarmManager
and WorkManager
.
In this demo app, We are subscribing to a FCM Channel discount-offers
. We'll receive Data payload from FCM to this subscribed channel and we will process and schedule it.
Firebase Messaging
- Firebase Cloud Messaging Library.Firebase IID
- Firebase Instance ID Library.WorkManager
- Used for Background Work Processing.google-services.json
configuration file in /app
directory.src
fcm
MyFirebaseMessagingService.kt
NotificationBroadcastReceiver.kt
ScheduledWorker.kt
util
| NotificationUtil.kt
| SettingUtil.kt
|
ui
| MainActivity.kt
|
MyFirebaseMessagingService
: FCM Receiver Service Implementation. Process of Notification Scheduling using AlarmManager
is implemented here.
NotificationBroadcastReceiver
: BroadcastReceiver
Implementation. Executed when AlarmManager is triggered. WorkManager is initiated and executed for background processing.
ScheduledWorker
: WorkManager
Implementation. Notification is displayed in the system tray and other background processed are executed.
NotificationUtil
: Implementation to display Notification on the system tray.
SettingUtil
: Function implementation to check whether Automatic Date & Time setting is ON/OFF.
MainActivity
: UI Implementation to subscribe to FCM Channel.
discount-offers
FCM Channel from Android Device. {
"to": "/topics/discount-offers",
"priority": "high",
"data" : {
"title" : "TITLE_HERE",
"message" : "MESSAGE_HERE",
"isScheduled" : "true",
"scheduledTime" : "2019-12-13 09:41:00"
}
}
Format of scheduledTime
: YYYY-MM-DD HH:MM:SS
onMessageReceived()
in MyFirebaseMessagingService
will be invoked. In this, following operations will be done-
isScheduled
parameter received is false
then notifications is displayed in system tray instantly.isScheduled
is true
then scheduledTime
is parsed from payload and AlarmManager
is used to set one-time alarm at that time and NotificationBroadcastReceiver
implementation will be executed on that time.onReceive()
, we have scheduled a WorkManager ScheduledWorker
for background work processing. There in doWork()
, we're finally we're displaying Notification on system tray. Do any background proessing and return status from WorkManager.Hurrah! we have successfully implemented On-Device Scheduling of FCM Push Notification.
I have sent below payload with to the FCM Channel (discount-offers
).
{
"to": "/topics/discount-offers",
"priority": "high",
"data" : {
"title" : " Christmas Offer ",
"message" : "Grab 90% Discount on Mobile Phones",
"isScheduled" : "true",
"scheduledTime" : "2019-12-13 14:12:00"
}
}
See output below and notice that Internet/Wi-Fi is OFF still at exactly 02:12 pm I'm getting a notification on the system tray .
Yippie ! It's working as expected. Hope you liked that. If you find it helpful please share this. Maybe it'll help someone needy!
If you found this project useful, then please consider giving it a ⭐ on Github and sharing it with your friends via social media.
Sharing isCaring!
If you want to contact me, feel free to reach me Visit My Profile.
MIT License
Copyright (c) 2019 Shreyas Patil
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.