Also regarding architecture, there’s already several non-official patterns out there: Stateful/Stateless Widgets, InheritedWidgets, Streams/Sinks, Redux, etc.
Strateful and Stateless Widgets are prerequisites in making widgets. Choosing Stateless would mean that this widget will not rebuild. Stateful may rebuild the Widget anytime like checkbox, radiobutton, and etc.
I think having many patterns have its own complexity when dealing the behaviour of the app. If you haven't watched Reactivate applications in Flutter from GOOGLE I/O 18. You'll see those patterns fit for the application.
Strateful and Stateless Widgets are prerequisites in making widgets. Choosing Stateless would mean that this widget will not rebuild. Stateful may rebuild the Widget anytime like checkbox, radiobutton, and etc.
I think having many patterns have its own complexity when dealing the behaviour of the app. If you haven't watched Reactivate applications in Flutter from GOOGLE I/O 18. You'll see those patterns fit for the application.
Thank you very much for the review.
Right, I forgot that "everything is widget" :)
The sentence you quote has a link to the specific talk you mention in your comment ;)