A modern programming language that makes developers happier.

kotlinlang

`Day40`
• Reviewed mvvm basics with some googling (<https://black-jin0427.tistory.com/270?category=727620|1>) (<https://medium.com/@amtechnovation/android-architecture-component-mvvm-part-1-a2e7cff07a76|2>) (<https://www.simplifiedcoding.net/android-viewmodel-using-retrofit/|3>)
    ◦ Actually I didn’t get why MVVM is so good but this explanation was good. (_“Now if one of our activity has some data on it fetched from server, but if for some reasons (for example orientation changes) the activity is recreated it will fetch the data from the server again. Fetching the same data from the server is a waste of resources. An efficient solution here is to separate the view data ownership from UI Controller logic.“)_
• Rough planning for tomorrow’s task
    ◦ should add dependencies for.. viewmodel? lifecycle? whatsoever
    ◦ should create _Repository class_ (use LiveData* *for observing response)
    ◦ should create _ViewModel class_ (Store &amp; manage UI-related data in a lifecycle conscious way. Allows data to survive configuration changes)
    ◦ It’s basically re-organizing what I’ve done till now. (And that is not easy..) I guess I should create a view model, pull off the parts of MainActivity into view model and etc.
`Self-Comment`
• Not much done today solely, but I know that this googling time will help myself tomorrow…
`Goals Tomorrow`
• Location api demo app - add distance checking feature.
    ◦ calculate distance in location callback
    ◦ create subject (maybe in boolean..?) -&gt; subscribe that subject -&gt; change textview according to that subject
• Refactoring into MVVM