Video for this session: http://www.youtube.com/watch?v=IETe7va_sQI Give your feedback on the session: http://bit.ly/xamfeedback How do you architect an application that relies on a flaky Internet connection? This talk will cover local caching of models, web caching, server synchronization and UI allowances you need to make to keep the user in control and happy.

1. The Disconnected
Mobile Device
How to keep your users happy in the face of
slow and faulty network connections
July 26th, 2012
Copyright 2012 © Xamarin Inc. All rights reserved

2. Agenda
The Disconnected Mobile Device
Frank A. Krueger
Developer at Xamarin
frank@xamarin.com
@praeclarum on Twitter
Xamarin
Copyright 2012 © Xamarin Inc. All rights reserved

3. Disconnected
http://blog.davidsingleton.org/mobiletcp

4. Mobile Users’ Bill of Rights
1. The App should tell the User if there are
problems
2. The User can tell the App to try harder
3. The App should be automatically trying to
update data in the background
4. The App should display old data, up until new
data is available
5. The User can still post data when disconnected,
and it will be transmitted ASAP

5. Architecture Implications
• Need to handle and recover from errors
• Need to perform all network communications
in the background
• Need to cache network data
• Need to treat server commands as data

6. Demo
Show all the steps necessary to implement
the Bill of Rights

7. Conclusion
You need to encapsulate all of this into user
interface controls
It’s too much to implement every time you
want to write an app or a new screen in an
app

8. Xamarin
Seminar
Please give us your feedback
http://bit.ly/xamfeedback
Follow us on Twitter
@XamarinHQ
Copyright 2012 © Xamarin Inc. All rights reserved