With Firebase Notifications, the developer can send out target notifications to the single and specific device. All you need to do is to gain access to the registration token for the app instance of that device to provide token while composing and sending the notification to the Notification console. Sometimes, these Firebase Notifications can be a little bit confusing and there are several different ways to implement them but all these behave in a different manner.
When it comes to enabling the Firebase Notifications there is a whole lengthy learning process which is both time-consuming and hectic. Well, in this blog you will come across a brief version of the implementation process. Moreover, this blog is especially for the amateur iOS developers, who are looking for the quick guide on Firebase Notifications.
The easiest way to send and receive notifications with Firebase is by using the built-in console notifications. A simple notification will be displayed with the following components:
The Title- which is the name of your app.
The Text- it will be what message text you will put in the console.
In case your app in running in the foreground then the notifications won’t be displayed on the device. You can fix this issue by adding a FirebaseMessagingService that will efficiently handle this situation. But before, let’s move on from the console to a command line tool to send notifications.
Handling Notifications in Foreground
Whenever the app is closed or working in the background, the notifications are handled by the Google Service Process which takes care of display notifications as required, including the default click action and the notification icon. When the app is in the foreground, the received messages are processed by the app itself, and since there is no logic in place to handle it, nothing will happen.
In reality, the onMessageReceive content will be a little bit more complex, and you will need different smart actions depending on the type of notification you want to display to the app users. The problem now you have is that the onMessageReceive is ONLY called when the app is in the foreground and if the app is in the background, the Google Services will take care of displaying your message. Instead of using notification messages, use “data”.
In the iOS-powered devices, you need to use the “notification” object. It will be good if you pre-instruct your mobile developer that you want to roll out different notification formats depending on the operating system. Just keep this thing in your mind that while registering the device to tokens in your system.
Click Actions and other Parameters
While implementing actions by using “click_action” parameter requires you to add an extra layer of filters in the iOS manifest for the each activity it will open.
Notifications sent via Firebase Console serves as the quickest way to send a notification but it lacks some options that developers need. Make sure you implement your FirebaseMessagingService from start. You should learn to send messages through Command Line. Along with that, you should also keep “notification” JSON object for iOS and can avoid using “data”. It will be good if you don’t use same solutions for both platforms.