Lines Matching full:application
16 <li><a href="#publishing-configure">Configuring Your Application</a></li>
17 <li><a href="#publishing-build">Building Your Application</a></li>
19 <li><a href="#publishing-test">Testing Your Application for Release</a></li>
30 <p>Before you distribute your Android application to users you need to prepare it for release. The
35 <p>When you prepare your application for release, you configure, build, and test a release
36 version of your application. The configuration tasks are straightforward, involving basic code
37 cleanup and code modification tasks that help optimize your application. The build process is
39 tasks serve as a final check, ensuring that your application performs as expected under real-world
40 conditions. When you are finished preparing your application for release you have a signed
42 application marketplace such as Google Play.</p>
44 <p>This document summarizes the main tasks you need to perform to prepare your application for
46 how they are released or distributed to users. If you are releasing your application through Google
48 Checklist for Google Play</a> to be sure your release-ready application satisfies all Google Play
51 <p class="note"><strong>Note:</strong> As a best practice, your application should meet all of your
67 <p>To release your application to users you need to create a release-ready package that users can
79 <strong>Figure 2.</strong> You perform five main tasks to prepare your application for
84 <p>The signing and optimization tasks are usually seamless if you are building your application with
86 example, you can use the Eclipse Export Wizard to compile, sign, and optimize your application all
90 <p>To prepare your application for release you typically perform five main tasks (see figure 2).
92 application. For example, if you are releasing your application through Google Play you may want
93 to add special filtering rules to your manifest while you are configuring your application for
98 your application. The Android SDK contains several tools to help you test and debug your Android
105 <p>To begin preparing your application for release you need to gather several supporting items. At a
106 minimum this includes cryptographic keys for signing your application and an application icon. You
111 <p>The Android system requires that each installed application be digitally signed with a
112 certificate that is owned by the application's developer (that is, a certificate for which the
114 the author of an application and establishing trust relationships between applications. The
120 <p class="caution"><strong>Important:</strong> Your application must be signed with a cryptographic
123 <p>You may also have to obtain other release keys if your application accesses a service or uses a
125 if your application uses the <a
129 library</a>, you will need to register your application with the Google Maps service and obtain
134 <h4>Application Icon</h4>
136 <p>Be sure you have an application icon and that it meets the recommended <a
138 application's icon helps users identify your application on a device's Home
142 <p class="note"><strong>Note:</strong> If you are releasing your application on Google Play, you
146 Assets for your Application</a> for more information.</p>
150 <p>Consider preparing an End User License Agreement (EULA) for your application. A EULA can help
152 with your application.</p>
156 <p>You might also have to prepare promotional and marketing materials to publicize your application.
157 For example, if you are releasing your application on Google Play you will need to prepare some
158 promotional text and you will need to create screenshots of your application. For more
161 Graphic Assets for your Application</a></p>
163 <h2 id="publishing-configure">Configuring Your Application for Release</h2>
165 <p>After you gather all of your supporting materials you can start configuring your application
167 to your source code, resource files, and application manifest prior to releasing your application.
174 <p>Make sure you choose a package name that is suitable over the life of your application. You
175 cannot change the package name after you distribute your application to users. You can set the
176 package name in application's manifest file. For more information, see the <a
183 application for release. You can deactivate logging by removing calls to
185 <code>android:debuggable</code> attribute from the <code><application></code> tag in your
198 Leaving stray or orphaned files in your project can prevent your application from compiling and
199 cause your application to behave unpredictably. At a minimum you should do the following cleanup
209 <code>src/</code> directory should contain only the source files for your application
212 <li>Check your project for private or proprietary data files that your application does not use
216 longer being used by your application.</li>
229 <p>You should specify only those permissions that are relevant and required for your application.</p>
233 <a href="{@docRoot}guide/topics/manifest/application-element.html"><application></a>
240 <a href="{@docRoot}tools/publishing/versioning.html">Versioning your Application</a>.</p>
245 application on Google Play. For example, the <code>android:minSdkVersion</code> and
253 <p>Android provides several tools and techniques to make your application compatible with a wide
254 range of devices. To make your application available to the largest number of users, consider
262 you can create an application that functions properly and looks good on any of the screen sizes
265 <li><strong>Optimize your application for Android tablet devices.</strong>
266 <p>If your application is designed for devices older than Android 3.0, make it compatible
272 <p>If your application is designed for devices running Android 3.x, make your application
275 application project. The Support Library provides static support libraries that you can add to
276 your Android application, which enables you to use APIs that are either not available on
283 <p>If your application accesses remote servers or services, make sure you are using the production
288 <p>If you are releasing a paid application through Google Play, consider adding support for
289 Google Play Licensing. Licensing lets you control access to your application based on whether the
294 application, see <a href="{@docRoot}guide/google/play/licensing/index.html">Application Licensing</a>.</p>
296 <h2 id="publishing-build">Building Your Application for Release</h2>
298 <p>After you finish configuring your application you can build it into a release-ready
309 ADT</a>. The Export Wizard compiles your application for release, signs your application with your
310 private key, and optimizes your application with the zipalign tool. The Export Wizard should run
311 successfully if you have run or debugged your application from Eclipse and you have no errors in
312 your application (see <a href="{@docRoot}tools/building/building-eclipse.html">Building
316 suitable for signing your application. If you do not have a suitable certificate and private key,
327 private key</a> suitable for signing your application. If you do not have a suitable certificate and
334 <p>If your application relies on a remote server, make sure the server is secure and that it is
336 href="{@docRoot}guide/google/play/billing/index.html">in-app billing</a> in your application and you are
339 <p>Also, if your application fetches content from a remote server or a real-time service (such as a
342 <h2 id="publishing-test">Testing Your Application for Release</h2>
344 <p>Testing the release version of your application helps ensure that your application runs properly
345 under realistic device and network conditions. Ideally, you should test your application on at least
347 sized correctly and that your application's performance and battery efficiency are acceptable.</p>
352 done testing and you are satisfied that the release version of your application
353 behaves correctly, you can release your application to users. For more information, see
355 Application to Users</a>. If you are publishing your application on Google Play, see
