What changes when we go offline first?
We all know how to build web apps around a central server. Increasingly, we want to develop apps in which the user can still get work done while offline and that sync their data the next time an internet connection is available. Martin Kleppmann shares recent computer science research that is helping develop the abstractions and APIs for the next generation of applications.
| Talk Title | What changes when we go offline first? |
| Speakers | Martin Kleppmann (University of Cambridge) |
| Conference | O’Reilly Velocity Conference |
| Conf Tag | Build systems that drive business |
| Location | London, United Kingdom |
| Date | October 31-November 2, 2018 |
| URL | Talk Page |
| Slides | |
| Video | Talk Video |
We all know how to build web apps around a central server. However, clients—especially mobile clients—are not always online and thus can’t always reach the server. Increasingly, we want to develop apps in which the user can still get work done while offline and that sync their data the next time an internet connection is available. We call such apps “offline first.” However, in the offline-first world, there is an issue that is not so often talked about: moving from server centric to offline first deeply changes the programming model. For example, if several users each change data while offline, how do you merge them back together again? Martin Kleppmann shares recent computer science research that is helping develop the abstractions and APIs for the next generation of applications.
