A modern programming language that makes developers happier.

kotlinlang

Hello there, I have some questions about nav_graph, hope anybody can help me. Thank's a lot.

Every activity should contain a navigation graph?

It is ok if I have just activities and I don't use a navigation graph?

If I have one host activity, how many fragments are ok to use for navigation? There is a stack that remains in memory and which I can overload?

When I need activities and when I need fragments?

&gt; Every activity should contain a navigation graph?
in short no. nav graph meant to fragment

&gt; It is ok if I have just activities and I don't use a navigation graph?
yes

&gt; If I have one host activity, how many fragments are ok to use for navigation?
as many as you want,

&gt; When I need activities and when I need fragments?
fragment kind of reusable component. (even though you can achieved same thing by using compound view or compose)

To the point, thank you. Thinking about your answers, I wonder about another question. If I want to navigate between two activities, I don't need to use a new navigation component and instead, I can navigate with Intent. This is true?

no needed a plan startactivity would work

Actually, you can use `activity` destinations to navigate to other activities: <https://developer.android.com/guide/navigation/navigation-create-destinations#create-activity|https://developer.android.com/guide/navigation/navigation-create-destinations#create-activity>

<@UJBPFB3SN> I didn’t know you could declare 3rd party app activities like that. Out of interest, how is the `android:label` argument used?