Task Stack & Back Navigation

Android's navigation model is heavily based on the concept of Tasks. A Task is simply a cohesive collection of Activities that users interact with when performing a certain job. These Activities are arranged in a stack (the "Back Stack") in the exact order in which each Activity is opened.

The Back Stack Mechanics

If you open the Email app (Activity A), click "Compose" (Activity B), and then click "Attach Photo" (which opens the Gallery app, Activity C), all three Activities exist in the same visual Task Stack, even though they cross application boundaries.

When the user taps the Back button, the top Activity is physically popped off the stack and destroyed, revealing the previous Activity beneath it.

Intent Flags (FLAG_ACTIVITY_*)

Developers can radically manipulate this stack at runtime by appending flags to the Intent used to start an Activity.

• FLAG_ACTIVITY_NEW_TASK: Starts the Activity in a brand new Task. This is heavily used by background Services or Notifications that need to launch a UI without attaching to an existing, unrelated flow.
• FLAG_ACTIVITY_CLEAR_TOP: If the Activity being started is already running in the current task, all Activities on top of it are instantly destroyed, bringing the target Activity to the top.
• FLAG_ACTIVITY_NO_HISTORY: The Activity is started normally, but it is not kept in the back stack. As soon as the user navigates away, it is permanently destroyed.

// Example of clearing the back stack when the user logs out
Intent intent = new Intent(this, LoginActivity.class);
intent.addFlags(Intent.FLAG_ACTIVITY_NEW_TASK | Intent.FLAG_ACTIVITY_CLEAR_TASK);
startActivity(intent);

Predictive Back Navigation (Android 13+)

Historically, apps intercepted the back button using onBackPressed(). This created a massive UX problem: the operating system had no idea what the app was going to do when the back button was pressed. It could pop a fragment, close a drawer, or exit the app entirely.

In Android 13, Google introduced Predictive Back Navigation. This system requires apps to register their back navigation logic ahead of time using the OnBackPressedDispatcher.

Because the OS now knows exactly what the back action will do before the user finishes swiping the edge of the screen, it can show a smooth, fluid animation predicting the outcome (e.g., shrinking the current window to reveal the home screen wallpaper beneath it).

// Modern back press interception using the Dispatcher
getOnBackPressedDispatcher().addCallback(this, new OnBackPressedCallback(true) {
    @Override
    public void handleOnBackPressed() {
        // Handle custom back logic, like closing a custom drawer
        closeCustomDrawer();
    }
});