TranslatorService | lightweight library that uses Cognitive Translator Service | Speech library

I have done something similar in one of my projects. You just need to move your translation code one level above. i.e.

Make a component called translation component which wraps all the components and put your logic in it. That way it will be loaded only once through the application life cycle.

You route config should then look something as follows:

You shouldn't manually touch dagger module implementations. Lets say you want to inject to a class called A. Add method called something like void inject(A a); to your Subcomponent.

And then inside that A class, invoke

DaggerDataServiceComponent.builder() .build() .translatorComponent(new TranslatorModule()) .inject(this);

it will inject to a field annotated with @Inject if type of that field is provided by your Dagger modules.

This will get you idea of Dagger. When you understand this, implement logic to your Components because in my example Subcomponent is pointless because both Components are created every time.