2019: Navigation Graph
The new Navigation Graph for developers is especially helpful to chain screen sequences, like tutorials inside your app.
The following is an extract of https://www.androidauthority.com/android-navigation-architecture-component-908660/
2018: Jetpack and AndroidX
Android is far from a finished platform and in 2018 progressed in the solution of the following challenges:
"What is the Navigation Architecture Component? Part of Android JetPack, the Navigation Architecture Component helps you visualize the different routes through your application and simplifies the process of implementing these routes, particularly when it comes to managing fragment transactions. To use the Navigation component, you’ll need to create a Navigation Graph, which is an XML file describing how your app’s Activities and fragments relate to each other..."
Get startet on https://developer.android.com/guide/navigation/navigation-getting-started
Tackling the challenge of supporting tens of thousand devices having a variety of different hardware. That means, making it easy for manufacturers to port new hardware to the platform. The new bundling mechanisms will separate code, that is unique to your app and the code, that is unique to your device, so Google can serve for each app bespoke libraries for each hardware over the Play Store. Separating modules, that can be installed by any hardware manufacturer, without any help from Google, from those, that want to license their device with Google's services. With AndroidX, the downward compatibility libraries (support libraries) are now separated from the Android SDK. Making developers want to use Google Services, instead of self made or third party's, so data is stored on Google's servers. With Jetpack, Google created a new container for high level convenience libraries on top of the Android SDK.
Read more here: https://stackoverflow.com/a/52002285/2477937