When building modules in the app that will work li...

# android

[Yacov Rosenberg]

When building modules in the app that will work like Libraries and maybe will be used in more than one app.
Do you guys consider a good or bad practice to use a DI framework like coin in those modules?

[Zun]

In my UI- modules I do. I can't really place them elsewhere. In my other modules such as services / shared I don't. Main reason being is that I reuse the services elsewhere in a context that isn't android… so hilt doesn't make sense anyway

[Yacov Rosenberg]

I know that with Koin you can create a isolated context, so you can use in the libraries, I just wanted to know if this is a good practice, if maybe there is some article about it.

[Javier]

Consumers want to have as few dependencies as possible, so I would avoid it. If you are the only one which is going to consume those libraries, up to you

[Yacov Rosenberg]

I see, in our case, is some modules for our company apps.

[marlonlom]

if the modules are not related to some dynamic feature modules, you could export them as libraries, but, in that case, think of move the modules to another project ( i dont know if gradle supports generating multiple artefacts in a single project with multiple modules)

[marlonlom]

@Yacov Rosenberg do you have a separated component/library internal repository for deploying the modules/libraries that are shared?

[Yacov Rosenberg]

I have separated repositories for each module, and also I have a solid pipeline that build those modules to some artifactory.