Developing Mobile Solutions with Windows Azure Part IIChris Risner and Nick HarrisTechnical Evangelists3-039

AgendaExtending Mobile ServicesStorageGeolocationPush

Mobile SolutionsPart 1 with Josh Twist• Mobile Services

Part 2• Websites• Storage• Worker Roles• Queues

Demo: The Mobile Services Client

Storing Files with Windows Azure Storage• Blobs and Containers• Shared Access Signatures• Security

Demo: Web API, Storage, and Clients

Next Steps for Web API, Storage, and SAS• Language support• SAS vs Direct Connect• CDN• Optimize calls to CreateIfNotExists• Uploading larger files in blocks• Media Services

Handling Geolocation

• GPS• Latitude and longitude• Geofencing

Demo: Web API and Geolocation

Next Steps for Geolocation

• Serialization format• Spatial support• Usage on the device• Accuracy on the device

Handling Push

• Queues• Worker roles• MPNS and WNS

Demo: Queues, Worker Roles, and Push

Next Steps for Push

• Handling offline state• Handling quotas• Handling invalid channels• Different types of notifications

• Tile• Toast• Badge• Raw

Final Considerations

• Multi-client support• Storage• Geolocation• Push• Mobile Services and more

Resources

• www.windowsazure.com• @chrisrisner and @nickha• Related Sessions

• 2-121 : Windows Store Device Apps (Thursday)• 3-036 : Building Services for Any Client with ASP.NET Web API (Thursday)• 3-129 : Windows 8 Connectathon with Windows Azure Mobile Services (Thursday)• 3-004 : Create Cross-platform Apps with Portable Class Libraries (Friday)

• Check out azureconf.com!

• Follow us on Twitter @WindowsAzure

• Get Started: www.windowsazure.com/build

Resources

Please submit session evals on the Build Windows 8 App or at http://aka.ms/BuildSessions

© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.