One major contributor: browser vendors have zealously guarded the right to evict things from the cache as needed, and according to algorithms of their choosing, even with the advent of PWAs.
-
-
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
To me it feels of a piece with the MP3’s (organize my folders) => iTunes (manage my local collection for me) => Spotify (manage local/remote for me) spectrum. As a platform that generally requires manual curation of local storage, apps feel line a major productivity regression.
-
On the other hand, for people with a lot of "hard-offline" situations, the ability to "set up" for offline is important, and automatic management works less good for that situation. I think the web needs a "Keep/Install" mode for that situation.
-
At the limit, eviction still possible, but combined with UI changes, much less likely
-
I think this is roughly right for "web apps" (user agent specified limits, not many specified guarantees), but I think you still want something more guaranteed via something that looks like app installs. On balance, this situation is still great though, and best in class!
-
Persistent Storage is probably what we need to evolve to handle hard cases. I.e., would you trade isolation for real persistence?
-
E.g., requiring a CSP value that opts the app into its own storage partition at all times in order to gain real persistence at install time
-
Would this mean you would have to use the same origin for all content (what about fonts?)
- 11 more replies
New conversation -
-
-
The thing that scares me a bit is knowing the data can be blown away at any time. I am imagining an offline data collection app that syncs when online, but the data gets blown away first before the reconnect and sync happens. Not sure if there is a good way to work around that.
-
Generally speaking, hints that data is really intended to be persistent work decently at resisting eviction, and could be improved in implementations. I don't think I would want a "drive by" API that didn't ALLOW engines to evict.
-
I could imagine an "install step" (
@slightlylate has called this "Keep" in the past) that would have stronger caching effects, more like the caching provided by installing a native app.
New conversation -
-
-
aka my phone
-
If you really want to test out the scenario, there's an $80 Android Go phone now available in the USA:https://www.theverge.com/circuitbreaker/2018/3/30/17179694/zte-tempo-go-android-one-price-specs-us …
End of conversation
New conversation -
-
-
Awesome? Typical situation: Phone is low on disk space, removes items from cache. App downloads the items again and again draining battery and consuming precious data plan. User has no clue why being low on space means dead battery too.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
One of the many reasons that make progressive web apps so great.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Now all we need is npm publishers to check the size of their packages before sending it out into the world, because "ain't nobody got space for dat"https://github.com/styfle/packagephobia …
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.