Skip to main content

Android App Components Activities, Fragments, and Intents


Activities :
=========
Activity is one of the most important component for any android app

Activities are the User Interface (UI) screens which user see.
It is similar to the main() function in different programming languages.

Its is the main entry point for user interaction.
You can have multiple activities in your app.
All your activities must be declared in the manifest file, with their attributes.

Every activity has different functions throughout its life, onCreate(), onStart(), onResume(), onPause(), onStop(), onRestart(), onDestroy().

To create activity we can use two methods either we create class file and xml file and include the class in manifest file. ---- method 1 

or we can create activity using empty activity like this.. --- method 2

note:- for using method 1 we must include our class file in manifest file  otherwise it will show error in logcat.

okay now let us see the activity life cycle.
let us program the life cycle of activity in our project.

okay function is coded let us see the result.

when our app is launched the method which were invoked are:-

- on create
- 0n start
- on resume

okay now when we press back button the method which were invoked are:-

-on pause
-on stop
-on destroy
 okay now let us start to learn fragments


Android Activity Lifecycle is controlled by 7 techniques for android.app.Activity class. The android Activity is the subclass of ContextThemeWrapper class.







You should always call up to your superclass when implementing these methods.


public class Activity extends ApplicationContext {

     protected void onCreate(Bundle savedInstanceState);

     protected void onStart();

     protected void onRestart();

     protected void onResume();

     protected void onPause();

     protected void onStop();

     protected void onDestroy();

 }


Activity Lifecycle

■ Activities in the foreground are running (onResume)
■ If something transparent obscurs the activity it is paused (onPause)
■ If you can’t see the activity it is stopped. (onStop)
■ If it is garbage collected (onDestroy)
Android Activity
Life Cycle
  •  Lifetime:
    • onCreate() to
    •  onDestroy()
  •  Visible when:
    •  onStart() to
    •  onStop()
  •  Foreground
    •  onResume to
    •  onPause()

 Android Activity Lifecycle Example

In this example, we are displaying the content on the logcat.
File: MainActivity.java
package com.example.activitylifecycle;  
import android.os.Bundle;  
import android.app.Activity;  
import android.util.Log;  
import android.view.Menu;  
public class MainActivity extends Activity {  
    @Override  
    protected void onCreate(Bundle savedInstanceState) {  
        super.onCreate(savedInstanceState);  
        setContentView(R.layout.activity_main);  
        Log.d("lifecycle","onCreate invoked");  
    }  
    @Override  
    protected void onStart() {  
        super.onStart();  
         Log.d("lifecycle","onStart invoked");  
    }  
    @Override  
    protected void onResume() {  
        super.onResume();  
         Log.d("lifecycle","onResume invoked");  
    }  
    @Override  
    protected void onPause() {  
        super.onPause();  
         Log.d("lifecycle","onPause invoked");  
    }  
    @Override  
    protected void onStop() {  
        super.onStop();  
         Log.d("lifecycle","onStop invoked");  
    }  
       @Override  
    protected void onRestart() {  
        super.onRestart();  
         Log.d("lifecycle","onRestart invoked");  
    }     
    @Override  
    protected void onDestroy() {  
        super.onDestroy();  
         Log.d("lifecycle","onDestroy invoked");  
    }  

}



Fragments :
==========

In most of the applications these days, fragments are largely used.
As there are a lot of android devices with different resolutions, its a bit tough to handle all of those, that’s where fragments come handy. We can combine 2 or more fragments and show them in an activity.

A Fragment is a component that is used by an activity.
Even though it is used by an activity, it has its own lifecycle.







Intents :
===========
Intent is one of the most important and most used app component of an android application.

Using Intents, you call to other app components or to other activity or also call other applications on your phone.

Intents are two types:

Explicit Intents where you call another activity or something with a class name. For instance, you can call another activity when some action happened in one activity. So you here explicitly specifies which activity to call.


Implicit Intents where we do not specify a class name but specify some sort of action, which can be handled by some other inbuilt apps or some other apps. For instance, you may want to open a camera, showing a map, sending emails etc. Here you don’t directly call camera app or map app, you will just specify the action.

Intent i = new Intent(FirstActivity.this, SecondActivity.class) ;

startActivity(i);




















Comments

Popular posts from this blog

BottomNavigationView

In this tutorial we will learn, how to add a bottom navigation to your activity and use it to switch between different fragments. We will fill our BottomNavigationView with 3 menu items and then check which item was selected with the OnNavigationItemSelectedListener interface and a switch statement. We will then create the appropriate fragment and display it in a FrameLayout with help of the getSupportFragmentManager, beginTransaction and replace methods. Link & Dependencies:- developer.android.com/topic/libraries/support-library/packages.html#design Add a directory in res folder and name it as menu. After adding menu folder in res folder add a xml file and name it bottom_navigation.xml. <?xml version="1.0" encoding="utf-8"?> <menu xmlns:android="http://schemas.android.com/apk/res/android"> <item android:id="@+id/nav_home" android:icon="@drawable/ic_home_black_24dp" android:titl...

UPI Payment Integration Android

                                 In this tutorial we will learn how to integrate upi payment gateway in our app. In gradle file add this dependency:- // EasyUpiPayment Library implementation 'com.shreyaspatil:EasyUpiPayment:3.0.0' Note:- Minimum Sdk must not be below 19 In MainActivity.java class file add these lines of codes:- package com.deftskill.upiintegration; import androidx.appcompat.app.AppCompatActivity; import android.os.Bundle; import android.view.View; import android.widget.Toast; import com.shreyaspatil.easyupipayment.EasyUpiPayment; import com.shreyaspatil.easyupipayment.listener.PaymentStatusListener; import com.shreyaspatil.easyupipayment.model.PaymentApp; import com.shreyaspatil.easyupipayment.model.TransactionDetails; import java.util.ArrayList; public class MainActivity extends AppCompatActivity implements PaymentStatusListener {     private EasyUpiPayment easyUpiPayment; ...

Clean Code in 2026: Why "Good Enough" Isn't Good Enough Anymore

Let’s be honest: we’ve all been there. You open a file you wrote six months ago, squint at the screen, and think, "Who wrote this, and what on earth were they trying to do?" In 2026, the stakes for writing Clean Code are higher than ever. With AI generating half our boilerplate and systems becoming more distributed by the second, "messy" code isn't just an eyesore—it’s a massive technical liability. Clean code isn't about being a perfectionist; it’s about being a professional who respects their future self (and their teammates). What Exactly is Clean Code? It’s not just about pretty indentation or using a trendy linter. Clean code is a philosophy. It’s the art of writing software that is readable, resilient, and easy to change. If your code is "clever" but takes three senior engineers an hour to decipher, it isn't clean. Clean code should read like well-written prose—it tells a story about what the system is doing, without the plot holes. W...