Editing 1367: Installing
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 12: | Line 12: | ||
[[Cueball]] has a clever idea to skip the 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. | [[Cueball]] has a clever idea to skip the 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. | ||
β | However, web pages and {{w|web application}}s already work like this. Clicking a link will make the browser download a web page and render {{w|HTML|HTML code}} and {{w|JavaScript}} that it links to. | + | However, web pages and {{w|web application}}s already work like this. Clicking a link will make the browser download a web page and render {{w|HTML|HTML-code}} and {{w|JavaScript}}s or plugin data (such as {{w|Adobe Flash|Flash}} applets) that it links to. |
The page usually isn't saved long-term on the user's computer; instead, the browser downloads it again when needed. {{w|HTML5}} does however offer the option of {{w|Cache_manifest_in_HTML5|caching web application files locally}} so it can remain operational when there is no network connection. | The page usually isn't saved long-term on the user's computer; instead, the browser downloads it again when needed. {{w|HTML5}} does however offer the option of {{w|Cache_manifest_in_HTML5|caching web application files locally}} so it can remain operational when there is no network connection. | ||
Line 18: | Line 18: | ||
In the title text, Cueball's idea for local application storage already exists in the HTTP protocol as {{w|HTTP cookie|cookies}}. The more flexible {{w|Web storage|web storage}} was originally part of the HTML5 specification, but it's now in a separate specification. | In the title text, Cueball's idea for local application storage already exists in the HTTP protocol as {{w|HTTP cookie|cookies}}. The more flexible {{w|Web storage|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. | + | Native phone applications and web applications are not completely interchangeable. The web browser that is needed to run web applications on a mobile phone doesn't allow access to several of the phone's resources, like notifications and sensors. The {{w|Firefox OS}} project is trying to standardize access to these resources so that the entire user interface can be a web application, while projects like {{w|Apache Cordova}} make these resources available to web applications by creating a native application wrapper for the web application. |
==Transcript== | ==Transcript== |