How to use a nested navigation graph for a login flow?

WHAT THIS TESTS: This question tests your understanding of architectural patterns within the Android Navigation Component. The interviewer wants to see if you can go beyond simple screen-to-screen navigation and use tools like nested graphs to create modular, encapsulated, and reusable UI flows. It's a test of clean code and separation of concerns, not just API knowledge.

A GOOD ANSWER COVERS: A strong answer walks through three distinct steps and then explains the benefits. First, create a new navigation graph file, for example login_nav_graph.xml. This file defines the three destinations (Welcome, Email, Password), the actions between them, and sets its own start destination (app:startDestination="@id/welcome_screen"). Second, in your main navigation graph (main_nav_graph.xml), you embed this flow using an <include> tag: <include app:graph="@navigation/login_nav_graph" />. This makes the entire login flow a single destination in the main graph. Third, to start the flow, you navigate to the ID of the nested graph itself, not one of its screens: navController.navigate(R.id.login_nav_graph). The primary benefits are encapsulation (the main graph doesn't know or care about the internal screens of the login flow) and reusability (the same login flow can be triggered from multiple places in the app with one line of code).

COMMON WRONG ANSWERS: The most common mistake is describing the correct setup but then navigating incorrectly. A candidate who says navController.navigate(R.id.welcome_screen) from outside the login graph has missed the point. This creates a tight coupling and breaks encapsulation, as the calling code now needs to know the internal implementation detail of the login flow's starting screen. If the login flow changes to start on a phone number screen instead, all call sites break. A less severe red flag is just describing the screens and actions but failing to mention creating a separate, included XML file, which suggests a lack of practical experience.

LIKELY FOLLOW-UPS: Expect questions like: "How would you return a result, like 'login successful,' from the nested graph back to the previous screen?" (Answer: Use the SavedStateHandle of the previousBackStackEntry). Another is, "How does this concept relate to feature modules?" (Answer: A nested graph is the ideal way to define the navigation for a self-contained feature module, keeping its UI flow completely isolated from the main app module).

ONE CONCRETE EXAMPLE: Imagine your main graph has 20 destinations. A login flow adds 3 more. Without nesting, your main_nav_graph.xml now has 23 destinations, increasing its complexity. With nesting, the main graph has only 21 destinations (the original 20 plus a single login_nav_graph destination). The complexity of the login flow is neatly contained in its own file. This simplifies the main graph by nearly 10% and prevents another developer from accidentally creating an action that navigates from a settings screen directly into the middle of your login flow (e.g., to the password screen), which would likely crash the app.