Today, we present to you Mobile Services 2.0.2-Beta Android SDK. With this new release, we introduce two new Offline features: Incremental Sync and Soft Delete.
The best mobile apps handle network interruptions gracefully, allowing users to be productive despite the lack of connectivity. Learn how you can use the offline sync feature of Azure Mobile Services, to create responsive apps that work, even when the network doesn’t.
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.
The latest version of the Azure Mobile Services SDK for Android added support for both futures (for asynchronous operations) and offline (disconnected applications). In this post I'll walk through the offline feature, by walking through the steps required to make the sample application downloaded from the portal (To do list) offline-enabled. We’ll be talking about the features as they’re needed for the app.
Addressing feedback on the usage of asynchronous calls in Android, we’ve released a major update in the Android SDK for Azure Mobile Services with futures support. With that, you can now easily perform multiple of those operations without having to deal with multiple nested callbacks. The changes are additive in most of the scenarios, but in some advanced scenarios we made a breaking change to make futures the default model used by the Azure Mobile Services Android SDK for dealing with asynchronous operations.
The best mobile apps handle network interruptions gracefully, allowing users to be productive despite the lack of connectivity. Learn how you can use the offline sync feature of Azure Mobile Services to create responsive apps that work, even when the network doesn't.