In this meeting, the State Changers expressed concern about using Flutter Flow and the stability of the build. They discussed the different levels of abstraction in Flutter and how it can complicate the development process. They also mentioned the potential risks of using a no-code system like Flutter Flow but acknowledged that it can speed up development and reduce maintenance. The participants praised Daniel for pointing out that they can check the Flutter version in Flutter Flow. They concluded the meeting by discussing the need for a tighter shipping loop that includes Flutter Flow but also allows for testing on devices and debugging.
(Source: Office Hours Extra - Flutterflow Export 6/5 )
