3 ms·
I'd like to echo this, specifically focusing on AJAX. It's not enough to be offline-friendly if your requests don't themselves retry or work well when internet
by lstamour 13y ago
I'd like to echo this, specifically focusing on AJAX. It's not enough to be offline-friendly if your requests don't themselves retry or work well when internet is spotty. A problem I've often encountered in online-only scenarios is when AJAX calls fail. How do you ultimately retry them? At a certain point, you need the same infrastructure you'd be building for an offline app to cache and queue requests, as well as present sensible non-success responses. So, just as mobile first solved problems for both tablets and focusing a design, offline first can solve problems with error messages, caching to speed up online responses and AJAX retries.
- gr2m 13y agoor you go away of AJAX calls entirely, by storing all data offline and having a separate process that synchronizes all changes, like remotestorage.io does it, or hood.ie
- lstamour 13y agoThat's what I implied by AJAX retry. That you need some method that sensibly queues the request, until it succeeds or is no longer needed. That process could easily be called synchronization, sure. Depends on the app, really. The request might "expire" or be no longer necessary, so it wouldn't show up at "sync" time. Perhaps the request could be automatically retried through other devices that are connected -- imagining for the moment, an app that could use bluetooth or local wifi to communicate an operation across to other running instances even when offline.