In traditional MVVM, what do you guys consider you...
# android-architecture
r
In traditional MVVM, what do you guys consider your model(ie your networking layer) ?
h
I consider everything after domain (inclusive)
o
To be specific, I consider my repository/useCase class and everything it encapsulates (ie DAO, webservices/networking etc)
👍🏻 1
☝️ 1
k
what is traditional MVVM, is it MVVM without clean architecture, D.I?
r
Without clean architecture. im guessing.
DI is fine
clean architecture is a architecture of its own
k
so in some cases, or some projects, we just need traditional MVVM?
r
I think MVVM, doesn't need clean architecture to be honest. The usecase model is cool and all , but its not needed to accomplish mvvm
DI. is just a good coding design principal to have regardless of the architecture
a
In MVVM the model is everything that isn't the UI, bit different definition than what most things mean when they say model