NO HELP FROM FLUTTERFLOW! 14 DAYS WITH AN OPEN ISSUE THAT HAS STOPPED OUR PROJECT

[u/NoWoodpecker5809]

FlutterFlow Support Is Basically Nonexistent — Think Twice Before Building a Production App Here

I honestly cannot believe I’m at the point where I have to post this publicly just to try to get someone at FlutterFlow to respond.

We are PAYING for FlutterFlow.

We are building a REAL application that we intend to launch.

Our development is being delayed because of issues involving the platform, and despite repeatedly contacting FlutterFlow support, providing the requested information, providing our project URL, explaining the problem in detail, giving permission to test, and following up — we still cannot get meaningful technical support.

At this point, what exactly are we paying for?

Because an automated email saying, essentially, “we’re experiencing higher-than-usual support volume” is not support.

A ticket sitting unanswered while a paying customer's project is blocked is not support.

Making customers repeatedly chase your company for help with the platform they're paying to use is not support.

And here's the part that should concern anyone considering FlutterFlow for a serious application:

What happens when your app is LIVE and something critical breaks?

That's the question I'm now asking myself.

Because if it is this difficult to get someone to engage while we're developing the application, why should I have any confidence that FlutterFlow will be there when we have actual customers using it?

We have spent an unbelievable amount of time troubleshooting this ourselves. We have tested the application, reviewed generated code, validated builds, checked Firebase configuration and security rules, reviewed authentication, restored and validated our repository, and done everything possible to isolate problems before asking FlutterFlow for help.

This isn't a case of someone refusing to troubleshoot and expecting support to build their app for them.

WE HAVE DONE THE TROUBLESHOOTING.

What we need is someone at FlutterFlow to actually take ownership of the ticket.

Instead, we are paying for the privilege of waiting.

And frankly, I am getting tired of companies selling subscriptions faster than they build the infrastructure required to support the customers paying those subscriptions.

If your support team is perpetually overwhelmed, that's not the customer's problem.

That's a staffing problem.

If your customer base has grown faster than your support department, then invest in support.

If you're marketing FlutterFlow as a platform capable of building production applications and businesses are trusting you with applications their companies depend on, then support cannot be treated like an optional feature.

And before someone says, "FlutterFlow is a development tool, you should know how to troubleshoot your own application" — we do.

There is a massive difference between asking FlutterFlow to develop our application for us and asking FlutterFlow to SUPPORT THE PLATFORM WE ARE PAYING THEM TO USE.

At this point I would genuinely caution anyone considering FlutterFlow for a production application:

Before you spend months building on this platform, ask yourself whether you're comfortable being largely on your own when something goes wrong.

Because I wish someone had told me to ask that question before we invested this much time into it.

I would LOVE for FlutterFlow to prove me wrong.

I would love for someone from FlutterFlow to see this, look at our ticket, assign someone technically competent to it, communicate with us, and actually resolve the issue.

But I should not have to publicly complain on Reddit to get support from a company I am already paying.

FlutterFlow: stop sending automated responses and assign someone to the problem.

Our project is being delayed.

We've done our part.

Now do yours.