'Should every view have a ViewModel?
I've been developing in Android for a few months back and I am currently learning and implementing MVVM arquitecture, but the info related in Internet confuses me a little bit.
Google recommend to have only one viewModel per view, other resources says that is not necessarily for all views....
In my current project I have a view where i don't know if is needed or not, main activity has a RecyclerView with clickable items (this activity has his viewModel) and when user clicks on one item it takes him to a details page populated using Bundle (I think until this point a viewmodel is not needed, or it is?), but as an update I want to implement a BarcodeScanner button in main activity and as result it will make a GET to an API and populate the same view (details with de result of the call).
I this case, does my details view needs a viewModel?
Any info is appreciated.
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|