mozilla

Revision 416355 of Publishing the app

  • Revision slug: Web/Apps/Tutorials/General/Publishing_the_app
  • Revision title: Publishing the app
  • Revision id: 416355
  • Created:
  • Creator: kohei.yoshino
  • Is current revision? No
  • Comment Updated links
Tags: 

Revision Content

Once you have finished your app, you need to do the following:

  • Deploy the app (hosted apps only) - Arrange for Web hosting and get the app up and running on the Web server. Packaged apps do not require hosting.
  • Publish the app - Make the app available for end users to install.

Deploying the app

You need to host a hosted app on a publicly accessible Web server, just like any other website. There are numerous ways to do this.

GitHub

If a hosted app is purely static (HTML, CSS, JavaScript, but no server-side processing), GitHub Pages is a solid hosting option. It will serve your manifest with the correct MIME type if you give it a .webapp extension.

Generic hosting solutions

For an app that needs a server-side processing, use a generic hosting option (like a Web server you may already own or have access to) with the right capabilities, or a hosting provider specifically tailored to the needs of your app, like Heroku or Google App Engine.

Publishing the app

Once your Web app has been deployed, you obviously want to make it installable by your intended user base. There are currently two options for publishing your app.

Submit to Firefox Marketplace

Submitting your app to the Firefox Marketplace has many advantages, such as increased publicity, no need to implement special APIs on your own Web site, and the possibility of publishing paid apps more easily.

Publish on your own website

If you want to let people install your app from a website you own, you must implement some JavaScript code on your Web site to manage installing and updating your app into users' browsers.

Revision Source

<p>Once you have finished your app, you need to do the following:</p>
<ul>
  <li>Deploy the app (hosted apps only) - Arrange for Web hosting and get the app up and running on the Web server. <a href="/en-US/docs/Web/Apps/Packaged_apps" title="/en-US/docs/Apps/Packaged_apps">Packaged apps</a> do not require hosting.</li>
  <li>Publish the app - Make the app available for end users to install.</li>
</ul>
<h2 id="Deploying_the_app">Deploying the app</h2>
<p>You need to host a hosted app on a publicly accessible Web server, just like any other website. There are numerous ways to do this.</p>
<h3 id="GitHub">GitHub</h3>
<p>If a hosted app is purely static (HTML, CSS, JavaScript, but no server-side processing), <a class="external" href="http://pages.github.com/">GitHub Pages</a> is a solid hosting option. It will serve your manifest with the <a href="/en-US/docs/Web/Apps/Manifest#Serving_from_GitHub">correct MIME type</a> if you give it a <code>.webapp</code> extension.</p>
<!-- comment out Dropbox reference per bug 791795
<p>Cloud storage service <a class="external" href="http://www.dropbox.com/">Dropbox</a> can also <a class="external" href="http://lifehacker.com/5528104/use-dropbox-to-share-and-host-your-web-site">be used for this purpose</a>.</p>
-->
<h3 id="Generic_hosting_solutions">Generic hosting solutions</h3>
<p>For an app that needs a server-side processing, use a generic hosting option (like a Web server you may already own or have access to) with the right capabilities, or a hosting provider specifically tailored to the needs of your app, like <a class="external" href="http://www.heroku.com/">Heroku</a> or <a class="external" href="http://code.google.com/appengine/">Google App Engine</a>.</p>
<h2 id="Publishing_the_app">Publishing the app</h2>
<p>Once your Web app has been deployed, you obviously want to make it installable by your intended user base. There are currently two options for publishing your app.</p>
<h3 id="Submit_to_Firefox_Marketplace">Submit to Firefox Marketplace</h3>
<p><a class="link-https" href="/en-US/docs/Web/Apps/Publishing/Submitting_an_app">Submitting your app</a> to the Firefox Marketplace has many advantages, such as increased publicity, no need to implement special APIs on your own Web site, and the possibility of publishing paid apps more easily.</p>
<h3 id="Publish_on_your_own_website">Publish on your own website</h3>
<p>If you want to let people install your app from a website you own, you must <a href="/en-US/docs/Web/Apps/JavaScript_API">implement some JavaScript code</a> on your Web site to manage installing and updating your app into users' browsers.</p>
Revert to this revision