Life of a Widget?! | Decoding Flutter 

I was thinking the same. I didn't get your comment though. I got the what we as developers think lifecycle methods are part, but not the lifecycle of an element. I do know however that the Flutter team and we refer to different things with confusingly same names.

​@@marflage Yes the confusion stems from the fact that the word "widget" is sometimes used for "static configuration of UI elements i.e recipe" and other times for the elements themselves.

agree

What more do you need to know? The last sentence seems to make it clear: widgets don't have a lifecycle. They are either built, rebuilt, or not used. During the building process, flutter calls the build method. When it's rebuilt, it just calls the build method again. When it's not used, the build method isn't called at all.

@@loganrussell48 well there is state and the Lifecycle of a therefore StatefulWidget. I know that this is the States Lifecycle, not the Widgets, but especially for new Flutter Devs, this video will probably only be confusing

@@niggelgame The states are no widgets, they are classes that help to keep state of variables, but every time it rebuilds, it rebuilds other widgets, never the same ones…

​@@niggelgame Even with a stateful widget, the widget doesn't have a lifecycle. A new version of the same type of widget will be built by calling the build method again, with the same mutable state class. It is the changing state class that actually makes the application useful. You can think of the build method as a sort of transformer that takes a data model (state) and transforms it into a usable piece of the application using the build method. Again, there is no lifecycle. Just build methods. Supply something different to the build method, get a differently configured widget returned from the method. When you want to change the widget, change the state of the widget using setState and the widget will update the state, and then the build method will be called again, to generate a new widget, which will fall into the same spot in the widget tree as the last one.

@@loganrussell48 yes, that’s what I wanted to say, but I didn’t really. My point was, that for new Devs, the State, which has some sort of Lifecycle, is directly coupled with a StatefulWidget, which may imply a StatefulWidget Lifecycle. That is what I thought until I started taking a closer look at Flutter itself and it is probably what many others think too, which could make this video seem confusing

It did not for me. But basically what was conveyed was that every element is rebuilt from the ground up every time there is a change in the state of the current view.

I think it makes the video more accessible to different skill levels. If more people can understand the video, doesn't that make it better? 🤔

Huh? It seems fine to me. Did they update it?