I'm developing a Xamarin.Forms app with a .Net Web API backend. I definitely don't want to do long polls on my app to the server, but I need the app to remain updated with the server information.

I thought push notifications were the solution (I even started developing that way), until I saw several examples using it only for messages. Is this so? Can I use push notifications only to send messages to the user's phone?

I already use SignalR in my application (I also have a MVC frontend) and I just found out I can use a SignalR client within my Xamarin.Forms app.

Is this the right way to go?

How do I maintain my app's data updated without long polling?


  • What do you mean by "right?" Jul 5 '16 at 0:10
  • 1
    What is a notification if not a message sent from the server to the client?
    – RubberDuck
    Jul 5 '16 at 1:53
  • @RubberDuck ok, but from what I saw I thought push notifications were only intended to send messages to the users, am I wrong? could I use it as a way to update my app without breaking any standards?
    – eestein
    Jul 5 '16 at 14:11
  • @RobertHarvey just from a standard point of view. Like, would I be breaking any standards by using any of the methods? What is the technology people use to handle this issue regularly? Thanks.
    – eestein
    Jul 5 '16 at 14:12
  • As you've already pointed out, push notifications are typically used for app messages. SignalR is used for general real-time communication. As far as standards go, SignalR uses standard websockets, and falls back to older technologies for web browsers that don't support websockets. I have no idea what push notifications uses. Jul 5 '16 at 14:47

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.