Revision 474949 of Developing app functionality

  • Revision slug: Web/Apps/Quickstart/Build/Developing_app_functionality
  • Revision title: Developing app functionality
  • Revision id: 474949
  • Created:
  • Creator: chrisdavidmills
  • Is current revision? No
  • Comment

Revision Content

We have already looked at developing web apps — in Your first app we reviewed the basic code steps required to make an app installable, talked about different open web app types, and said a few words about Web APIs and permissions required to use certain device APIs. Read it first if you've not already done so. In this article we talk about the types of functionality you might want to implement in a bit more detail.

Open web apps are no different to normal web sites/pages in terms of how you code functionality. They run on regular web technologies, all of whihc you can find detailed documentation for on this site, for example:

There are a few differences here and there. A manifest.webapp file is required to define app information such as permissions, locales, icons, etc., and there are a variety of special APIs available to allow you to implement install functionality, charge money for your apps, and access device features such as contacts, battery status and device storage.

You can find a list of APIs and required permissions at App permissions, and a more general index of all API interfaces.

Revision Source

<p>We have already looked at developing web apps — in <a href="/en-US/docs/Web/Apps/Quickstart/Build/Your_first_app">Your first app</a> we reviewed the basic code steps required to make an app installable, talked about different open web app types, and said a few words about Web APIs and permissions required to use certain device APIs. Read it first if you've not already done so. In this article we talk about the types of functionality you might want to implement in a bit more detail.</p>
<p>Open web apps are no different to normal web sites/pages in terms of how you code functionality. They run on regular web technologies, all of whihc you can find detailed documentation for on this site, for example:</p>
<ul>
  <li><a href="/en-US/docs/Web/Guide/HTML/HTML5">HTML5</a></li>
  <li><a href="/en-US/docs/Web/CSS">CSS</a></li>
  <li><a href="/en-US/docs/JavaScript">JavaScript</a></li>
  <li><a href="/en-US/docs/HTML/Canvas">Canvas</a></li>
  <li><a href="/en-US/docs/AJAX">Ajax</a></li>
  <li><a href="/en-US/docs/HTML/Using_the_application_cache">Offline resources in Firefox</a></li>
  <li><a href="/en-US/docs/Web/Guide/DOM/Storage">DOM Storage</a></li>
  <li><a href="/en-US/docs/IndexedDB">IndexedDB</a></li>
  <li><a href="/en-US/docs/DragDrop/Drag_and_Drop">Drag and drop</a></li>
</ul>
<p>There are a few differences here and there. A <a href="/en-US/docs/Web/Apps/Manifest"><code>manifest.webapp</code></a> file is required to define app information such as permissions, locales, icons, etc., and there are a variety of special APIs available to allow you to implement <a href="/en-US/docs/Web/API/Apps.installPackage">install</a> functionality, <a href="/en-US/docs/Web/Apps/Quickstart/Build/Payments">charge money for your apps</a>, and access device features such as <a href="/en-US/docs/WebAPI/Contacts">contacts</a>, <a href="/en-US/docs/WebAPI/Battery_Status">battery status</a> and <a href="/en-US/docs/WebAPI/Device_Storage">device storage</a>.</p>
<p>You can find a list of APIs and required permissions at <a href="/en-US/docs/Web/Apps/App_permissions">App permissions</a>, and a more general <a href="/en-US/docs/Web/API">index of all API interfaces</a>.</p>
Revert to this revision