Lines Matching full:application
14 the container for your application binary. It contains all of the information necessary to run
15 your application on a device or emulator, such as compiled <code>.dex</code> files (<code>.class</code> files
17 resources (<code>resources.arsc</code>) and uncompiled resource files for your application.</p>
27 <p>To run an application on an emulator or device, the application must be signed using debug or
28 release mode. You typically want to sign your application in debug mode when you develop and test
29 your application, because the build tools use a debug key with a known password so you do not have
30 to enter it every time you build. When you are ready to release the application to Google
31 Play, you must sign the application in release mode, using your own private key.</p>
33 <p>Fortunately, Eclipse or your Ant build script signs the application for you in debug mode
34 when you build your application. You can also easily setup Eclipse or your Ant build to sign your
35 application in release mode as well. For more information on signing applications, see <a href=
38 <p>The following diagram depicts the components involved in building and running an application:</p>
58 <li>The Android Asset Packaging Tool (aapt) takes your application resource files, such as the
77 <li>Finally, if the application is being signed in release mode, you must align the <code>.apk</code> with
78 the zipalign tool. Aligning the final <code>.apk</code> decreases memory usage when the application is
