The State Changers held a robust discussion centered on the complexities and challenges of using Flutterflow in their projects. They expressed frustration over the lack of clarity and complications in identifying stable builds. However, it was acknowledged that Flutterflow is different from Flutter itself, and they exist at different levels of abstraction, which contributed to the complexity.
Comparisons were drawn between Flutterflow with React Native and DraftBit, each possessing varying complexities and degree of abstraction. The conversation highlighted the need to understand the different versions of each tool and how they interrelate, as well as the dependencies and assumptions contained within them. A crucial part of the discussion focused on the trade-offs when using no code systems, like Flutterflow. These systems, while significantly reducing coding efforts, increase the potential for things to go wrong due to additional layers of abstraction. Thus, developers must weigh the risks of a system failure against the convenience of faster coding and reduced maintenance. The State Changers are looking for ways to reduce their dependence on Flutterflow's API, have better device testing capabilities, and improve debugging. The meeting concluded on a positive note when team member Daniel discovered and shared where to find the version of Flutter being used.
(Source: Office Hours Extra - Flutterflow Export 6/5 )
