I have a rails application and I would like to send notifications to users on their mobile. I only need simple text notifications, but I can't afford to write an application for any operating system.
Is there any simple way to do that? (gem, third-party services)
Boxcar might be what you are looking for? http://boxcar.io/help/api/providers
Web Notifications might be a solution in the future.
I created a gem in order to create a central push notifications, it supports iOS and Android at the moment, but i will add more platforms.
Maybe this will help you, its a single gem that makes iOS an Android at the moment, and its fairly easy to implement
here is the link: https://github.com/NicosKaralis/pushmeup
Related
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 looking to build a mobile messaging app firstly in android and then ios later, and am struggling with the backend architecture and need some advice on what would be best in my circumstance. Basically i am used to just developing apps through a basic web server and using mysql with php, but now i think and want to create something that not only is very reliable and fast but is also scalable and can be used by both the android and ios platforms.
I am thinking about developing it on google cloud platform using either their google app engine or google compute engine depending on what other architectures i use. Also i was going to use google cloud messaging as my main way of handling the messages, however i am now not sure of that as it is only supported by apps that run on android and not ios, also i have heard it can be unreliable in some messages getting lost.
My main problem is that i have heard so many things about different architectures like ejabberd, xmpp, socket i.o and databases like redis that all work well with messaging apps, however i am not sure which to go that will work well together.
Sorry if this seems a bit of a confused situation, but i dont want to start developing something that i am later going to have to change. Thanks for the help
Announced last week: Engage your users across Android, iOS and Chrome via Google Cloud Messaging 3.0:
https://developers.google.com/cloud-messaging/
https://www.youtube.com/watch?v=gJatfdattno
You are asking about many different things.
Storage: can be a mysql database or something like mongo db
Transport protocol: XMPP is a chat protocol with many chat features included but it is not supported in browsers. WebSocket is more low level and more general but works inside the browser
webserver software: you basically need access to the database and be able to transmit XMPP or WebSocket. I'd recommend node.js for this. PHP is more for web pages
I've got a server written in Scala/Java. I want to make an app in PhoneGap/Cordova which uses push notifications.
I would prefer to have one codebase for both Android and iOS. Is there a way to do universal push notifications for both Android and iOS.
Is using Parse Push REST API for that purpose a good decision, cosidering that I've already got my own server?
If it sounds opinion based, excuse me. I'm new in this topic, and just want to decrease the redundancy as much as possible.
Not sure about Parse, but clientside if you are using Cordova then the PhoneGap Push Plugin should be what you are looking for, it's available for iOS, Android, Windows and others and let's you handle the Push Notifications in Javascript.
I don't know how you could solve this platform independent on the server side, though.
I have a client who has a requirement for a chatting app. This app should make communication possible on Android and Blackberry.
Wonder if this is technically feasible? If yes then how? Any clue?
Check out WhatsApp—you can send text, pics and more.
Yes, all you need is a chat server and clients on both mobile devices that utilize the server.
All these frameworks support web services, so its quite easy to create a web-service to handle this on the server for you.
You can probably skip the server and let them talk directly to each other.
If you are looking for a technique to build three apps that can chat with each other regardless of phone OS this surely can be done.
You need to look for a chatting standard that is covered with libraries for all the three systems. I would look into Jabber/XMPP. It is the most commonly used open standard for submitting messages and at least for Android there is the Smack library that will run on Android and give you all the necessary functionality. I don't know
which libraries can be used on iPhone or BB but there should be something available at least on the iPhone.