Main Content

Taking It Offline: Lessons Learned

A talk by Paul Rosen at edUI 2013

About the Talk

November 5, 2013 3:30 AM

Richmond, VA

Richmond, VA

Creating an offline application that seems natural to the end user requires a number of different technologies to work together: Data needs to be saved in LocalStorage but mirrored to the server whenever possible; the browser’s history must be manipulated when the user expects it (so that the “back” button and URLs work intuitively); and the entire business logic of the program needs to reside in JavaScript, which requires the use of a JavaScript Framework to keep the app maintainable. In addition, since the user may never refresh the page, any remote changes must be picked up automatically.

The entire approach to implementing the site must be different, and I’ll share the lessons I learned as I figured out how the various technologies either work or interfere with each other.

Ratings and Recommendations

Avg. Rating

Average based
on 4 ratings

comments powered by Disqus