Lines Matching full:your
26 your code—along with any data and resource files—into an APK: an <i>Android package</i>,
70 <li>The core framework components that define your app.</li>
71 <li>The manifest file in which you declare components and required device features for your
73 <li>Resources that are separate from the app code and allow your app to
82 component is a different point through which the system can enter your app. Not all
85 helps define your app's overall behavior.</p>
128 the file system, an SQLite database, on the web, or any other persistent storage location your
135 <p>Content providers are also useful for reading and writing data that is private to your
172 photo with the device camera, there's probably another app that does that and your
176 photo. When complete, the photo is even returned to your app so you can use it. To the user,
177 it seems as if the camera is actually a part of your app.</p>
180 already running) and instantiates the classes needed for the component. For example, if your
182 runs in the process that belongs to the camera app, not in your app's process.
187 restrict access to other apps, your app cannot directly activate a component from
189 another app, you must deliver a message to the system that specifies your <em>intent</em> to
199 to your app or another.</p>
257 file). Your app must declare all its components in this file, which must be at the root of
320 <p>Activities, services, and content providers that you include in your source but do not declare
327 <p>For more about how to structure the manifest file for your app, see <a
348 <p>When you declare an activity in your app's manifest, you can optionally include
350 from other apps. You can declare an intent filter for your component by
373 startActivity()}, the system may start your activity so the user can draft and send an
385 same features and capabilities. In order to prevent your app from being installed on devices
386 that lack features needed by your app, it's important that you clearly define a profile for
387 the types of devices your app supports by declaring device and software requirements in your
392 <p>For example, if your app requires a camera and uses APIs introduced in Android 2.1 (<a
394 you should declare these as requirements in your manifest file like this:</p>
406 Android version <em>lower</em> than 2.1 cannot install your app from Google Play.</p>
408 <p>However, you can also declare that your app uses the camera, but does not
409 <em>require</em> it. In that case, your app must set the <a href=
414 <p>More information about how you can manage your app's compatibility with different devices
426 to update various characteristics of your app without modifying code and—by providing
427 sets of alternative resources—enables you to optimize your app for a variety of
430 <p>For every resource that you include in your Android project, the SDK build tools define a unique
431 integer ID, which you can use to reference the resource from your app code or from
432 other resources defined in XML. For example, if your app contains an image file named {@code
434 named {@code R.drawable.logo}, which you can use to reference the image and insert it in your
437 <p>One of the most important aspects of providing resources separate from your source code
443 to your UI.</p>
445 <p>Android supports many different <em>qualifiers</em> for your alternative resources. The
446 qualifier is a short string that you include in the name of your resource directories in order to
448 example, you should often create different layouts for your activities, depending on the
456 <p>For more about the different kinds of resources you can include in your application and how to
469 activate app components, such as activities and services, and how to make your app components
473 which provides a distinct screen in your application with a user interface.</dd>
488 to how you can optimize your app for each device or restrict your app's availability
493 system that requires the user's consent for your app to use those APIs.</dd>
