I appreciate this man whose explanation is at peak level ... After 3 years from the time of uploading, this playlist is still found worth it ... !! As even AI suggested me this Channel for android development ... Thank you so much sir ... Keep it up , and after this playlist , I will checkout your latest android basics playlist for sure ... Thank you 😃
Great tutorial, thank you for this. So much better explained than the other tutorials, this is how you do a tutorial, build everything from scratch, not have a bunch of ready made code and then start copy pasting like some other tutorials.
I'm starting Android programming and getting to know how to make ui layouts. I've been searching for a week good tutorial until I came across this video of yours. I am very pleased with the way you put it without unnecessary explanations and long-winded speeches and for the good audio and video quality.. At first viewing, I still didn't understand your video importance but eventually the matter opened up and I understood that now we are at the heart of the matter and how the constraint layout pile up. Thanks for your videos.
Nice tutorial, thanks! Easy to understand for beginners. Please make some tutorials about making small apps using the basic functionalities for beginners.
Hello Raw, I've made my first app a month ago ( a simple app with no database) and I think the easiest app to make are read-only apps like recipes apps, online libraries apps, story book app and so on
very good tips, i never noticed those options... BTW am i the only one in the whole universe having constant trouble with constraint layout ???? i mean, if my layout is very simple (like, just a cascade of elements one above another), it's fine; but as soon as the design becomes a bit complicated, i pull my hair off each time... idk, it's me or the constraint layout or the IDE... it was so much easier with linear or relative layouts... constrain layout sure gives me too much CONSTRAINTS, duuuuh
i worked with constraint layout but i still don't get to make views to stick to the same position in all phones sizes , what could be the problem and thank you for the video
This is not always possible, even with Constraint layout. Generally, you want to set the constraints from the inside to the outside. But to support all screens you have to create multiple XML files for different screen sizes
hi why it it is not possible to directly add buttons and all in case of linear layout...as just you did in constraint layout...is xml coding always needed in linear layout??
I will go deeper into constraint layout next video. I don't see a reason why you should use relative layout, constraint layout is just better. This is why there won't be a part about relative layout
But in Visual Studio you also need layouts for responsiveness. ConstraintLayout is a pretty smart thing to make your layout responsive while staying performant
@@PhilippLackner Be that as it may, there still seems to be a lot of unnecessary complexity in Android Layouts (it isn't just Constraint Layout). Do other Layout packages/tools have the same performance problems Android has, for example, with such basic and simply layouts as LinearLayout? Do others do as Android did, making things more confusing by first telling people to use RelativeLayout instead of LinearLayout, but then retracting and saying RelativeLayout has too many of its own problems,among them, not being very performant? For that matter, did Android *have* to introduce the new term in their tutorials and documentation, 'constraint', without every defining the term? You gave more of a definition than they ever did, and even that seems more complicated than it had to be. First, you said the constraint pulled the widget all the way to the wall of the container, but then you admitted that that behavior is *modified* by the presence of margins. Swing never did anything like that. The behavior of the widgets is much easier to predict. That could be why people are still learning and using Swing even after Oracle made the decision to try to push everyone over to FX instead.
I appreciate this man whose explanation is at peak level ... After 3 years from the time of uploading, this playlist is still found worth it ... !! As even AI suggested me this Channel for android development ... Thank you so much sir ... Keep it up , and after this playlist , I will checkout your latest android basics playlist for sure ... Thank you 😃
I simple can't understand who doesn't like the video ? Super and crystal clear voice.
every point explained clearly.
These videos are amazing, you cover so much in such a short period of time
Glad you like them!
This playlist is a godsend. Thank you for the tutorials!
Great tutorial, thank you for this. So much better explained than the other tutorials, this is how you do a tutorial, build everything from scratch, not have a bunch of ready made code and then start copy pasting like some other tutorials.
I'm starting Android programming and getting to know how to make ui layouts. I've been searching for a week good tutorial until I came across this video of yours. I am very pleased with the way you put it without unnecessary explanations and long-winded speeches and for the good audio and video quality.. At first viewing, I still didn't understand your video importance but eventually the matter opened up and I understood that now we are at the heart of the matter and how the constraint layout pile up. Thanks for your videos.
Thanks that you put such useful stuff for free online. And not only that, it is good too
these are the best android tutorials on the internet
I have an exam in college tomorrow and you are a life saver thank you
Nice tutorial, thanks! Easy to understand for beginners. Please make some tutorials about making small apps using the basic functionalities for beginners.
Hello Raw, I've made my first app a month ago ( a simple app with no database) and I think the easiest app to make are read-only apps like recipes apps, online libraries apps, story book app and so on
Great vid, watch on 2x, his diction is clear and you can follow everything.
toll. ganz klar und verständlich. danke
Outstanding explanation...!
Glad it was helpful!
This was awesome. Thanks for the high-quality content.
What a great video. Thank you very much. Such a simple way of explaining ConstraintLayout
Very useful. Thank you!
Perfect explanation. Thanks!
very good tips, i never noticed those options... BTW am i the only one in the whole universe having constant trouble with constraint layout ???? i mean, if my layout is very simple (like, just a cascade of elements one above another), it's fine; but as soon as the design becomes a bit complicated, i pull my hair off each time... idk, it's me or the constraint layout or the IDE... it was so much easier with linear or relative layouts... constrain layout sure gives me too much CONSTRAINTS, duuuuh
Really you explain really well philipp😇
Please make a complete guide for beginners
Well Explained!!
Thank You Very Much!
Glad it was helpful!
cool let me watch it baraker zeonlist.. nice explanation
Video was liked successfully
Thank you very much for your help on this subject Philipp. Much appreciated.
Clear and to the point
thanks
I must thank you for share it and damn the way you explain it it's so clear. Excellent work!
great video, thank you for your clear concise explanation, keep up the excellent work
i worked with constraint layout but i still don't get to make views to stick to the same position in all phones sizes , what could be the problem and thank you for the video
This is not always possible, even with Constraint layout. Generally, you want to set the constraints from the inside to the outside. But to support all screens you have to create multiple XML files for different screen sizes
Thank you , i will try to learn to do that , cause i never tried setting up different XML files
Interesting and clear explanation
wow amazing teacher
Good job
I will just say its amazing
hi why it it is not possible to directly add buttons and all in case of linear layout...as just you did in constraint layout...is xml coding always needed in linear layout??
Excellent!
Thankyou😍
Nice Lecture Bro
thank you i use to code each line in the text sometime i become confused on the attributes. next should be relative layout
I will go deeper into constraint layout next video. I don't see a reason why you should use relative layout, constraint layout is just better. This is why there won't be a part about relative layout
@@PhilippLackner yes thank you we love it
Thank you!
Very useful!
Glad to hear that!
Thank you so much for this.Does relative layout still exist in android studio 4?..Thanks in advance
Yes, It exists (Constraint Layout)
Super useful, subscribed.
Thanks and welcome :)
Clear
Well done, thank you!
Thank you too!
Is there a reason the margins are in multiples of 8dp?
Damn this guy goood!
My constraint widget doesn't work, when I enter a number and press enter nothing changes
thankyou
I wish there was an explanation for relative layout😢
How do we add scrollview with constraint layout?
just put the constraintlayout in the scrollview
why don't u have a course on udemy?
I have Premium courses for advanced development on my website here, check it out :) pl-coding.com/courses
@@PhilippLackner can't believe I have been missing out all this time
You should have named this as Button basics. 😆
i did not understand
why the hell it has to be this complicated?? couldn't they do something like MS Visual studio... this is plain stupid
But in Visual Studio you also need layouts for responsiveness. ConstraintLayout is a pretty smart thing to make your layout responsive while staying performant
@@PhilippLackner Be that as it may, there still seems to be a lot of unnecessary complexity in Android Layouts (it isn't just Constraint Layout). Do other Layout packages/tools have the same performance problems Android has, for example, with such basic and simply layouts as LinearLayout? Do others do as Android did, making things more confusing by first telling people to use RelativeLayout instead of LinearLayout, but then retracting and saying RelativeLayout has too many of its own problems,among them, not being very performant?
For that matter, did Android *have* to introduce the new term in their tutorials and documentation, 'constraint', without every defining the term? You gave more of a definition than they ever did, and even that seems more complicated than it had to be. First, you said the constraint pulled the widget all the way to the wall of the container, but then you admitted that that behavior is *modified* by the presence of margins.
Swing never did anything like that. The behavior of the widgets is much easier to predict. That could be why people are still learning and using Swing even after Oracle made the decision to try to push everyone over to FX instead.
That's true!!!
Thanks!
Thank you!
You're welcome!