When the connection fails
•Als PPTX, PDF herunterladen•
1 gefällt mir•560 views
Going offline on mobile
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (15)
Andere mochten auch
Andere mochten auch (20)
Ähnlich wie When the connection fails
Ähnlich wie When the connection fails (20)
Mehr von Barbara Fusinska
Mehr von Barbara Fusinska (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
When the connection fails
- 1. When connection fails Going offline on mobile @basiafusinska basiafusinska.com barbarafusinska.com
- 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
- 26. PROBLEMS
- 28. CACHED UPDATES
- 29. PROBLEMS
- 30. PROS & CONSS
- 34. PROBLEMS
- 36. DATA SYNC
- 40. INCREMENTAL SYNC
- 44. HOW TO GATHER INCREMENTAL DATA?
- 45. SERVER SIDE
- 46. LOCAL SIDE
- 47. Sequential changes Created & updated Created & deleted Updated & deleted
- 48. 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
Hinweis der Redaktion
- Cookies, Local Storage, Local databases
- HTML 5
- How to Cache data? Twitter/Facebook – last posts/tweets, Background process -> local storage/database Strategies: - load fresh data, and when it fails take it from cache always load data from local storage/db
- Need of fresh data (seconds/minutes) – loading process can be to heavy, How to communicate age of the data to the user?
- Updates sent when online
- Calling extrenal services – proxy pattern Calling external service that uses time of the request internally
- We don’t always want to download the whole internet (fb/twitter) Better for apps that are ment to be used online – not data based, based of fresh data
- Need of local db Full copy (user/account context) of the server db Need of Data Sync
- Using external services (example: setting up new google callendar integration) Different DB (server, mobiles) – proper API, platform agnostic
- Data Sync is hard, expensive, difficult Suitable for apps when it makes sense to download all the data (crm system)
- Initial sync Paginated (we don’t want to kill out the device), retries User sepcific data/access rights
- Can also be paginated Timestamps
- When paginating – timestamp returned from the server can be used Server returns: New object that has shown up since that time Objects that were deleted (or we don’t have access right any more) Changed objects (whole object or specific attributes) When event driven approach – only new objects -> events
- Gathers data from last timestamp
- Cannot store all the devices timestamps Data driven approach: store Creation/Update/Delete datetimes Event driven approach: event timestamp
- Last sync timestamp Creation/update/delete datetime – not optimal Flags: IsNew, IsDirty, ToBeDeleted, separate table for deleted ids
- …analogy to merge & rebase Allowing clients/devices to decide? Created & updated -> NEW - NEW Created & deleted -> don’t sync or 2 requests - Not posted! Updated & deleted -> delete or 2 requests - Delete
- Local side: If new object in relation is replaced by existing one (form server) there are left overs in a database. They shoud be cleaned
- Regular vs. document/text data
- Options: Local changes Server changes Custom changes
- Auto merge (not really possible if we update whole object) Allowing user to merge