I am working on a new app and I am planning to use...

# android-architecture

[Sushobh]

I am working on a new app and I am planning to use dagger. I am specifically interested to know your thoughts on dagger components.
1. Should I create components based on the lifecycle of their use case. For example, a component for all objects when the user is logged in? I am confused about how to structure my components.
2. Where should components be stored? For example, for the user logged in component, where do I store the component?
3. How do I dispose of components? Is setting it to null enough?
I am having a hard time, how many components to create and for what use cases. Please assist. If there is a better channel for this question let me know.

[aishwaryabhishek3]

Which usecase is stopping you from using hilt ? is it because you want components feature-wise and not layer-wise ?

[Sushobh]

I am not interested in using hilt.

[aishwaryabhishek3]

Ideally you would have 1 component per activity and not feature . you can have feature wise components which are marked as dependencies on your activity components (marked as dependencies in ActvityComponent , not by using SubComponents ).

[Sushobh]

Thanks. I was planning on creating activity subcomponents whose parent will an app component, providing app wide dependencies.

[Sushobh]

What do you think?

[aishwaryabhishek3]

You will have issues modularizing the app then if you use subcomponents

[Sushobh]

Why would that be the case?

[aishwaryabhishek3]

Subcomponents keeps the components coupled

[aishwaryabhishek3]

https://stackoverflow.com/questions/29587130/dagger-2-subcomponents-vs-component-dependencies

[Sushobh]

Ok. " feature wise components which are marked as dependencies on your activity components" is this accomplished by using creating Dagger modules?

[Sushobh]

No prob. I checked the so thread, they have the info. Thanks

[aishwaryabhishek3]

So lets say you have onboarding feature , common classes like your APIs DBs etc specefic to this feature will be provided by a OnboardingComponent (this component has its own modules which provide your APIs DBs etc) , Now lets say in OnboardingFeature you have SignUpActivity , SignUpComponent will have dependency on OnboardingComponent to provide all the APIs DBs .

[Sushobh]

So you are saying having a component dependency will support modularization while subcomponents will prevent it right?

[aishwaryabhishek3]

Yes

[Sushobh]

So if i have two feature modules, A and B. B depending on A, how will it work?

[aishwaryabhishek3]

Hilt is the best if you want to modularize , but keeping feature wise components is a pain

[aishwaryabhishek3]

feature modules should not depend on each other

[Sushobh]

Let say A is a platform module while B is a feature module

[Sushobh]

I would want networking apis part of A in B. Should i use component dependecy here? Will it work

[aishwaryabhishek3]

Yes , will work fine

[aishwaryabhishek3]

in B’s component you add dependency for A’s component

[Sushobh]

Any resources to learn this in more detail?

[Sushobh]

Most posts online are rudimentary, so not very helpful

[aishwaryabhishek3]

I have learned most of this by looking at all my companies code only so I do not have resource for you unfortunately

[Sushobh]

Cool, thanks for your help

[aishwaryabhishek3]

I would still say try out hilt , it makes lot of stuff easier

[aishwaryabhishek3]

you can have a look at this if it works for you : https://developer.android.com/training/dependency-injection/dagger-multi-module