Depends on app Creates a separate apk Allows you to use Dynamic Delivery Easier to do at the beginning Build time impact affects especially the new modules Library App depends on it Only one apk No Dynamic Delivery Complicated refactor Build time impact affects especially the old modules
containing only the manifest. You will also need a core module containing the component for the dependencies used in different features. Easy to do when you start a new app, difficult and time consuming when you have an ongoing project.
same and act as a base module. The refactor is easier because the new module will implement the app module, so it will have access to all the classes inside it. You can keep them as included in the App Bundle and decided in the future to use dynamic delivery. Navigation between modules is more tricky.
but it might be better to avoid it. Avoid also @Subcomponent to improve build time performances. The generated code can be referenced in the app module, but there’s no reason to (and the app module should be empty!)
@Subcomponent and Dagger Android Generated code cannot be referenced in the base module The base module should contain as little as possible code Library Can use @Subcomponent (but better not to) and Dagger Android Generated code can be referenced in the base module (but shouldn’t) The app module should be empty