Extract NavigationTrackingStrategy as separate module

[joshskeen]

Are you requesting automatic instrumentation for a framework or library? Please describe.
NA

Is your feature request related to a problem? Please describe.
Yes. We do not ship androidx.navigation with our project, nor do we want to.
Instead, it would be best if we could choose whether to include androidx.navigation as a dependency in our project by
using dd-sdk-android:rum.

Describe the solution you'd like
Extract NavigationTrackingStrategy to a separate, new module, that can be selectively included in a project. For projects that do not use androidx.navigation, they no longer needlessly include this dependency.

[0xnm]

Hello @joshskeen! Can we please share more details about your concern: is it a blocker for you at the current stage and what is the issue behind - is it final binary size / number of methods in the binary?

While NavigationTrackingStrategy can indeed be extracted into the dedicated package, there are still some parts of the code in the RUM module which are using classes from androidx.navigation for the internal needs.

[joshskeen]

Hi @0xnm. There are several reasons. Binary size is definitely one. The other is that our project in no way is using androidx.navigation and introducing androidx.navigation transitively is not desired. While it isn't blocking us, it would be more ideal if we had the option to exclude (and without breaking rum).

[0xnm]

Hello @joshskeen. Thanks for the details provided, we will discuss this possibility with the team.

Meanwhile, I would like to say that we are also publishing statistics on the transitive dependencies usage, and androidx.navigation group brings the following artifacts with relatively small footprint.