I'm using phonegap/cordova for both my iOS and Android applications. I'm looking for geolocation push notifications, so I can do a push message for both my east coast and west coast customers. Is there a third party platform that would allow me to integrate this ability and let me do one-time push notifications?
We recently did the same thing.
Initially:
We tried to capture all the user push ids and store them, then set our own system up. Which was a pain in the...
Then:
A better option is to set up native push notifications with http://parse.com/
They have a few API options. So its easy to set up the users.
When you add the user
also add a [channel]
Call the channel ["east_coast"] or ["west_coast"]
Then push a notification out to the channels that include ["east_coast"]
Easy.
Related
We are developing an app for Android and IOS for students. student can receive notification for upcoming events like exams or interviews.
We are between two decisions: Using FCM with the development of a backed which manages the sending of notifications and the registration of tokens or using the schedulers that exist in IOS and Android then download a list of events from an API regularly and trigger a local notification which will require less development on the backend side but a little more on the frontend side.
What would be best in your opinion and can we trigger a notification even if the app is closed for the 2nd solution?
I would deffinitely recommend to use FCM. It is much easier than it looks like and the performance of your notifications would be much better regarding stability, timing, battery persistance and other. You can use on of the Firebase databases to store the notification tokens and the Firebase Cloud Functions to send them from there. I have made a very similar App for Kindergarden children and it works great. I'm not sure if it would even work at all when you do it on your own. At least not as you expect it. For me that sounds like much more work.
I'm building an app with React Native and handling local notifications with https://github.com/zo0r/react-native-push-notification
The problem is, When I research about scheduling local notifications, I believe there is a limit for that. My applications purpose is about sending notifications so I need to send 10-15 of them in a day. What is the best practice for that with React Native ?
Should I somehow schedule some events for scheduling local notifications or should I use some remote push notifications ?
There's no limit on scheduling local notifications. I'm not sure there is limit or not but you can send 10-15 of notifications in a day using this library because I'm using it in that way.
Important thing is that you should set each notification's id (in case of ios userInfo) and it should be different each other.
We need to allow a user to set specific preferences for receiving push notifications. Examples:
mute specific channel
send push only when #mentioned (global and
chat specificly)
docs https://getstream.io/chat/docs/#push_ios doesn't cover it at all. Seems only turn on/off all notifications is possible?
At the moment this is not supported by Stream Chat, improvements to the Push capabilities are added regularly so extended support for mutes and mentions will also come up soon enough.
In the meantime you can achieve this by handling chat events via webhooks and add the mute/mention logic on your webhook handler. More information about this can be found in the docs: https://getstream.io/chat/docs/#webhook_events
Is there a way to send push notification with passbook on android ?
I found this https://www.pass2u.net, but i'm not quite convinced...
pass2u have an open API and offer free access to pass issuers with less than 1000 updates per month. One advantage over PassWallet is that their revenue model is not dependent upon advertising.
Both pass2u and PassWallet have reliable APIs that closely mirror the Passbook webservice and can be easily implemented with minimal overhead.
One further advantage of Pass2u over PassWallet is their support for Baidu push. If you have users in China then PassWallet updates will not work because they are dependent on the Google cloud messaging APIs which are not available.
The PassWallet app supports push notifications. It uses the same mechanism and API as Passbook/Wallet on iOS, the only difference being where you send the push notifications.
When a pass is installed, it registered with your service as normal, but in addition to the serial number etc. a URL is provided too. You then send a message to that URL.
You'll find more info here http://attidomobile.com/portfolio/passwallet/
I'm currently in the early stages of designing a cross-platform mobile app (iOS, Android, WP8). At its core, the application will allow proximity based interaction between an unknown number of client devices.
Could someone recommend a framework or technology that would allow me to push server generated location based proximity alerts to the clients that even scales well? Could push notifications (cross platform using PushSharp) be a viable option for this, or will Push notifications always go hand in hand with some kind of toast notification on the device?
Update: 30 seconds or even a minute delay should do.
Push Notifications have way to much latency to give you anything near real-time. Also Push Notifications are not guaranteed to reach a device.
You really need to think about how much time constrained the location updates should be. You should also make some tests with how fast the GPS on various devices updates. I have tested on a Nexus 4 and it is not near real-time either. So throughout your entire application whether it is server side or client side you will have things blowing your real-time wishes.
However IF you can live with a delay of a couple of seconds to maybe 30 seconds or more, Push Notifications my work well for you, they also scales quite nicely.
EDIT:
Push notifications always go hand in hand with some kind of toast
notification on the device?
There is a concept called RAW notifications, which allow you to send arbitrary information with the Notifications. However personally I would just notify the client about updates ready on a server, where it then can get all the information the application needs. This is because as I said Push Notifications are not guaranteed to ever reach the device, but also because you are limited to how much information you can embed in the Notifications.
So my suggestion for a flow would be:
Client A updates its location and sends it to a web service
Web Service receives info from Client A and prepares notifications for all the other Clients, which need information about Client A and pushes information about they need to update their info.
Client B receives a Push Notification telling it to refresh data from the Web Service and does that.
That would work well if the application is in a background state. When showing in the foreground I would simply poll a server every second or so; Still receiving Notifications just forcing the client to update.
For the "scales well" part, you might also want to take a look at Windows Azure Service Bus Notification Hubs. It's currently in preview and supports only Windows 8 Store apps and iOS but support for Android and Windows Phone is on the way.