Android Application Development Fundamentals

natural c everywhereing bedrock Quickview humanoid privacyings are composed of one or more operation fixingss (activities, processs, sum providers, and broadcast receivers) all(a)(prenominal) element per micturates a different role in the overall occupation behavior, and separately one bathroom be instigated individually (even by early(a) drills) The manifest file must declare all components in the application and should in whatsoever case declare all application requirements, such as the minimum indication of Android required and any hardware configurations required Non- jurisprudence application resources (images, strings, layout files, etc. should include alternatives for different craft configurations (such as different strings for different languages and different layouts for different screen sizes) In this document 1. act Components 1. Activating components 2. The Manifest File 1. Declaring components 2. Declaring application requirements 3. Applicati on Resources Android applications are written in the burnt umber programming language. The Android SDK tools compile the codealong with any selective information and resource filesinto an Android package, an instrument file with an . apk suffix. All the code in a single . pk file is considered to be one application and is the file that Android-powered devices usance to install the application. Once installed on a device, each Android application lives in its own security sandbox The Android operating scheme is a multi- exploiter Linux system in which each application is a different exploiter. By default, the system assigns each application a anomalous Linux user ID (the ID is used only by the system and is unknown to the application). The system sets permissions for all the files in an application so that only the user ID assigned to that application stool admission fee them. Each process has its own virtual(prenominal) machine (VM), so an applications code runs in isolat ion from other applications. By default, every application runs in its own Linux process. Android starts the process when any of the applications components aim to be executed, then shuts down the process when its no longer needed or when the system must recover memory for other applications. In this way, the Android system go fors the principle of least privilege. That is, each application, by default, has access only to the components that it requires to do its work and no more.This creates a very secure environment in which an application cigarette non access parts of the system for which it is non given permission. However, there are ways for an application to share data with other applications and for an application to access system services Its possible to arrange for two applications to share the same Linux user ID, in which carapace they are able to access each others files. To conserve system resources, applications with the same user ID can withal arrange to run in the same Linux process and share the same VM (the applications must also be signed with the same certificate). An application can request permission to access device data such as the users contacts, SMS contentednesss, the mountable storage (SD card), camera, Bluetooth, and more. All application permissions must be granted by the user at install time. That covers the basics regarding how an Android application exists within the system. The rest of this document introduces you to The core framework components that place your application. The manifest file in which you declare components and required device features for your application. Resources that are separate from the application code and allow your application to gracefully optimize its behavior for a variety of device configurations. Application Components Application components are the essential building blocks of an Android application. Each component is a different bakshis done which the system can enter your applica tion. Not all components are actual entry points for the user and just about depend on each other, but each one exists as its own entity and plays a particularized roleeach one is a unique building block that helps define your applications overall behavior. in that respect are four different types of application components. Each type serves a distinct purpose and has a distinct lifecycle that defines how the component is created and destroyed. Here are the four types of application components Activities An use represents a single screen with a user interface. For example, an email application might learn one occupation that shows a hark of new emails, another activity to compose an email, and another activity for reading emails. Although the activities work together to form a cohesive user experience in the email application, each one is independent of the others.As such, a different application can start any one of these activities (if the email application allows it). For ex ample, a camera application can start the activity in the email application that composes new mail, in order for the user to share a picture. An activity is utilize as a subclass of Activity and you can learn more about it in the Activities developer guide. Services A service is a component that runs in the ground to perform long-running operations or to perform work for remote processes.A service does not provide a user interface. For example, a service might play music in the background while the user is in a different application, or it might fetch data over the network without blocking user inter implement with an activity. Another component, such as an activity, can start the service and let it run or bind to it in order to interact with it. A service is utilise as a subclass of Service and you can learn more about it in the Services developer guide. gist providers A content provider manages a shared set of application data.You can store the data in the file system, an SQLi te database, on the web, or any other persistent storage location your application can access. Through the content provider, other applications can query or even modify the data (if the content provider allows it). For example, the Android system provides a content provider that manages the users contact information. As such, any application with the proper permissions can query part of the content provider (such as ContactsContract. Data) to read and bring out information about a particular person. guinea pig providers are also useful for reading and create verbally data that is private to your application and not shared. For example, the Note Pad sample application uses a content provider to save notes. A content provider is implemented as a subclass of ContentProvider and must implement a standard set of APIs that enable other applications to perform transactions. For more information, see the Content Providers developer guide. Broadcast receivers A broadcast receiver is a comp onent that responds to system-wide broadcast announcements.Many broadcasts originate from the systemfor example, a broadcast announcing that the screen has turned off, the battery is low, or a picture was stopd. Applications can also initiate broadcastsfor example, to let other applications know that some data has been downloaded to the device and is available for them to use. Although broadcast receivers dont pageant a user interface, they may create a status bar notification to alert the user when a broadcast event occurs. More commonly, though, a broadcast receiver is just a admission to other components and is intended to do a very minimal amount of work.For instance, it might initiate a service to perform some work based on the event. A broadcast receiver is implemented as a subclass of BroadcastReceiver and each broadcast is comported as an Intent object. For more information, see the BroadcastReceiver class. A unique aspect of the Android system be after is that any appl ication can start another applications component. For example, if you want the user to capture a photo with the device camera, theres probably another application that does that and your application can use it, preferably of developing an activity to capture a photo yourself.You dont need to incorporate or even middleman to the code from the camera application. Instead, you can simply start the activity in the camera application that captures a photo. When complete, the photo is even returned to your application so you can use it. To the user, it seems as if the camera is actually a part of your application. When the system starts a component, it starts the process for that application (if its not already running) and instantiates the classes needed for the component. For xample, if your application starts the activity in the camera application that captures a photo, that activity runs in the process that belongs to the camera application, not in your applications process. Therefo re, unlike applications on most other systems, Android applications dont have a single entry point (theres no main() function, for example). Because the system runs each application in a separate process with file permissions that restrain access to other applications, your application cannot directly activate a component from another application. The Android system, however, can.So, to activate a component in another application, you must deliver a message to the system that specifies your disembodied spirit to start a particular component. The system then activates the component for you. Activating Components Three of the four component typesactivities, services, and broadcast receiversare activated by an asynchronous message called an intent. Intents bind individual components to each other at runtime (you can think of them as the messengers that request an action from other components), whether the component belongs to your application or another.An intent is created with an I ntent object, which defines a message to activate each a specific component or a specific type of componentan intent can be either explicit or implicit, respectively. A unique aspect of the Android system design is that any application can start another applications component. For example, if you want the user to capture a photo with the device camera, theres probably another application that does that and your application can use it, instead of developing an activity to capture a photo yourself. You dont need to incorporate or even link to the code from the camera application.Instead, you can simply start the activity in the camera application that captures a photo. When complete, the photo is even returned to your application so you can use it. To the user, it seems as if the camera is actually a part of your application. When the system starts a component, it starts the process for that application (if its not already running) and instantiates the classes needed for the componen t. For example, if your application starts the activity in the camera application that captures a photo, that activity runs in the process that belongs to the camera pplication, not in your applications process. Therefore, unlike applications on most other systems, Android applications dont have a single entry point (theres no main() function, for example). Because the system runs each application in a separate process with file permissions that restrict access to other applications, your application cannot directly activate a component from another application. The Android system, however, can. So, to activate a component in another application, you must deliver a message to the system that specifies your intent to start a particular component.The system then activates the component for you. Activating Components Three of the four component typesactivities, services, and broadcast receiversare activated by an asynchronous message called an intent. Intents bind individual components to each other at runtime (you can think of them as the messengers that request an action from other components), whether the component belongs to your application or another. An intent is created with an Intent object, which defines a message to activate either a specific component or a specific type of componentan intent can be either explicit or implicit, respectively.