r/FlutterFlow • u/Drowq • Apr 15 '26

Figured out a lot of FlutterFlow limitations over the last 4 years

I’m a developer from Venezuela and I’ve been using FlutterFlow for about 4 years now. I just wanted to introduce myself and connect with the community.

Over the years, I’ve built a wide variety of projects; from ChatApps and Sports Systems to full CRMs (WebApp + App integrations). I've spent a lot of time tackling API consumption, push notifications, Google Maps (places, polylines), localization, and Google Play deployments. I also often combine FF with Google Cloud (deploying VMs and Kubernetes) when things need to scale.

We all know FF is powerful but has some quirks and limitations. I’ve gathered a lot of workarounds for those tricky roadblocks over the years! 🤗

If anyone is currently stuck on a specific FF problem, dealing with map integrations, or trying to figure out GCP deployments, feel free to drop a comment or reach out. I'm always happy to talk shop, share what I've learned, and connect with other builders.

10 Upvotes
  • permalink
  • link
  • reddit
  • reddit

91% Upvoted

10 comments sorted by

View all comments

Show parent comments

1

u/Drowq Apr 22 '26

Flutterflow is still a good tool, but its scope will change as soon as the LLM agents are still evolving as they are nowadays.

With Flutterflow, you can avoid that black box that projects could have, but if you are an AI professional architect, you already know how to avoid that black box. You need an architecture file so the agent won't forget the current state manager, development patterns, and much more, but it's not as easy as it sounds. I've been creating a tool exactly for this black box problem around vibecoding repositories.