When not to use mobile-web-app-capable : <p>I've <a href="http://www.html5rocks.com/en/mobile/fullscreen/#toc-launch" rel="noreferrer">read</a> on how adding</p>

<pre class="lang-html prettyprint-override"><code>&lt;meta name="apple-mobile-web-app-capable" content="yes"&gt;
&lt;meta name="mobile-web-app-capable" content="yes"&gt;
</code></pre>

<p>to your HTML will allow users to add that page to their home screen and use it as an App. So I'm wondering whether it would make sense to add these meta tags to pretty much all the HTML I generate. After all, the user doesn't <em>have</em> to install them as apps, but if they choose to do so, why should I prevent that?</p>

<p>I'm mostly thinking about unauthenticated content here which is static from a HTML server perspective, although it may well be interctive thanks to client-side JavaScript. To give you an idea, think about single-page tutorials, perhaps with some interactive code demo in it. Something like that.</p>

<ul>
<li>Am I making any promises by adding these tags?</li>
<li>In what situations should I avoid adding them?</li>
</ul>
