Hey guys, i was wondering why we can't inject the Viewmodel directly, but instead we've to inject a factory. Which ate the benefits came from this practice?

Why can't you inject view model directly? I do it all the time

If you inject ViewModel then it will be recreated on every configuration change

Hmm i get it. But we had a problem few days ago with it. We were testing a Video feature and the tester rotated the screen, this action recreated the VM. We tested binding a scope in it, but same problem

I don't think it's recreated necessarily. It depends on how you inject the vm

Koin better than Dagger hahah. I'm joking guys, please do not kill me 😞 We were using Dagger by the way

we inject the factory via dagger and then ViewModelProviders does the rest

Hmm thanks @Matej Drobnič and @LeoColman. One last doubt, do you have an example how do you implement this factory? The way that we're doing the Factory is being recreated every time that he is injected. We're using this tutorial as guide: https://android.jlelse.eu/android-less-dagger-boilerplate-code-for-viewmodel-creation-9fec91a27bf3

If you are using this tutorial, then factory is not recreated every time since it's

@Singleton

Hmm, we're implementing the second way. I'm going to discuss the first way with my team and consider the tradeoff. Thanks @Matej Drobnič

We are actually doing it the second way too

Hmm, we're considering to use Lazy initialization to solve this kind of problem.

where would you put the lazy?

Hmm one point to consider. We were thinking in fragment case, but we can retrieve using by viewModels. Howsoever we are going to use as described in tutorial.

I think you are prematurely optimizing this. It's one allocation per activity creation, it's not big enough deal to warrant such hacks.

Probably, thanks for the feedback 😁