Jawaharlal Nehru Technological University Hyderabad MCA 2018 ANDROID APPLICATION DEVELOPMENT Previous Question Paper (January - 2018 - R15)

Android applications are primarily categorized based on their architecture and the technology stack used to build them. The main types are:

• Native Applications: These are developed using the Android SDK, primarily with Java or Kotlin. They have direct access to device hardware and APIs, offering the highest performance and best user experience, but they are platform-specific.
• Web Applications: These are essentially mobile-optimized websites accessed through a browser. They are platform-independent and easy to update, but they lack access to device-specific features like the camera or sensors and rely heavily on internet connectivity.
• Hybrid Applications: These combine elements of both native and web applications. They are built using web technologies like HTML, CSS, and JavaScript and wrapped in a native container (using frameworks like Cordova or Ionic). This allows them to run on multiple platforms while accessing some native device features.
• Progressive Web Apps (PWAs): These are web applications that provide a native-like experience, including offline capabilities via service workers and the ability to be added to the home screen, bridging the gap between web and native apps.

A fragment in Android has a lifecycle that is closely tied to its host Activity. When the host Activity is paused, all fragments within it are also paused, and when the Activity is destroyed, all fragments are destroyed. The lifecycle methods are as follows:

• onAttach(): Called when the fragment is first associated with its host Activity.
• onCreate(): Called to perform initial creation of the fragment.
• onCreateView(): Called to create and return the view hierarchy associated with the fragment.
• onActivityCreated(): Called when the host Activity's onCreate() method has completed.
• onStart(): Called when the fragment becomes visible to the user.
• onResume(): Called when the fragment is active and the user can interact with it.
• onPause(): Called when the user is leaving the fragment, though it may still be visible.
• onStop(): Called when the fragment is no longer visible.
• onDestroyView(): Called when the view hierarchy associated with the fragment is being removed.
• onDestroy(): Called to do final cleanup of the fragment's state.
• onDetach(): Called when the fragment is being disassociated from the Activity.