JNTU MCA ANDROID APPLICATION DEVELOPMENT Previous Question Paper (September/October - 2022 - R15)

Android applications are built using four primary components that serve as the building blocks for the application's functionality:

• Activities: Represent a single screen with a user interface. They handle user interactions and manage the visual layout of the application.
• Services: Components that run in the background to perform long-running operations or remote processes without a user interface. They continue to run even if the user switches to another application.
• Broadcast Receivers: Components that enable the application to listen for system-wide broadcast announcements (e.g., battery low, screen turned off) and respond accordingly.
• Content Providers: Manage access to a structured set of data. They allow an application to share its private data with other applications or retrieve data from other providers in a secure manner.

Additionally, the Intent mechanism acts as the messaging object that facilitates communication between these components, while the AndroidManifest.xml file acts as the essential configuration file declaring these components to the Android system.

The Activity lifecycle is managed by the Android system through a series of callback methods that track the state of an activity as it transitions from creation to destruction. The key lifecycle states are:

• onCreate(): Called when the activity is first created. This is where static setup such as creating views and binding data to lists occurs.
• onStart(): Called when the activity becomes visible to the user.
• onResume(): Called when the activity starts interacting with the user. The activity is now at the top of the activity stack.
• onPause(): Called when the system is about to start or resume another activity. This is used to commit unsaved changes or stop animations.
• onStop(): Called when the activity is no longer visible to the user.
• onRestart(): Called after the activity has been stopped, prior to it being started again.
• onDestroy(): The final call received before the activity is destroyed, either because the user finished the activity or the system is reclaiming resources.

Understanding these transitions is critical for managing system resources and ensuring the application state is saved correctly when the user navigates away or the device configuration changes.