Indiana Jones and the Offline Apps

Vivimos en un mundo conectado, o eso es lo que nos han vendido.

En una sociedad que afirma que hay conectividad en todas partes, las situaciones en las que ésta brilla por su ausencia son más comunes de lo que creemos; y si queremos proporcionar la mejor experiencia para nuestros productos, tenemos que tenerlas en cuenta.

Manejar apropiadamente el estado de la conectividad de tus aplicaciones; puede hacer que éstas funcionen de manera que parezcan magia.

En esta charla comentaremos conceptos y técnicas que puedes utilizar para conseguir esta experiencia.

Transcript

1. INDIANA JONES AND THE OFFLINE APPS
6. “ Offline is not a set of techniques to make your app faster. It is a philosophy that drives how your product is experienced. 6
7. 1. THE REASONS
8. Source: Ericsson Reports 8
9. People who deserve to use your apps 9
10. AIR IS A LIMITED MEDIUM 10
11. THE INTERNET 11
13. 2. PIECES OF THE PUZZLE
14. OPTIMISTIC UX 14
15. NAIVE APPROACH 15 Place your screenshot here Place your screenshot here Place your screenshot here
16. OPTIMISTIC APPROACH 16 Place your screenshot here Place your screenshot here Place your screenshot here
17. OPTIMISTING* BETTER Place your screenshot here 17 *I know the term “optimist” does not exist
18. SALIENCY 18
19. HIGH SALIENCY Place your screenshot here 19
20. REDUCED SALIENCY Place your screenshot here 20
21. VERY LOW SALIENCY Place your screenshot here 21
22. GRACEFUL DEGRADATION 22
23. Place your screenshot here 23
24. PREDICTIVE OFFLINE 24
25. Place your screenshot here 25 Place your screenshot here API ZERO CASE FEED
26. A GREAT OFFLINE EXPERIENCE RECIPE ➢ Highly optimistical ➢ Low to no saliency ➢ Gracefully aware of errors 26
28. 3. A LITTLE MORE TECHNICAL INSIGHT
29. SIT AND THINK ➢ Understand your platform ➢ Understand your feature ➢ Understand your limitations 29
30. LOCAL SERVICE
31. REMOTE SERVICE
32. SERVER CLUSTERING
33. PLATFORM SYNCING
34. COLLABORATIVE
35. OFFLINE CAPABILITIES
37. LOGIC DIFFERENTLY 37 Random Use Case
38. LOGIC DIFFERENTLY 38 API Call Cache modification UI side effects Random use case
39. LOGIC DIFFERENTLY 39 API Call Cache modification UI side effects Random use case
40. LOGIC DIFFERENTLY 40 API Call Cache modification UI side effects Worker Job Cache modification API Call “Classic” Use Case “Offline” use case
41. SYNCING BETWEEN DEVICES 41
42. THE GIT WAY 42 PULL MERGE PUSH
43. TRACKING MODIFICATIONS VIA METADATA 43 { "id": "sefford", "rev": "1-abc", "data": "..." } ➢ Vector Clocks ➢ Lamport timestamps
44. “ Conflicts are not an error condition, the are the result of your infrastructure allowing the same data set to be modified across disconnected systems. The introduction of such conflicts in such a topology is the expected behaviour and their programmatic resolution is a core piece of the application logic. 44 https://developer.ibm.com/dwblog/2015/cloudant-document-conflicts-two/
45. OFFLINE TECHNOLOGIES 45 Web App Polymer App Toolbox Ionic Hoodie WorkManager SyncAdapters CouchDB Realm Firebase
47. EPILOGUE
48. FINAL TIPS ➢ Offline can be implemented à la carte ➢ Introspection over the playing field is critical ➢ Strive to build apps that work like magic! 48
49. CREDITS AND RESOURCES Special thanks to all the people who made and released these awesome resources for free: ➢ Offline first resource website ➢ Miguel Quiñones awesome presentation about offline ➢ Nice list of resources about offline topics ➢ What’s graceful degradation? ➢ Cesar Valiente’s Wunderlist Sync Architecture presentation ➢ Presentation template by SlidesCarnival ➢ Maps in slides from David Rumsey Map Collection 49
50. 50 THANKS! Any questions for me? You can find me at @sefford & sefford@gmail.com