ViewModels & Configuration Changes - Android Basics 2023 

I do not know how anyone can learn Android coding without these videos, thank you so much.

Perfect as usual, Philipp! I wish you a lot more subscribers! Keep sharing your knowledge please in a clear and understandable way! Danke😉

Thank you Philipp for all your work. You are really an inspiration for me as Android Developer and I've learned so much thanks to you 😊

You're the goat i was having difficult in state management and your video clarify my mind, thanks

It's a very clear and detailed explanation as usual. Thank you!

Thanks it really cleared my doubt i was confused but now its clear.

Perfect explanation, thanks Philipp

I really liked that you explained in such great detail. When you don't use Dagger-Hilt, everything becomes clearer despite the boilerplate code. I had a lot of memory leak issues with Context 🎉

Very clearly explained. Thank you very much

This is at least 100% better then developer.android blog. Excellent.

You're making me learn compose in a mere couple of weeks. Why is noone else coming up with these essential videos? These solutions are so simple yet noone will mention them in a documentation

I just want to thank you, I am learning a lot from your videos! Cheers!

Videos like this are necessary for developers in any level, sometime you need to know how a component really works and what its purpose is, in order to avoid bugs, performance issues and leaks.

In depth explanation thank you so much Philipp

Great series! Maybe you could include things like - this could be asked in an android interview and share some trick questions :)

thx a lot for this basics video!

I have learnt a lot of languages and watched a lot of videos but yours are next level, whatever I need you have a video and exactly at the level I need and perfectly explained.

Thx for this great video.

User: turns the screen Activity: nooo! I don't want to die!!!

Is Google making all this unnecessarily complex? Newbie here

a big thanks to all your efforts one day i will surely become a great android developer only because of you ❤

Please make a video on how to make usecases for a complex app having many features This series is gonna be very useful

thanks for great content 🙏🙏❤ ,

you are the best bro

❤ good one

Hi, Philipp! Thank you so much 🙏 I would like to ask you what is written on your T-shirt in this video? Thanks

sehr schön 👍aka very nice

Awesome

Thanks, you explain kotlin compose very well. There is little information at an advanced level in the Russian-speaking segment.

In order to get data from Broacastreceiver to compose functions should we use this aproach?

Perfectly explained, I have been struggling the idea of mvvm and how it works, but now WOW. Thanks man very appreciated.

if model layer is exposing a list of objects with epoch time, is it good to convert all of them to new object by parsing them to corresponding strings?.. If I follow this approach, I would have 4 data classes that represents the same data: dto, entity, model that repository exposes and model that is parsed for the view. Should I follow this approach?

Is this telling us we need to use ViewModel or just what it can be used for if we want to use it? Is it the only way to handle configuration changes or is it an alternative to APIs like rememberSaveable?

Philipp the 🐏 in Android tutorials 🔥

Hello, which theme are you using, it looks very nice ?

The GOAT ♥

thanks

thank you.. I was stuck and didnt know whats wrong,, turned out i needed to sync it..

Hi sir, thanks for your helpful series. But I got one more question about the differences between MVP and MVVM, can you help me figure it out. Thankyou

Can you please explain the reason of getting dublicate class error? thanks

👌👌

