Android push notification using MQTT instead of using FCM - android

I have an Android application developing in Java and using Firebase Database. This application will send the notification to the users when uploaded something to the database. Therefore, I want to ask whether can the application send push notification using MQTT instead of using Firebase Cloud Messaging(FCM)?

Therefore, I want to ask whether can the application send push notification using MQTT instead of using Firebase Cloud Messaging(FCM)?
You can use whatever you want. There's no requirement to stick Google service for this.

Related

It is Possible to send Push notification at specific time Using FCM IN FLUTTER

I am using the Firebase Cloud MessagingPush notification service to send notifications in flutter but I want to send notifications at a specific time like a reminder for a meeting through push notification I just want to know how can I achieve using Firebase Cloud Messaging or any other push notification service provider.
I already used flutter local_push_notification but the problem is notification is not showing at terminated state but it is working on the background and foreground state.
is there any method is available that I can use on my server where all my API is presently saved, which I using to call in a flutter.
You can use firebase cloud functions. You should send notifications at the moment you want with cloud functions and problem should be solved.
Here is the docs.

How can i notify the Android user if any change /update in any Website for Android device?

i want to send a notification when a website update something. (For Android Device)
Is there any way to send notification to my Application user?
You can use Firebase Cloud Messaging to send a notification when ever you want. This tool is very easy to init and to use.
Here is the Doc.

Firebase notification on child added/modified

Is it possible to generate a push notification (if the app is not in the foreground) on firebase db changes? I started coding an android app.
Firebase provides a tool called Cloud Functions.
With this, you can listen to your Firebase Database and send Notifications without the need for an external server :)
See : https://firebase.google.com/docs/functions/use-cases
To do it in a simple way, you can use a Service, in this Service you can set a Listener on a ref in your firebase DB when the event is triggered you can create a notify and show it to the user.
This is a very simple tutorial:
https://www.simplifiedcoding.net/android-push-notification-tutorial-using-firebase/
There certainly is. Just have your Android app write the notification request into the database.
Sending device-to-device notifications is not a supported scenario in Firebase Cloud Messaging (see this answer), so you'll need a server component for that. For an example of how to send a push notification in nodejs, see this answer.

Push Notification using Firebase and Google Cloud Messaging

I want to send push notification in my app (Android) using Google Cloud Messaging. I am using firebase for backend. As firebase do not support inbuilt push notification i am using Google App Engine.
I do not have any idea on Google App Engine. Right now i am using a template provided by google for sending push notification.
Google Cloud Messaging Template Github
Till now i have deployed my app in Google App Engine and i am able to send push notification to all devices that are registered (From Web) An HTML page i get when i use GCM template.
What i want to do is , to Listen for Firebase data change and send push notification to user who is not online or has closed the app.
How can i run a servlet in background so that it keeps running in background and send push to user who is not online/connected.
As i have only push notification logic in Google App Engine Should i use servlet or struts.
Thanks in Advance
It is my understanding that Firebase really doesn't work very well with GAE, so you might want to reconsider your choices.
Listening for data changes, as you have mentioned, requires that your app leave a background thread running. To do this on GAE you have to disable automatic scaling which is an important feature of GAE.
You could create a separate backend GAE module with manual scaling and then have it use eg. a queue to notify your main GAE module of a data change, but this seems to me to be unnecessarily complicated and inefficient.
Hopefully Firebase will improve their product so it can notify of data changes in a more efficient and flexible manner, but in the mean-time, perhaps you should use a regular compute engine instance.

Worklight Push Notification for multiple user

I have created an Push Notification application in IBM's Worklight in which it is sending notification for only one user's device(Android Device).How I can send Push notification to multiple user's devices?If any one created application then provide me some sample.
Worklight server must know user's identity in order to be able to send push notifications. In case you did not define any user authentication in your application, Worklight server will use an "anonymous" user identity - a persistent cookie created on first application launch. This is considered an unauthenticated access.
In case this is the model you want to use you need to declare an EventSource in your adapter which does not require authentication (do not specify securityTest for it) and then use WL.Server.notifyAll(eventSource, options) API.
This will send notification to users that are subscribed to a specified event source.
Source: http://www.ibm.com/developerworks/forums/thread.jspa?threadID=462167&tstart=360
Push notification works on Android and iOS only.
You can see how to implement on iOS in the push notifications module.
You can find the module at https://www.ibm.com/developerworks/mobile/worklight/getting-started/index.html#advanced
What I did to accomplish this is to save in a backend database all the users subscribed to a specific event source then send notifications to each of them.
I checked the Worklight info center and WL.Server.notifyAll(eventSource, options) api is not listed!!

Categories

Resources