3 ms·
Isn't it because the browser loads user interface and code all the time (sure, there's caching, but still), while apps only load data?
by kombine 11y ago
Isn't it because the browser loads user interface and code all the time (sure, there's caching, but still), while apps only load data?
- asadotzler 11y agoApps never download 100MB updates every few weeks either, right?
- err4nt 11y agoYou can create VERY lightweight offline-cacheable offline apps, try adding this to your home screen: App: http://staticresource.com/quotes.html http://staticresource.com/quotes.html
- ndesaulniers 11y agoThis year, browsers are implementing the Service Worker spec [0] which is a major improvement to the previous App Cache spec [1]. Both could be used to load UI (and all other static assets) when offline. There are also numerous headers for describing TTL for downloaded assets, and APIs for offline storage (localStorage, indexedDB). I think the main differences are that while the web has these capabilities, you don't get them for free. You do have to go out of your way to use them. Usually, they're developed assuming an Internet connection, then made to work offline. Usually, it's the other way around for native apps. [0] http://www.w3.org/TR/service-workers/ http://www.w3.org/TR/service-workers/ [1] http://www.w3.org/html/wg/drafts/html/master/browsers.html#appcache http://www.w3.org/html/wg/drafts/html/master/browsers.html#a...