You are great! I learn so much from you and still improving myself. I have a small request from you, Please create a playlist/single video for MVVM architecture with Retrofit API call. Also please make this with Activity & XML (don't use Jetpack Compose).

Hello, can you make a wideo with istalation of Android studio and show how to config it, and what emulator you use ?

Congratulations Philipp. A simple question, can I work with WorkManager inside the ViewModel class?

It's a cool explanation of MVVM, but what a pity I don't have enough money to buy your premium courses...

~15:00 the crash due to adding a parameter... this type of issue is why I am having so much difficulty learning how to use Android... half the time, there is no obvious reason why a crash occurs, and the log often gives the wrong line number... is there an easy way to debug such problems?

Thank you bro...was waiting on this to start using KMM...will this work for compose ios if I share the ui and the logics ?

Hi Philipp, Can You Also Make a Video About Repository And Data Classes? Would Be very Helpful

What emulator do you use?

sir, how to know that meetups are going on and how to join them and joining them is worth it ?

安卓现在的框架给我的感觉很庞杂，有时候不知从何入手。但是这个视频讲解了ViewModel是什么，怎样手动构造，这样只要懂基本的知识就能使用，拨开了框架的神秘面纱。

cool bro

Kotlin, OOP, Android... the more I learn, the more I am completely stunned at how ludicroulsy complex it is... so many different ways to overcome the global vs local variable problem (aka client-server where do I put the code/data problem)... Synthetics, deprecated, no longer supported, then findViewById/binding, now Jetpack Compose... what next?

Hi! Is there any compose view for single row calendar view? With date highlight?

10:25 i just want to say out loud that the whole confusing configuration change hack since android OS 1.0 is a ridiculous hack and should have been addressed years ago What a sloppy mess

Hi, I never know how to import viewModel. Using by viewmodels() is the newest way? What os the best way to use viewModel with XML. Do you have tutorials?

Hey! can you share your green wallpaper?

If I find my first job, I will donate you to show my love❤

i don't understand why not to make UI actions update the model itself and vice versa.

Should we use only one viewModel in whole app or create different viewModels for different purposes?

This video is pretty much Android development in a nutshell. Part 1: The motivation behind MVVM; how it just totally simplifies the process of making changes on the UI, and keeping it synced with the data model that's being represented. Easy to implement, easy to understand, there's a good deal of boilerplate but it's easy to ignore. Part 2: There's a small Gotcha! When you rotate the device, the screen re-renders and your viewmodel gets destroyed & reinitialized. Not a problem though, Android gives you a solution for this, you just need your viewmodel to extend the androidx ViewModel class and it will persist the viewmodel's state during screen configuration changes for you. Part 3: So here's a common scenario where you're in a sub-component that doesn't know which activity is calling it. You'll need to do that in a specific Android way, but the android package for doing it isn't included by default so you'll need to update the gradle dependencies (that's the build.gradle (:app) one, not the other build.grade top-level file). Doing this (or maybe for reasons totally unrelated?) sometimes causes a "duplicate class" error message to appear that, thankfully someone has tracked as being an issue with the latest kotlin.android plugin (in build.gradle (:project)), so just downgrade to an older and more stable version of that; and for reasons only about 5 people understand you also need to update your composeOptions (build.gradle (:app)) to a newer version; and then your project builds again! But it's a hollow victory, because now you're left with this sense of unease and uncertainty over whether it will work as prescribed when you actually do try to implement it in a subcomponent instead of MainActivity; that maybe there's an edge case related to using this same component from different intents, or on different devices, or with different versions of Jetpack Compose or Android. Or that maybe this will break the project in the future; or that you'll be forced to continue using this older version of kotlin.android and miss out on future features. Your code works now, but the feeling of unease over your software will never leave now. And then also here's a common scenario where you might want to use constructor arguments for your Android-specific ViewModel that you are required to use. You'll need to create a whole ViewModel Factory from the ViewModelProvider and override the create method with your own way of creating ViewModels and then create the ViewModel using that; all that even if you only want one instance of your ViewModel. Some developers just put the entire Android project in a WebView. Anyway, you're a phenomenal teacher and this video explained things really well. Thank you for helping us navigate the eternally-changing landscape that is native Android development.

I think this is similar to React virtual dom 😮

This man is soon to become the God of native android apps 🙂 Amazing content and best in the world

Hi Philipp, could u share your theme settings plz? 1. What's the name of theme? 2. What's the name of fonts? Thanks ahead :)

Ich habe gehört, dass Du ein Händchen dafür hast AndroidStudio super gut zu erklären. Aber warum auf englisch? Gibt’s da nicht schon jede Menge guter Video s? Ich deutsch dagegen sieht’s da schon viel schlimmer aus. Warum also nicht auf deutsch?? Die AutoÜbersetzung ist viel zu schnell und auch nicht immer genau. Vielen Dank fürs Verständnis. Andreas Blechschmidt

waiting for 123K

Android's ViewModel is not a VM from MVVM. It's just a container which allow to survive configuration changes. Here is also what documentation stated: "The ViewModel class is a business logic or screen level state holder. " ... just a holder. I can implement MVP in my app and use ViewModel as a container for a Presenter in order to survive configuration changes.

bro sorry for interpart i really dont understand like view model and some many other so i want you suggestion .plz dont say life circle it only show me how is work i doent show what inside is do .plz i am lost

Was es aussieht Was es aussieht parAmeter parAmeter

Can MVVM be done with Java or must it be Kotlin!?