Android Basics 2023 should be adopted by Google! So much has been written and nothing has been said so well. Thanks for the wonderful series on behalf of all beginner Android (Kotlin) developers! 🔥
It was so interesting to see how Context retrieved in Presentation being shown on the secondary display is different from the one retrieved in its parent Activity which is shown on the main display - they had different resource configuration, so on the smaller secondary display hdpi drawables were used, while on the main display they were xxhdpi 🙂
Good material, concise …and great presentation!! Only suggestion I have is get rid of the annoying sound and image effect you have once in a while..maybe if the video is loading ?
I am learning Android development and now my basics are very much clear but when I try to read official documentation it still feels tough Please make a dedicated video on how to actually go through it
Thank you Phillip! This was very helpful 👍👍👍I wish this video came out before I submitted my first app to the Google Play Store. Had struggled a lot with passing the context.
I wish you had this in Java... I'm not a fan of Kotlin. Took your course on it but trying to unlearn 24 years of programming with more traditional languages such as C based and Java is quite difficult.
Nice video! and another reason to use activity context over application context is when user changed system language, only activity will be recreated and the application won't. so if you use getString() with activity context will have the updated language and application context won't. correct me if I am wrong.
Great content as always thank you😊, could you provide us an example,how we could get context in kotlin and compose multiplatform.For example i want to access context from shared common with expect and actual.Could you recommend any suggestion.For example,scenario , we are using KVault it needs context for android and no need of context for ios while calling inside from shared common with compose multiplatform
Thanks Philip for the informative video! Any chance you could discuss how to access the context in a Fragment? If I am correct, requireContext() should be used. However, sometimes I noticed that the Fragment might not be attached to a context, leading to an IllegalStateException. It would be nice, if you could discuss how to use context in a Fragment in general, what context to use, and what issues may arise. Thanks again for the great video!
Considering the traditional way of android development is dying and being phased out for the modern android development way. Are these 2023 Android Basics videos taking that into account?
What should we do if we need to use activity Context in our ViewModel, but don't want the memory leaks that come with referencing the Context in ViewModel's field?
From my understanding "native android developer" means somebody that can transform his code into the selective android processor' machine code. For example, in android, the CPU could be ARM architecture, or other architecture. So, their technique might differ for different CPU, like what library to link etc. Not to mention that android have different type of operating system too if not mistaken. But for us that knows kotlin, we can let JVM settle this issue of handling different CPU architecture. We just focus on our code testing, the unit testing, android testing. But honestly I wanted to learn Gradle first without android studio only Gradle and kotlin, and try to use different dependencies out there. Currently working on to parse object file for 3d rendering without tutorial. The only guidance is from C++.
Quick note for you: a native Android developer is anyone who writes an app for Android only, directly with Android's Java or Kotlin libraries. A non-native developer would write code in a framework like Flutter or React that cross compiles to Android/iOS/other, and abstracts away the details of Android-specific concepts like Context or the onCreate/onDestroy lifecycle. It is "native" with respect to the operating system, not the hardware- the same could be said for a native Windows or iOS app. Hope this helps!
@@PhilippLackner Thank you! So, in this case the memory leak will occur only if we change the screen orientation and the activity is not permanently destroyed, right? But if we navigate away, the viewModel will be destroyed along with the activity?
Do you know why there is no context in desktop apps, for example all I need to read/write a file is to create a File object and pass the path then create something wraps that File object
![[TH] 2024 PMGC League | Survival Stage วันที่ 1 | PUBG MOBILE Global Championship](http://i.ytimg.com/vi/FVFT-PFwU80/mqdefault.jpg)
Thanks for giving context to Context
Test
Someone had to say it at some point. 🤷♂
Is it you dad?
Android Basics 2023 should be adopted by Google! So much has been written and nothing has been said so well. Thanks for the wonderful series on behalf of all beginner Android (Kotlin) developers! 🔥
Thanks so much 🙏🙏
Never knew what context did, but I’m happy to say this has laid a good foundation for me
so long without understanding the concept of Context until watch your video. thanks!
Thanks a ton, he's better than my professor
Thank you so much sir, I have been working as android developer for 5 years but I just understand what is context now.
Such clarity on Android...you will only find in this channel!
It was so interesting to see how Context retrieved in Presentation being shown on the secondary display is different from the one retrieved in its parent Activity which is shown on the main display - they had different resource configuration, so on the smaller secondary display hdpi drawables were used, while on the main display they were xxhdpi 🙂
There's no over knowing these things. Always something new to pick. Thanks for your videos
I've read the documentation at least three times but your videos explain these concepts so much better, thanks!
Thanks! For 10 min video I got more usefull information than for the previous hours of exploring other resources
Your videos are a great resource for anyone learning to code. Thank you for creating it!❣
Good material, concise …and great presentation!! Only suggestion I have is get rid of the annoying sound and image effect you have once in a while..maybe if the video is loading ?
wow saar "material" very good term saar amazing vocabulary hope you are having a great day doing the needful. btw which designated street?
I am learning Android development and now my basics are very much clear but when I try to read official documentation it still feels tough Please make a dedicated video on how to actually go through it
Yeah the Android docs suck
I'm loving this playlist. keep up the great work
Thank you Phillip! This was very helpful 👍👍👍I wish this video came out before I submitted my first app to the Google Play Store. Had struggled a lot with passing the context.
Thank you I have just joined this series will follow up to end.
A very good explanation of a more "tricky" topic
Goldmine of Information ! I am collecting money to enroll to your Personal Training, hope I do it soon ! 😄
Crystal clear explanation ! Thanks.
Fantastic explanation!
what a greet explanation of Context,thank you
Thanks Philipp , can you make a video about state flow?
thank you Philip, this is great video about Viewmodel
You're the best, bro! This was very helpful. Thanks for sharing knowledge...
Great video! Waiting for more of these!
That was an amazing explanation...
again very cleary explained, thanks very much
thanks for amazing topic
Thanks man! You did a great work already and I'm wating for more topics like these!
Very informative Video.
what theme you are using in android studio ?
Great job Philip
great explanation😄
I wish you had this in Java... I'm not a fan of Kotlin. Took your course on it but trying to unlearn 24 years of programming with more traditional languages such as C based and Java is quite difficult.
What is the differences between requireContext(), requireActivity(), context, and activity in fragment? And when do we use it?
Nice video! and another reason to use activity context over application context is when user changed system language, only activity will be recreated and the application won't. so if you use getString() with activity context will have the updated language and application context won't. correct me if I am wrong.
Nah, which context doesn't matter there since it's just used to retrieve a resource
@@PhilippLackner oh you are right, my case should be updating an in-app language but the application context is not updated correctly
Thank you a lot!❤️
Perfect, as usual. Thank you!
I love your videos! Thanks so much !!!
very well explained!
Great free leson. Thanks!
Great content as always thank you😊, could you provide us an example,how we could get context in kotlin and compose multiplatform.For example i want to access context from shared common with expect and actual.Could you recommend any suggestion.For example,scenario , we are using KVault it needs context for android and no need of context for ios while calling inside from shared common with compose multiplatform
What Android studio theme does Phillip use?
Thanks Philip for the informative video! Any chance you could discuss how to access the context in a Fragment? If I am correct, requireContext() should be used. However, sometimes I noticed that the Fragment might not be attached to a context, leading to an IllegalStateException. It would be nice, if you could discuss how to use context in a Fragment in general, what context to use, and what issues may arise. Thanks again for the great video!
requireContext is correct, but the Fragment needs to be attached to the activity, so you can't use it in a global variable for example without lazy
Super
thanks Philip
whenever i have to use context anywhere , i just use val context = LocalContext.current. is this approach ok? or can it lead to some error?
thanks for such informative video
please make a playlist about Ios Basics 2023 as well it will be very helpful who want to start KMM
Thanks, this helps. ❤
nice video
Considering the traditional way of android development is dying and being phased out for the modern android development way. Are these 2023 Android Basics videos taking that into account?
The things I teach here are fundamental about Android and haven't changed in the past 5 years
Most Android jobs have to deal with both legacy and modern development tools and techniques. Also, Context is used everywhere.
What should we do if we need to use activity Context in our ViewModel, but don't want the memory leaks that come with referencing the Context in ViewModel's field?
Don't do it, there's no reason to
So the answer to my question is: We should learn architecture better. After watching more of your videos, I'm starting to understand! Thank you!
Great!!
legend
7:07 Imaæginnn
0:57 it comes to 'exync'? what exync mean?, awrote this in the auto-generated subtitles, but I wonder what words he actually said.
"exact"
"When it comes to exact use cases..."
@@jayshartzer844 thx :>
From my understanding "native
android developer" means somebody that can transform his code into the selective android processor' machine code. For example, in android, the CPU could be ARM architecture, or other architecture. So, their technique might differ for different CPU, like what library to link etc. Not to mention that android have different type of operating system too if not mistaken.
But for us that knows kotlin, we can let JVM settle this issue of handling different CPU architecture.
We just focus on our code testing, the unit testing, android testing.
But honestly I wanted to learn Gradle first without android studio only Gradle and kotlin,
and try to use different dependencies out there.
Currently working on to parse object file for 3d rendering without tutorial. The only guidance is from C++.
Quick note for you: a native Android developer is anyone who writes an app for Android only, directly with Android's Java or Kotlin libraries. A non-native developer would write code in a framework like Flutter or React that cross compiles to Android/iOS/other, and abstracts away the details of Android-specific concepts like Context or the onCreate/onDestroy lifecycle. It is "native" with respect to the operating system, not the hardware- the same could be said for a native Windows or iOS app. Hope this helps!
How did you make your @s green?
167th...Thanks Philipp
Cool
7:28 Why viewModel isn't destroyed before the activity is destroyed? Wouldn't we avoid a memory leak, in this case a context?
The whole purpose of a viewmodel is to outlive the life cycle of the activity, check the previous video 😄
@@PhilippLackner Thank you! So, in this case the memory leak will occur only if we change the screen orientation and the activity is not permanently destroyed, right? But if we navigate away, the viewModel will be destroyed along with the activity?
Do you know why there is no context in desktop apps, for example all I need to read/write a file is to create a File object and pass the path then create something wraps that File object
Context, as described in this video, is an Android specific paradigm. You could create your own concept of “Context” in a desktop application.
6:25
Learnt too many things from you
Waht's your Android Studio Theme?
Xcode dark
I came here to learn but now only watching your videos beacuse you are very handsome 😅 charming
Tidak masalah ANDROID GENOSIDA di Uji Coba di Indonesia,.kalau di butuhkan akan di perluas di seluruh negara dunia.😮