Explain xkcd: It's 'cause you're dumb.
Title text: But still, my scheme for creating and saving user config files and data locally to preserve them across reinstalls might be useful for--wait, that's cookies.
This comic refers to the kind of "inventions" which seem new from the point of view of a smartphone (handheld computer) user, but have already been around for a long time on desktop or laptop/notebook computers.
Cueball has a clever idea to skip the downloading and installing of applications on mobile phones: he would host the applications online instead, and provide links to the servers. The apps wouldn't stay on the phone all the time; instead the phone would download each app again every time the user wanted to run it.
The page usually isn't saved long-term on the user's computer; instead the browser downloads it again when needed. HTML5 does however offer the option of caching web application files locally so it can remain operational when there is no network connection.
In the title text, Cueball's idea for local application storage already exists in the HTTP protocol as cookies. The more flexible web storage was originally part of the HTML5 specification, but it's now in a separate specification.
Native phone applications and web applications are not completely interchangeable. Web applications may not allow access to more advanced or platform-specific resources. Projects like Apache Cordova make these resources available to web applications by creating a native application wrapper for the web application.
- [Cueball and Megan are standing next to each other.]
- Cueball: Installing things has gotten so fast and painless.
- Cueball: Why not skip it entirely, and make a phone that has every app "installed" already and just downloads and runs them on the fly?
- I felt pretty clever until I realized I'd invented webpages.
add a comment! ⋅ add a topic (use sparingly)! ⋅ refresh comments!
explainxkcd has it pretty easy with this one since the comic explains a lot of itself. Maybe explain what a smartphone is and how apps work? 22.214.171.124 05:28, 12 May 2014 (UTC)
For some reason, this reminded me of the old Snaptu app. (https://en.wikipedia.org/wiki/Snaptu) 126.96.36.199 07:02, 12 May 2014 (UTC)
Maybe it should be mentioned that sometimes you DON'T want to auto-install every application and give it access to all your phone resources. Because, you know, malware. -- Hkmaly (talk) 09:47, 12 May 2014 (UTC)
I wonder why he chose
localStorage... seems like
localStorage does a better job of storing configs. greptalk12:06, 12 May 2014 (UTC)
document.cookies was invented before
localStorage. --188.8.131.52 22:19, 12 May 2014 (UTC)
Firefox OS can technically do this, and technically does this. greptalk12:07, 12 May 2014 (UTC)
Web pages and native apps still has a few essential differences that prevent us to interchange them practically, at least for now. The latter can be compiled and optimized into binaries that executes performantly on the specific device/platform. Current web standards don't make pages/sites/apps this way, the web browser needs to load the text codes then interpret and run them on the fly, which is much slower. 184.108.40.206 08:33, 16 May 2014 (UTC)
The phrase "[...] a phone that has every app "installed" [...]" from Cueball's dialogue seems to conflict with the explanation. I understood it as the phone would have all the apps installed, but with only the "header" data. In the Android context, I suppose that would be the AndroidManifest.xml. In the Windows context, I suppose that would be the registry entries. 220.127.116.11 00:30, 11 November 2015 (UTC)