diff options
Diffstat (limited to 'docs/html/guide/publishing/preparing.jd')
| -rw-r--r-- | docs/html/guide/publishing/preparing.jd | 20 |
1 files changed, 10 insertions, 10 deletions
diff --git a/docs/html/guide/publishing/preparing.jd b/docs/html/guide/publishing/preparing.jd index 267cba2..4db546d 100644 --- a/docs/html/guide/publishing/preparing.jd +++ b/docs/html/guide/publishing/preparing.jd @@ -94,12 +94,12 @@ orientation changes. </li> </ul> <h3 id="eula">2. Consider adding an End User License Agreement in your -application</h4> +application</h3> <p>To protect your person, organization, and intellectual property, you may want to provide an End User License Agreement (EULA) with your application. -<h3 id="iconlabel">3. Specify an icon and label in the application's manifest</h4> +<h3 id="iconlabel">3. Specify an icon and label in the application's manifest</h3> <p>The icon and label that you specify in an application's manifest are important because they are displayed to users as your application's icon and @@ -114,7 +114,7 @@ display the icon and label to users. </p> <p>As regards the design of your icon, you should try to make it match as much as possible the style used by the built-in Android applications.</p> -<h3 id="logging">4. Turn off logging and debugging and clean up data/files</h4> +<h3 id="logging">4. Turn off logging and debugging and clean up data/files</h3> <p>For release, you should make sure that debug facilities are turned off and that debug and other unnecessary data/files are removed from your application @@ -129,9 +129,9 @@ application project.</li> code.</li> </ul> -<h2 id="finalcompile">Before you do the final compile of your application</h3> +<h2 id="finalcompile">Before you do the final compile of your application</h2> -<h3 id="versionapp">5. Version Your Application</h4> +<h3 id="versionapp">5. Version Your Application</h3> <p>Before you compile your application, you must make sure that you have defined a version number for your application, specifying an appropriate value for both @@ -149,7 +149,7 @@ element in the application's manifest file, using appropriate values. </p> <p>For detailed information about how to define version information for your application, see <a href="{@docRoot}guide/publishing/versioning.html">Versioning Your Applications</a>.</p> -<h3 id="cryptokey">6. Obtain a suitable cryptographic key</h4> +<h3 id="cryptokey">6. Obtain a suitable cryptographic key</h3> <p>If you have read and followed all of the preparation steps up to this point, your application is compiled and ready for signing. Inside the .apk, the @@ -222,20 +222,20 @@ to download Maps data. </li> href="#signing">Signing Your Applications</a>.</p> -<h2 id="compile">Compile Your Application</h3> +<h2 id="compile">Compile Your Application</h2> <p>When you've prepared your application as described in the previous sections, you can compile your application for release. </p> -<h2 id="post-compile">After Compiling Your Application</h3> +<h2 id="post-compile">After Compiling Your Application</h2> -<h3 id="signapp">8. Sign Your Application</h4> +<h3 id="signapp">8. Sign Your Application</h3> <p>Sign your application using your private key. Signing your application correctly is critically important. Please see <a href="#signing">Signing Your Applications</a> for complete information. </p> -<h3 id="testapp">9. Test Your Compiled and Signed Application</h4> +<h3 id="testapp">9. Test Your Compiled and Signed Application</h3> <p>Before you release your compiled application, you should thoroughly test it on the target mobile device (and target network, if possible). In particular, |