A new release of the .NET and node.js backends for Azure Mobile Services added support for logging in to the services by using native SDKs from Google, Microsoft and Facebook. The post shows how to use the client SDKs to provide a better login experience to the users of mobile applications.
Recently we announced splitting the user experience between Service Bus and Notification Hubs to enable a better experience for Notification Hubs. Now, we are now making the default of NamespaceType to be ‘Messaging’ to align with the Portal behavior.
Learn how to push a rich notification with an image using Notification Hubs in iOS8 & 7.
A new release of the .NET backend for Azure Mobile Services improves the experience when using Azure Storage tables – continuation links are now exposed and can be used for paging through large tables.
The Azure Mobile Services team is sponsoring a booth and mini-hackathon at Xamarin Evolve in Atlanta! We’ll also be presenting…
We’ve just released the beta version of the iOS offline SDK, which adds support for accessing Table Storage when using a .NET backend Mobile Service. In order to add this support, we made a minor breaking change to the offline SDK.
Custom authentication scopes for social login providers, single sign-on for store applications, updated dependency to the latest ASP.NET Web API, among other updates in the latest release of the Azure Mobile Services .NET backend.
In order to simplify the experience which today combines both Notification Hub and messaging entities, Service Bus backend is working towards enhancing the user experience.
To follow up on the announcement of Azure Search last week, I wanted to take a minute to give a bit of framing on why we built Azure Search and how we picked its current capabilities.
This article shows you how to use socket.io to do realtime communication with your Azure Mobile Service Node backend.