Is dynamic delivery a must know now? I am thinking...

# android

[Nikola Milovic]

Is dynamic delivery a must know now? I am thinking of putting in the effort to get a good grasp on it, but I am not sure if it's a good idea to focus on that or just stay with the standard multi module approach.

[Casey Brooks]

I think it’s like a lot of these newer architecture components. If you can get it implemented early in the development of your app, you’re setting yourself up really well for long-term success, but is more difficult to add into an existing app using different architecture patterns/libraries. Dynamic delivery integrates very cleanly with the Navigation Component, and shouldn’t take too much more work to get setup than a standard multi-module app for a new project

[Nikola Milovic]

@Casey Brooks Oh that really does make a lot of sense. I guess it's a worthy investment. Thanks!

[Casey Brooks]

This repo is a good example of an app architected with the latest Jetpack components and Kotlin features, and is well-worth looking at. There’s a lot here which you may or may not need, so I use it more as a reference for individual features and high-level concepts https://github.com/VMadalin/android-modular-architecture

[Casey Brooks]

And here are the docs for integrating dynamic delivery with the Navigation Component. I haven’t actually gotten around to trying it for myself yet, but it looks very seamless https://developer.android.com/guide/navigation/navigation-dynamic

[Nikola Milovic]

❤️ Thank you!