Merge pull request #685 from html5rocks/fullscreen_article

more changes after techwriter review #484

content/mobile/fullscreen/en/index.html

@@ -302,7 +302,7 @@ <h3 id="toc-keepuserin">Keep the user in the fullscreen experience</h3>
 <pre class="prettyprint">window.history.go(-1)</pre>
 
 <h3 id="toc-letuserchoose">Let the user choose when to go fullscreen</h3>
-<p>There is nothing more annoying to the user than a web site doing something unexpected.  When a user navigates to your site don’t try and trick them into fullscreen.</p>
+<p>There is nothing more annoying to the user than a web site doing something unexpected.  When a user navigates to your site don't try and trick them into fullscreen.</p>
 
 <p>Don't intercept the first touch event and issue a requestFullScreen.</p>
 <ol>
@@ -318,10 +318,16 @@ <h3 id="toc-letuserchoose">Let the user choose when to go fullscreen</h3>
 <p>If you want to launch apps fullscreen do think about using the install experiences for each platform.</p>
 
 <h3 id="toc-nospam">Don't spam the user to install your app to a homescreen</h3>
-<p>If you plan on offering a fullscreen experience via the installed app mechanisms, then just because you have the ability to detect if a user's app is not running as an installed app does not mean the user wants to install your app all the time. </p> 
+<p>If you plan on offering a fullscreen experience via the installed app mechanisms be considerate to the user:</p>
+<ul>
+  <li>Be discreet. Use a banner or footer to let them know they can install the app.</li>
+  <li>If they dismiss the prompt, don't show it again.</li>
+  <li>On a users first visit they are unlikely to want to install the app unless they are happy with your service.  Consider prompting them to install after a positive interaction on your site.</li>
+  <li>If a user visit your site regularly and they don't install the app, they are unlikely to install your app in the future.  Don't keep spamming them.</li>
+</ul>
 
 <h2 id="conslusions">Conclusions</h2>
-<p>While we don’t have a fully standardised and implemented API, using some of the guidance presented in this article you can easily build experiences that take advantage of the user's entire screen, irrespective of the client.</p>
+<p>While we don't have a fully standardised and implemented API, using some of the guidance presented in this article you can easily build experiences that take advantage of the user's entire screen, irrespective of the client.</p>
 
 <blockquote class="commentary talkinghead talkinghead-pk">If you know of any good patterns for full-screen, leave a comment and we can let the world know.  If you know of anti-patterns in full-screen let us know so we can update the article to save the frustrations of millions of users on the web. </blockquote>