Android Application Fundamentals

Unlike desktop apps which have a single entry point and run as a single, monolithic process. Android applications have much more complex structure. They are built using multiple app components.

The complete android code is packaged into a single file called APK (an Android Package).

Languages supported: Java, Kotlin and C++.

Important features of an Android app:
  • Android OS is based on the Linux operating system, a multi-user OS, where every app is a different user represented by a unique Linux user ID. (Exception: It is possible to have apps with the same user Linux user ID i.e everything between these apps can be shared)
  • Each app has its own linux “process” which is hosted on its private Virtual machine VM.
  • System controls the “process” i.e starting and stopping of the process.
  • To access any special device data, the app has to request it from the system.

Building blocks of Android app
  • AndroidManifest file
  • Core Framework components - Activities, Services, Broadcast receivers, Content Providers
  • Resources (includes texts, images, animations, etc)

Tools for Android development
  • Android Studio (Preferred)
  • IntelliJ
  • Eclipse


Don’t worry if you don’t understand, I had the same experience for the very first time ;-). Keep following us to understand everything about Android.

Resources: https://developer.android.com/guide/components/fundamentals?hl=en
Location: India

Comments

Post a Comment

Popular posts from this blog

Fragment Lifecycle

Image
Just like Activities, Fragments also manages its own lifecycle. Though these lifecycle callbacks are a bit different than activity’s callbacks they exist for the similar reason as that of activity’s callback. Fragment manages two different lifecycles. One for the fragment instance and other for the view shown in the fragment. Having different lifecycle for fragment’s view is useful in the situations where the work should be performed only when view exists. Points to note: Fragment lifecycle call-backs are similar to Activity’s lifecycle. More important they are dependent on Activity’ state. Fragment manages 2 different lifecycles - Instance and View. Fragment callbacks are: onAttach, onCreate, onCreateView, onViewCreated, onViewStateRestored, onStart, onResume, onPause, onStop, onDestroyView, onDestroy, onDetach Fragment state is saved before onStop for API level less than 28 while in API level 28 and above its saved after onStop method. i.e In API level 28 or above devices its safe to...
Read more

AndroidManifest

Image
One of the most important components of your project. Stays in the root directory of the project source. This is used to describe essential information about the app to Android Build Tools, Android OS and Google Play. Most important things for which AndroidManifest is used: To declare app’s package name: Used by Android build tools to map code entities and to map it with applicationId defined in build.gradle To declare different app components: Include all activities, services, broadcast receivers, and content providers To declare app permissions: Helps in accessing specific restricted by System or other apps. To declare hardware and software features: Used to decide which device can app be installed into Package name and application ID Example <?xml version="1.0" encoding="utf-8"?>        <manifest            xmlns:android="http://schemas.android.com/apk/res/android"           package="co...
Read more

Activity Lifecycle

Image
To let Android System interact with Application different methods are defined by the system which communicate different states of the activity to the application. Those methods/states are called as Lifecycle Callbacks. Activity can go into different combination of these states. In the code each callback is used to understand the state in which the activity is in and accordingly perform different operations. Let’s discuss different activity callbacks and what each of them represent in real life scenarios. You will find each section explained with the 3 labels. Let us see what each label represents: Called: It will tell you when is this method called. Implement: What should be implemented in this method. State: What is the state of activity from user's perspective.                         onCreate() Called: This is the first callback received in Activity which is called as soon as the system creates the Activity. Implement: Used ...
Read more