"Why I'm Leaving FlutterFlow: My Final Project and Transition to Vibe Coding"

Feedback

Today, I made the decision that the current project will be the last one my company develops using FlutterFlow. While the tool has significant potential, its persistent instability has become a major challenge.

Every version update brings unpleasant surprises, with features that work inconsistently, such as the test mode, which seems to function only when it "feels like it." Over the past two weeks, we faced significant difficulties with the platform. A task that should have taken no more than two days ended up requiring an entire week due to issues with custom code that simply didn’t work.

My experience with FlutterFlow has been deeply frustrating. I initially switched from Bubble to FlutterFlow due to Bubble’s exorbitant new pricing plans, believing that investing in FlutterFlow would be a wise choice. Unfortunately, the tool has caused nothing but stress, frustration, and a sense of helplessness in the face of its numerous instabilities and limitations.

As a result, I’ve decided to transition to Vibe Coding. Since the current project is already underway and there’s no time to switch platforms, I will complete it on FlutterFlow. However, this will undoubtedly be my company’s final project on this platform.

9
36 replies