8:33 How exactly does it know to what state to animate, if the end-state is empty? Everything in their is set to the default (alpha 1 for example) , except for constraints which stay the same as those on the start?
@@xBlaqs But it's the end result. Not the beginning. Wouldn't it make more sense to have those set in the beginning, and animate to the new state that it more defined? Or both ways are possible? Meaning that for both start and end state, they take all from the layout xml as default, and only if you change, it changes for where you've put the values?
@@LiranBarsisa That's right. It's default for both. I think sometimes it's easier to animate to your target state. Go to 2:00. It's all explained in the video.
@@xBlaqs OK thanks. I do wonder though: Do app developers use this mechanism a lot? Sure it could be nice in some cases, but in others I might think "That's too much for something simple". I once asked about adding some basic functionality of ViewAnimator/ViewSwitcher (to switch easily between states of loading and showing content), and was told that those aren't recommended to be used, but I don't get how I could have used something more suitable, as there aren't always moving parts that I need/can animate between them. Just switching of views...
It was a very good explanation! Waiting for upcoming parts!
Good explanation really enjoyed. It was very well paced and step by step. I am waiting for the next episode related to KeyFrames.
Can I apply the MotionScene, MotionLayout and ConstraintSet in API >= 21 ?
8:33 How exactly does it know to what state to animate, if the end-state is empty? Everything in their is set to the default (alpha 1 for example) , except for constraints which stay the same as those on the start?
If ConstraintsSet is empty, it takes all the constraints defined in your layout xml file.
@@xBlaqs But it's the end result. Not the beginning. Wouldn't it make more sense to have those set in the beginning, and animate to the new state that it more defined?
Or both ways are possible?
Meaning that for both start and end state, they take all from the layout xml as default, and only if you change, it changes for where you've put the values?
@@LiranBarsisa That's right. It's default for both. I think sometimes it's easier to animate to your target state. Go to 2:00. It's all explained in the video.
@@xBlaqs OK thanks. I do wonder though:
Do app developers use this mechanism a lot?
Sure it could be nice in some cases, but in others I might think "That's too much for something simple".
I once asked about adding some basic functionality of ViewAnimator/ViewSwitcher (to switch easily between states of loading and showing content), and was told that those aren't recommended to be used, but I don't get how I could have used something more suitable, as there aren't always moving parts that I need/can animate between them. Just switching of views...
I am confused! What am I supposed to learn, this or jetpack compose which tackles animation in its own way?
I am trying to do a translationX and translationY animation to end at the center of another view in the motionlayout? How? thanks!!
I love this man! You are great at explaining such subjects!
MAD skills is simply amazing!!
nice video! waiting for more
in 9.5 minutes this guy said over 100 times more than a google io speaker!! Awesome!
Thank you and very super easy way to understand the motion layout 😄
Thanks for this guide!
Amazing!
Great tutorial
very informative explanation.
Great feature
Love it!
Awesome ❤️
Awesome
i love u sir....you are awesome !....awesome explanation!
Please share source code
Thanks
Kinda cool.
give me more many example sir please
🤩🤩🤩🤩🤩
Some one please help me how to learn Arduino program
Why don't you refine android's basic animations?😒