Good Tech for Hard Places: Fighting Ebola with Javascript Offline Apps...
summary
JavaScript offline apps power contact tracing and call centers during the West Africa Ebola outbreak, using CouchDB and PouchDB plus Angular/Cordova; replication of everything causes 40+ minute syncs and browser-storage eviction, so selective replication cuts 12‑hour delays to near‑instant and moves call‑center response from ~5 days to 24 hours. Built mobile and call‑center apps that work offline, solved conflict by data‑modeling (separate changing bits), and learned to avoid Chrome’s temporary‑storage data loss.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 0:12Background
- 0:47What is Ebola
- 2:02How does contact tracing work
- 8:39What is CouchDB
- 10:44CouchDB in Nigeria
- 11:19Too greedy
- 11:42Replication
- 12:09Why replication
- 12:29Contact tracing
- 13:32Call centers
- 15:14Conflicts
- 17:32Space
- 18:50Beginner mistakes
- 19:26Get an expert
- 21:13State of the outbreak
- 23:29Conclusion
related talks
31mI'm offline, cool! What now?
22mSurviving the Offline Apocalypse
30mOffline First: Making Your App Awesome When the Network Isn't
45mOffline First (Web) Apps
32mOnConnectionLost - The Life of an Offline Web Application
45mOffline UX
38mMoving seamlessly through offline and online
38mHow we developed an Offline‑First app using Persistent Storage