[FIXED] What is the difference between using Safe Args for screen transitions and not using them?

Issue

Safe Args

I was referencing the JetPack Navigation Component related documentation to create a bottom navigation for screen transitions.

But in that link it says:

• The recommended way to navigate between destinations is to use the Safe Args Gradle plugin.
• Safe Args is recommended both for navigating as well as passing data between destinations.

After seeing this, I have a few questions.

Is there a performance difference between just using the navaigation component and using safe args?

Of course, safe args even has the ability to pass data between screens. But apart from this, is there any difference only in terms of screen transitions (navigation)?

Solution

Safe Args just generates code that you can write yourself, following the guide to navigating by ID and manually passing a Bundle of arguments - it has no effect on the performance of your app at runtime or how screen transitions work.

Answered By - ianhanniballake
Answer Checked By - Candace Johnson (JavaFixing Volunteer)