I have registered with RIM for the push notification evaluation. But i cant find good sources for implementing push notifications. There are some samples in the sdk but i couldnt find out a way to implement them. So, i am looking for a good tutorial where i could find step by step implementation of push notification services...
RIM's samples for the server side involve setting up a web application container (e.g. Tomcat), setting up a backend database, and then building their Spring-based application. This sample web app handles things like device registration, content subscription, etc. and features a portal to manage everything.
The bare minimum that is required, though, is to send a WAP Push message which is just an HTTP POST to their Push Service servers. Here is a thread from the BlackBerry Support Forums that describes how to use their low-level PAP API to construct this message. Pay attention in particular to the messages by the user mdicesare.
There's also another SO question that has some tips.
Related
Currently building a mobile application that ideally would have functionality that allows one user to "nudge" another user, pretty much the equivalent to a Facebook "poke." For the sake of building quickly, we'd like to use as many third-party libraries/services as possible. So far we were looking into using pusher and expo, but to be totally honest, we are a bit confused as to how to architecture this.
From what I understand, the front-end (ios app) would subscribe (open a socket) to a specific channel/server and the server would then send messages to the client(s) that subscribed whenever necessary. How this works with users being subscribed to every other user they are friends with, I don't understand. What's the proper way to architecture this?
I also read that on the front end, when a user doesn't have the ios application open you can't have any websockets open to the server, so how does that work?
Additionally, how does one bundle notifications??
Really confused with this, any help would be greatly appreciated.
Chris
Well, push notifications now mostly are implemented with Firebase. This is a service inside most of mobiles, so you only need use these libraries to implement your client application.
From the server, you only need to consume a rest api of Firebase.
Now there are permissions to allow mobile applications receive push notifications in background. You do not need to implement a socket or websocket, that is a feature of Firebase.
Read more about this.
https://medium.com/google-cloud/push-notification-for-react-native-bef05ea4d1d0
https://dzone.com/articles/how-to-add-push-notifications-on-firebase-cloud-me
How do I send push notifications to my iOS app? I need to send small messages even when the application is in the background or not running.Is there a simple tutorial. I searched a lot and only found third party solutions. Is there a direct way to access APNs, and if not which third party should I go for.
To send remote notifications, you need your own server that is authorized (you can grab a remote notification certificate from your developer account from developer.apple.com). Then you just follow Apple's API to send a notification to a specific device.
I followed a Ray Wenderlich guide a while back and found it useful.
However, you might not want to set up your own server and stuff. This is where third-party solutions come in. I've worked with Parse's push notification system and found that it is pretty easy to set up.
I am implementing the push notification in iOS for sending offers and deals. Right now I am working in the development environment. I see that some of the devices are not being notified. Could anybody explain possible causes? I have also read that if a push is sent to same device multiple times then APPLE disables them for that particular device? Could some one verify this or provide any documentation where I can find the issue. Any feedback would be appreciated.
Not directly answering your question, but what you asked about in the comments and an alternative. You could use a push-notification service such as Parse.
They allow you to send Push Notifications to Web, iOS and Android, also offer data storage and backend infrastructure. The best thing about Parse is that they're free. Unless you have one million unique recipients, which is rather hard to accomplish. Parsee allows you tons end Push Notifications in multiple ways, some including automatic messages based on their tables or other events. You can program those in their cloud code. You can do so using their REST API or their Java Script API if you have a website. You could also send from the Push window on their website.
Setting up is fairly easy. I'll give you the most important links below.
iOS Quick Start Guide
Rest API
PHP Guide
Hope that helps, Julian
If you are dependent on APNS then there is no guarantee provided regarding the delivery of the push notification. And regarding sending multiple notifications. Like if you send notification every min then many may not deliver. Else it will. This service is free and many including myself using it on a regular basis. It has been delivered regularly even though apple will not provide any guarantee. i'm using a php script on server side to send push notification. Refer the below link if you want to know how to send a push notification using php.
tutorial
I developed a Blackberry Native application and now the client want notifications even when the device is turned-off. After a few searching, Blackberry Push Service seems the way to go, but i have some concerns:
Blackberry Push Service is a free or paid service?
What are the library requirements on the client side? Do I need additional libraries or it only work with Blackberry SDK?
How are the notifications sent? Do I need to build an additional application for that? The client has IIS servers, so I wanna know if it is possible to build such an application in .NET.
Have any one tried Urban Airship? Seems like a simpler way to accomplish the task.
RIM charges for Push services based on how much data you are pushing through their servers, and for delivery confirmation. If your customer base is small, and the push data requirements are modest they won't charge anything.
When you register to start a push service they will send you sample code but there are no additional library requirements.
Push notifications are XML documents that are POSTed to a RIM 'web' server. There are a number of services you must provide to the client for registration and push control. The standard way of doing this is again with a 'web' server that RIM and the client device communicate with. When you register RIM will send you a sample server module designed to run in Apache TomCat, but I (and others) have replicated the necessary capability on Linux, Apache, MySQL, and PHP servers (LAMPS). I don't see any reason you could not implement this on IIS but I have no experience with IIS. (I put 'web' in quotes because this server may, but does not have to, serve any web pages in the traditional sense. The push service uses HTTPS as the transport protocol.)
I don't even know what that is.
If your client is running a BES then they already have everything they need to push to the client and get delivery confirmation without any additional cost. JP Mens published a very good article on using the BES MDS server to push data to clients from a LAMPS machine.
Amazon Web Services have an SDK for iOS which supports the Amazon Simple Notification Service (SNS).
Does this mean it would be possible to use SNS to send push notifications to a running iOS app? So for example you could make an real-time instant messaging app.
Is this right, or have I misunderstood what SNS does? It just seems to me that you would need to open a connection/socket in order to recieve push notifications from your server. How does the SDK actually work?
Update:
I've since asked this question on the AWS Mobile Development Forum: https://forums.aws.amazon.com/thread.jspa?threadID=81089&tstart=0
Apparently there is an article coming out (probably here: http://aws.amazon.com/articles/SDKs/iOS) shortly to explain everything.
Update 2
The article: http://aws.amazon.com/articles/9156883257507082
According to Apple documentation "Local notifications and push notifications are ways for an application that isn’t running in the foreground to let its users know it has information for them.".
So, technically speaking, any data, including notifications, received when the application is running in the foreground are not "Push Notifications" and can't be a reason for rejecting the application. They're simply data being consumed that way or the other by the application.
In this specific case you are not asking about Push Notifications per Apple's documentation, rather about a technology used to deliver data to the application when the application is running and user is interacting with it. It happens that the name Amazon SNS is similar to Push Notification.
In any case Apple wouldn't be able to see what is the technology behind delivering data to your application, whether it is Amazon SNS or anything else. All they can see is that the application may have some additional ports open when it's running, and that of course would be absolutely legal. In fact, many applications communicate with their back-end servers using sockets (not HTTP requests), and that is the same technology as used by Apple to deliver their Push Notifications.
According to the Amazon documentation, they in turn uses the APNS method and provide a much simpler frontend for Apple, Android and Kindle. A realtime instant messaging app could be considered as workable since by using the Amazon SNS platform, you could even consider the application to be available for all.
I mean by utilizing the Amazon SNS, the communication could be done between iOS and Android devices and to kindle also provided the applications are written accordingly. Though the Amazon documents do not provide a comprehensive example, there are bits and pieces. Also there is an upcoming event on the Aug 29 which could be seen from the Amazon SNS page.