Visual Studio Mobile Center powers end-to-end mobile app development experiences. Adrian Hall joins Scott Hanselman to showcase how to work with his TODO app data in the cloud with Visual Studio Mobile Center’s Tables feature. Check out the other Mobile Center (http://mobile.azure.com) features including Build, Test, Distribute, Identity, Crashes, and Analytics.
At Build 2016, Microsoft showcased a scalable, performant, highly available, and cross-platform IoT service and application. MyDriving uses a wide range of Azure services to process and analyze car telemetry data for both real-time insights and long-term patterns and trends. Download the code on GitHub, play with the app in a sandbox environment, or deploy it to your own Azure subscription to run. Find out more at: http://aka.ms/IoTSampleApp
In this episode, Robert is joined by Harikrishna Menon, who shows us MyDriving, an Azure IoT and Mobile sample application. This solution uses On-board diagnostics (OBD) data from your car to analyze your driving. The backend uses multiple Azure Services like IoT Hub, Stream Analytics, SQL databases, HDInsight, Machine Leaning, and App Services and how you can configure them without having to write a lot of code. The app runs on Windows, iOS and Android and is built with Xamarin. Hari shows how to make use of the full DevOps cycle (Visual Studio Team Services, HockeyApp, Xamarin Test Cloud) to build, test and distribute the app.
Matthew Henderson shows Scott the open source Field Engineer" sample application that shows how to create Azure Mobile Applications. We'll go through how TableControllers support ASP.NET MVC Applications and Web APIs, and how you can consume data from applications on your mobile device.
Kirill Gavrylyuk comes to Azure Friday to show the latest Azure App Service updates as of August of 2015 and beyond. Mobile Services features are now integrated into Azure App Service and are available to subscribers are at no additional cost! We'll see how to add Push Notifications to a Web Site running in Azure and push down to an iPad in this episode. And all the code is on GitHub!
In the cloud-first, mobile-first world, people are building Android and iOS applications and need a powerful cloud-powered backend. This session will review all of the ways that Azure can help build amazing applications on top of Microsoft’s cloud platform. This includes options for data storage, push notifications, job processing, media delivery, offline data sync, authentication and more. We’ll review all of these features at a high level and dive into some live coding demos throughout!
Targeting the screen most people keep in their pocket is critical to the modern business. This video shows how to build mobile experiences for any platform using Azure, with capabilities like data storage, offline data sync, authentication with Azure Active Directory, and push notifications.
A one-off special that looks at the how Microsoft Azure's new Hybrid Connections feature, part of the Azure BizTalk Services suite, makes building hybrid applications easy. This is not your father's hybrid solution, it's way more awesome than that.
As enterprises transition to the cloud, it is frequently necessary to leave some assets on-premises: whether it is for technical, compliance, or security reasons. Mobile Services allows you to easily create a cloud-hosted mobility layer on top of these assets, while safely connecting to them back on your premises using Hybrid Connections. Supported assets include any resource that runs on a static TCP port, including Microsoft SQL Server, MySQL, HTTP Web APIs, and most custom Web Services.
In this video, Donna Malayeri walks through how to use the new offline features in Mobile Services. This is a companion to the tutorials Get started with offline data in Mobile Services and Handle conflicts with offline data. With this feature, mobile applications can create and modify data even when they are offline. When the app is back online, it can synchronize local changes with the Mobile Services backend. The feature also includes support for detecting conflicts when the same record is changed on both the client and the backend, allowing the developer to decide how to handle such conflicts.