It is possible to implement push notifications desktop (chrome or firefox) for each specific user application using https://github.com/developerdynamo/laravel-push-notification?
Sure. As long as you have a way sync with the client in the background, like a websocket connecion, you can easily use the Web Notification API.
Related
I am currently working on an web application, which need to implement a notification system, just like Facebook and Youtube does. (Not mobile PUSH Notification. Just to show how many notifications are in the notification couter and, when soneone expand it, show all notifications. Just as Facebook) What I need to know is, what is the following best method to use.
1.Websocket
2.SSE
3 XMPP
Our application is on budget and, we are running it on a VPS server.
Long story short; is Facebook web application or any other social network web app handling in two different ways the in-app notifications(through web socket) and the push notification(through service worker)?
Is this statement correct?
I'm developing a web platform (social network alike) and I'm looking for a smart way to handle notifications (push notification and in app notification), NOT displaying, which is quite straight forward.
To be more clear I mean "in-app notification" those appearing in the upper right corner of the web app (usually) and displayed with fancy js or whatever, and I mean "push notification" those showed by the browser through the Notification API based on Push API and service worker.
I have a website running Laravel in the back-end, where users can create reports for other users.
When the report is created I would like to send a push notification to recipient user's desktop.
Do I need to use services like Pusher, OneSignal?
Any useful site with examples would be appreciated.
Your question
You could use Pusher, Redis/Socket.io, Pubnub, etc. Which one to use? well, this is more an opinion-based question.
These services broadcast events, then in your client apps (like your web front-end) you configure the client-side libraries of the service you choose to subscribe (to channels) and listen to those events. The documentation explains it better.
Examples/tutorials
Pusher
This is a tutorial published by the Pusher team.
Redis/Socket.io
This one
is a Laracasts series about this.
Just google.
Update
There is a Laravel-specific alternative, a package created exclusively for Laravel:
Laravel WebSockets
This is the post talking about the package and its inner working.
This is the repo.
Here you have the documentation.
If you like to show Native Desktop notification then i would suggest Web Push notification. In this way once user subscribed to push notification ,they will get real time notification and does not need to be on your website.
https://github.com/laravel-notification-channels/webpush
I am planning to use ionic to to create a hybrid chat app. Which one should i use to implement push notification and realtime chat. Either parse or pubnub or both. can i just use pubnub to achieve both functionality?
Ionic has it´s own push notification service in alpha state. You should give it a try. Seems pretty awesome and easy to implement.
Personally I have built a chat app with firebase and it works out of the box. There is also a full tutorial how to implement it.
Parse is a great choice for push, but you can send push notifications using PubNub JavaScript APIs too.
I actually write a few tutorials on hybrid mobile chat apps (using Cordova), also tuts for push notifications with GCM and APNs:
http://www.pubnub.com/blog/converting-your-javascript-app-to-an-ios-app-w-phonegap/
http://www.pubnub.com/blog/sending-ios-push-notifications-via-apns-javascript-using-apns-phonegap/
I wrote a tut for for Android with GCM too, if you want to check out :-)
I have to prepare a web Admin for the mobile apps that have iPhone and android versions. I don't know how to send the push notifications to specific users or to all users from my ASP.net web Admin.
Take a look at the rest API.
Pratically you have to perform a POST (using maybe RestSharp) passing your app id\key and the content of the push.