I've been looking for a way to send push notifications to Android, iOS and Windows phone devices. I've come across the Parse4cn1 library. This library uses Parse. However i saw on the Parse site that they will retire soon. I have the following questions regarding the Parse4cn1 library and the retirement of Parse.
Does the Parse4cn1 library still work after Parse's retirement?
Do i need to setup my own open source Parse server to support the push notifications and when i do this does it also support push notifications for Windows Phone? (http://blog.parse.com/announcements/parse-server-push-notifications/ says it doesn't but i'm not entirely sure.)
Kind regards,
R Visser
See this related SO question.
In any case, parse4cn1 will not support features that are not available in Parse Server. As far as I know, push is currently only supported for Android and iOS by Parse Server. So when parse4cn1 is updated, it will support those. However, I've not scheduled that update yet. Feel free to chip in if you have the time/resources to update the library and issue a pull request. I'll be glad to review and merge it.
By the way, I recently came across OneSignal which claims to offer free push notification on a wide range of platforms. I have my reservations though as they apparently sell your data and unspecified device info to third parties in return for the free push services. I'm yet to do a full evaluation so don't take my word for it. Have a look yourself and decide if it's interesting to you.
I hope this helps.
Related
I want to use pubsub's pull subscription.
So far its been hard to figure out setting auth & fails in subscription or grpc.
Also its not recommended to package client-secret.json in apk.
Havent found any leads to setup on android
Has anyone done this on android
On the Setup client library its mentioned
Note: Cloud Java client libraries do not currently support Android.
Following this link for Pull Subscriber
Any help would be appreciated
Pub/sub to a mobile platform has some potential issues, depending on your use-case. For example, if a phone is off for a long time, pub/sub will queue a lot of messages which may be expensive. You also would need to create a topic for every user if you want to keep data for each user private.
You might find that Firebase Cloud Messaging is a better solution for pushing notifications to an android app.
Although the com.google.cloud.pubsub library doesn't support Android, the com.google.api.services.pubsub library does. com.google.api.services.pubsub is auto-generated, so is harder to use and worse documented, but it should work on Android.
See client libraries explained for the difference between the libraries.
I'm new to the concept of push notifications and sending them from Amazons SNS service so apologies if this is a stupid question.
For our current app we are wanting to target both android and iOS devices. We've successfully created a platform application in SNS that uses firebase to target android devices.
We initial thought that we could use the same platform application for iOS as firebase supports pushing to iOS devices. However, the AWS documentation indicates that you have to create a separate platform application which uses APSN to push to iOS devices.
Is it the correct approach to have multiple SNS platform applications for each device operating system you're trying to target?
Any advice would be appreciated, thanks David.
I thought I’d provide the outcome we came to just in case anyone might find it useful. After looking into firebase it seemed an obvious choice for it to replace SNS. The notification side of firebase is free and much easier to integrate into our app as opposed to SNS where it seems you have to worry about multiple notification providers for each mobile platform. The documentation around firebase is a lot better than what is available for SNS.
Why is it so damn hard to find a reliable solution for sending push notifications on your own? I need a solid solution for sending close-to-real-time notifications to separate Android devices using WCF.
I should not have to rely on 3rd party notification services like Google's FCM. I should be able to have a notification pushed to a user's device without their application running in the foreground and have that application open when the user selects that notification. Even when the phone reboots, the phone should still be able to process your push notifications without needing to start your app first.
Have any of you Pros accomplished this yet? If so, show us the code because there are way too many half-baked solutions out there that are either too old or never actually worked.
I'm using Cordova through Intel's XDK, but I don't care what environment you're using, just show us something that actually works.
Thanks
Do not use Cordova cross platform solutions for this. Either use native IDEs per platform or use cross platform solutions that translate a common code base into native code per platform.
I am planning to build a web application and android app, which will manage huge numbers of notification (push notification), and can work in slow internet connection too. I need to send and get instant notifications. Number of users can be thousands or millions, application will have multiple servers (web farm), multiple database. Now I need to decide that which database will be best for this kind of application and which language should I use for programming. Please help me out. Any suggestions will be appreciated
Well, first you need to decide what your immediate needs are. Are you going to use this on a platforms that could potentially have hundreds of people accessing information at the same time? Then you need to estimate your future needs.
This will help you to decide your database system.
As per my experience i am suggesting you to use MYSQL database.
I Blindly Suggest you to Use Parse Cloud Database,as it provides SDK for All mobile Environments like Android and IOS for easy implementation and also it recently Launched a Javascript SDK to use.Its free for Trial.MultiPlatform Support and Secure
Check it out Here: https://www.parse.com/
Are you sure you going to get to thousands and millions users ? Everyone starts from scratch (read: zero users, except some friends). By this I mean, that you have to concentrate on what's the real issue within your development (growing app user base is different story):
Creation of Android app and it's lifecycle (updates, support of previous versions & etc).
Back-end. Will I also work on Back-end. Working on 2 'projects' (Android app and it's back-end) isn't easy. Not everyone is experienced enough to work on multiple assignments at the same time.
Valuate an option of using SaaS/Paas backend. Most of the have trial or free version for developer.
Third option is great. Get cheap/free web host. Store there configuration, that your Android app will download when it starts. In configuration you should declare what's the back-end and how to communicate with it. You can use any of known services like https://www.firebase.com or https://parse.com/plans or even use Google App engine free tier / AWS free tier.
About developing app for Android - if your app doesn't need any complex calculation or libraries - just write it with JavaScript. It's fast enough. Though, Java apps are always faster and easier to debug.
Good luck !
I am writing a messaging application for Android. Because 30% of Android users are still on 2.1, I have decided we will not use Google's C2DM system for push notifications, which requires 2.2+.
Does anyone have experience building medium to large scale services on android that require push notifications? I'm interested in things such as:
How many users can reliably be supported per server or per IP address?
How difficult is it to increase capacity as you go?
How long will it take to set the server up?
How reliably does it deliver messages?
How quickly does it deliver messages?
I know there are a few popular solutions out there such as MQTT, Deacon, Xtify and Urban Airship, but I cannot seem to find reliable data about the above topics from people who have actually implemented these solutions in capacity.
Urban Airship's blog has a couple of entries that describe how they are scaling their Android push solution for pre-2.2 devices:
C500k in Action at Urban Airship
Linux Kernel Tuning for C500K
Android Messaging: Deploying the Octobot
Think in the future, I highly recomend you take a look at the time it has taken for Android OS' to evolve on phones and study that against the cost of using other non-official solutions, mainly, the question you should ask yourself is, how long will 2.1 phones be on the market vs how much will it cost to run other solutions.
Do you want to break your easy solution for an "exception" to the rule? It really depends on what you want, I see people still developing for 1.6 and such, when IMO there is really such a small market share to attend there that its not worth breaking the easier and more useful 2.1 API.
As for designing your own push server, you are talking about a project that will probably take longer than 2.1's useful life. I mean from scratch.
I cant give you any insight on the solutions you have mentioned though.