CONSTRAINT LAYOUT BASICS - Android Fundamentals 

Glad you like them!

Glad it was helpful!

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

Thank you too!

Glad it was helpful!

Thanks and welcome :)

Glad to hear that!

Yes, It exists (Constraint 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

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

just put the constraintlayout in the scrollview

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

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!!!

You're welcome!