1. When connection fails @basiafusinska basiafusinska.com barbarafusinska.com Going offline on mobile

2. About me @basiafusinska basiafusinska.com barbarafusinska.com

3. Agenda Why & when What How – Data sync patterns – Full offline experience – Local data sync – Conflicts

4. WHY DO WE EVEN NEED OFFLINE?

10. UX PATTERNS FOR OFFLINE APPS

11. DON’T LOSE LOCAL DATA…

12. DON’T TREAT OFFLINE LIKE AN ERROR…

13. DON’T SCARE THE USER…

14. COMMUNICATE…

15. DON’T LIE…

16. Atwood’s Law Any application that can be written in JavaScript, will eventually be written in JavaScript

17. HOW TO BUILD FULL OFFLINE EXPERIENCE?

18. Cache Retrieving data from a new source Local copy

21. Local database How much data do you need?

23. OFFLINE IS NOT A PROBLEM

24. OFFLINE PATTERNS cache, deferred updating, local database sync

25. BACKGROUND CACHING

26. PROBLEMS

27. DEFERRED UPDATING

28. CACHED UPDATES

29. PROBLEMS

30. PROS & CONSS

31. LOCAL DATABASE SYNC

32. FULL OFFLINE EXPERIENCE

33. VERSIONING & MIGRATION

34. PROBLEMS

36. DATA SYNC

37. Syncing technologies http://grasmeyer.com/blog/2013/10/8/a-comparison-of-syncing-technologies

40. INCREMENTAL SYNC

41. GET /endpoint/{timestamp}

43. POST /enpoint {data}

44. HOW TO GATHER INCREMENTAL DATA?

45. SERVER SIDE

46. LOCAL SIDE

47. Sequential changes Created & updated Created & deleted Updated & deleted

48. RELATIONS

50. RESOLVING RELATIONS

51. CONFLICTS

52. Sync new/created data No conflicts … unless relations

53. DELETE

54. UPDATES

59. Summary Full offline experience Data sync Conflict resolution

60. Questions? @basiafusinska barbarafusinska.com basiafusinska.com