The pics at the beginning of this video really help to nail the point across: "Clean Architecture has many layers that need careful coordination and knowledge."
MVVM has changed since the date of this video. I prefer MVVM over MVP. So much simple,no interfaces hell, reactive and the most important thing: it doesn't hold a view reference. So if you do async tasks and when it finishes then call getView().loadResults() this might crash your app if the user already leaved the activity or fragment. Ofc this can be handled with an if != null condition but it is so ugly and boilerplate... What do you think?
No the app will not crash in that case you mentioned because when the activity gets destroyed the liveData does not "post" updates, it only does it when your activity is visible
The pics at the beginning of this video really help to nail the point across: "Clean Architecture has many layers that need careful coordination and knowledge."
Great and clear explanation
A skillful combination of theory and practice. Thanks!
Excellent presentation. Nicely done sir.
Would love to work with this guys, seems like a super nice dude
MVVM has changed since the date of this video. I prefer MVVM over MVP. So much simple,no interfaces hell, reactive and the most important thing: it doesn't hold a view reference.
So if you do async tasks and when it finishes then call getView().loadResults() this might crash your app if the user already leaved the activity or fragment.
Ofc this can be handled with an if != null condition but it is so ugly and boilerplate...
What do you think?
No the app will not crash in that case you mentioned because when the activity gets destroyed the liveData does not "post" updates, it only does it when your activity is visible