I searched through a lot of documentation and other answers but I cannot figure out what is the correct way to have a background service that performs some work and sends notifications. I found a lot of deprecated methods.
I don't want a foreground service that comes with a permanent notification on user's device.
I want a sort of live notification when something happens in my application like Whatsapp does when there are new messages.
I tried to set a standard service with the start_sticky clause, but what I got is that my service starts completely randomly. More or less Android decides to start my service once every 20 minutes.
This is not what I want. I want a service that is always vigilant like Whatsapp that sends a notification when it realizes that a message is present.
Can anyone provide to me a clear explanation and example, please?
I want to show notification only app is close or background or in different chatroom. but I don't know which is better Solution.
stop send push notification when another device foreground
just send push notification anyway and don't show the notification in another device when app foreground.
In first solution I need to get another device information from server like in which chatroom or in which activity or in foreground it make my app and database more complex but maybe it reduce the network usage.
In second solution just send notification anyway and receiver device just ignore it but maybe big network usage.
Most apps that I know off use the second approach: they always send the FCM message, and only show it when needed. That also means that they usually only send a so-called tickle message, which contains very little data and whose main purpose it is to wake the app up.
How do apps like Whatsapp or Messenger send alerts/push notifications to users to let them know they have received a message even when the app is closed or destroyed?
I've done some research before I wrote this question.
This SO question recommends a Service and a BroadcastReceiver. But the BroadcastReceiver relates to when the device is booted and I cant imagine a Service being constantly and permanently running to check whether someone has sent messages (that's absurd!). In any case, the example that the ansewr gives does not show how or when the Service will stop running.
This SO question appears to suggest an AlarmManager but that solution is non-asynchronous (eg, the notification time has to be pre-set).
I've read Android's Notification and Services documentation. None of which appear to address this point.
Most of the questions that I find on Google appear to be questions relating to how can the app receive push notifications from a server (ie GCM) rather than the app sending push notifications / alerts to the user. I've currently dismissed those questions as irrelevant as I am trying to send notifications to users rather than receive them from servers.
I let you look around Firebase Push Notifications enter link description here
There are 2 types of notifs:
with the click_action when the app is closed or destroy
with data object when the app is open
How can I send my user notifications during the day if my app is closed? It should also work if he hasn't opened the app after a reboot of his phone. How can I implement something like that in my app and what things should I learn for that?
Thanks!
Push Notifications come through GCM (google cloud messaging) on Android. In order to see a tutorial on this you can go to https://www.simplifiedcoding.net/android-push-notification-using-gcm-tutorial/
As per "it should also work if he hasn't opened the app after a reboot of his phone" part, once you register your app with the client, you can employ logic of what happens (or doesn't happen) when you logout of the app. For example, you can unregister from the service so you don't get any notifications.
In your case, if you'd like to keep receiving notifications then you can do so by making sure you keep your token alive, preferably in System Preferences, and handle the case of what happens if the token needs to be updated. (see onTokenRefresh() callback)
First do the happy path and see you can register and receive, and then go and do any additional logic for your notifications.
You can use the AlarmManager for this. It will wake your Application with an scheduled Intent where you can perform your code, e.g. show the notification.
seems to be a duplicate to How to schedule a task using Alarm Manager
I'm building a newspaper-like app and I would like to know how many people received the article's push notification vs how many actually read it.
I was thinking to implement a way in which when the notification is received the app wakes up and send a request to the server saying "Hi I'm _____, I've received the notification of the article ____" and store it in the database. Then afterwards if the user click on the notification and goes to read the article I send another request saying "Hi I'm ____ and I've read the article _____" and I also store it on the database. Afterwards with some queries I'm able to understand the percentage read/received.
I don't understand if it's even possible to wake up the app even if it was not opened by the user in a while and send a request to the server (for background is meant that the application is not launched or that is in the cache ?).
I would like to achieve what they did with Whatsapp:
I receive a new message on Whatsapp
I don't open the app
I go to WhatsApp Web
I open the conversation on WhatsApp Web
The badge and the notification on the phone goes away because I read it somewhere else
I think that that feature is achieved with silent push notifications that just update the app badge and clear the read notification.
Thats a very nice question on how to implement such silent notifications. There are few variables here that we need to consider and deal them in a different way.
Push notifications sent to the users - Some of them would have received it, Some may not have received it at all.
Pushing multiple notifications to the same user in a small amount of time - It becomes difficult here to track the exact notification user opened the app. Because user might have read all the news that received notifications in a single attempt.
The actual content displayed to the user in the app - User might have opened the app because of notifications. Some times he might have seen the notifications and then opened the app directly without interacting with the notifications.
So this is how the implementation can be.
Implement push notifications for the app
User receives the push notifications and the notification badge shows Number (1).
Now when the user views the same news story in any other medium (Your own Mac App or PC app). Server is notified of the users action and the news he/she/whoever just read.
Now the server knows it has sent a notification and it is not read. When you receive the read notification, you can send a remote notification that can be handled by the app in background and update the badge.
Check out this link for more details on how to handle notifications in various modes.
Apple documentation also can be referred here for background mode - remote-notification.
So you will be making your app run in background with certain settings to respond to silent notifications and update the badge just like WhatsApp. I hope this helps.
I've already implemented such thing in one of my app, and it's actually tricky.
You'll have a lot of use cases to handle.
First thing (but you seem to already know it): Apple does not provide
any callback to say : "this notification was sent"
Second thing : when your app is killed (not even in background), nothing at all can be done with your notification, meaning your app won't be able to wake up and read the notification, and therefor do something. The only thing you can do is changing the badge number, even if your app is killed.
Third thing : when your app is in background, you can wake up your app during 30sec. During that time you can send a request to the server, but if it takes too long, the process will be killed by the OS.
Saying that, here is a quick explanation of how you could implement the system:
You'll need on the server side to save in your data base any notifications that were sent. As soon as they are sent, save them as "pending"
On the app side: if your app is in background, as soon as the notification is received, you can wake up your app to send a request to the server. Then in your data base, your notification status will change to "receive" or "notified". If your app was killed, when the user launch your app, send a request to the server to ask for all notification in "pending" state, that way your app will be up to date, as well as your badge number.
If the user click on the notification, this will open your app directly on the article, that way you'll be able to send a request and say to your server that the article was received and read.
If the user read your article on the web side, send a notification. Set the notification badge number with the number of actual "pending" notification in your data base.
Hope this will help you in addition of the answer of #Prav :)
try this Notification Listner service https://github.com/kpbird/NotificationListenerService-Example.
Reply from Apple Developer Technical Support:
Hello Matteo,
Thank you for contacting Apple Developer Technical Support (DTS). Our engineers have reviewed your request and have concluded that there is no supported way to achieve the desired functionality given the currently shipping system configurations.
So at the end of the games IT'S NOT POSSIBLE
You want to sync your app with web app or website than once you send notification to application than set notification to particular ID.If user read that message from your web then send push notification again with different message and handle in service or broadcast receiver after that cancel notification if received message contains different message.you can also use Notification Listener.Refer thislink
Refer this link for ios.
Hi #Smile Applications after reading your question I would suggest you see OneSignal website. OneSignal will allow you to send notifications to your subscribed users. It will also show you how many users are using your app and how many of them have received your notifications. If you want to send notifications and track them from the app itself you can use their API. It is easy and I have implemented this in Android and soon will be implementing in IOS.
Now the second part of your question about knowing how to track how many users have read/opened your notification and on which activity they are on you can use Google Analytics. It will allow you to see from which part of the world your users are using your app and which activities of your app are being opened most. It is also easy and I have implemented this also in Android and soon will be implementing in IOS too.