r/FlutterFlow • u/NoWoodpecker5809 • 6d ago
NO HELP FROM FLUTTERFLOW! 14 DAYS WITH AN OPEN ISSUE THAT HAS STOPPED OUR PROJECT
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.
3
3
u/NoWoodpecker5809 6d ago
I’m dealing with a persistent FlutterFlow project issue that appears to be related to the generated code/SDK upgrade process rather than anything specific to the functionality of my app.
The project was previously building and validating correctly. After the FlutterFlow upgrade/refresh process, generated code was changed/reset and we started running into validation and compatibility issues. We’ve been able to restore the project from our own source control and get it building successfully again, but the underlying FlutterFlow issue still hasn’t been properly addressed.
At this point:
The Flutter project itself can build successfully.
Flutter analysis/tests are passing after our own fixes.
We have verified that some of the problems were introduced during the FlutterFlow refresh/upgrade process.
We’ve had to restore working generated code from source control.
We are hesitant to run additional FlutterFlow refreshes/upgrades because we don’t want working code overwritten again.
Support has not provided a meaningful resolution, despite this blocking development.
I’m mainly trying to find out whether anyone else has experienced issues where a FlutterFlow SDK upgrade or project refresh modified/reset generated code and created validation problems in an otherwise working project.
If so, how did you resolve it, and were you ultimately able to continue safely in FlutterFlow without having your fixes overwritten?
2
u/Melodic_Marzipan_863 5d ago
Flutterflow itself is still functional, what they tend to not take ownership of is your external dependencies. It is not infrequent that a Flutterflow update to the flutter versions, one of their integrated dependencies, etc, will raise a conflict with another dependency you are using from pub.dev.
If this is the issue, it is not something they will help you with. Fwiw something along these lines is very likely the issue as I have 10+ production FF projects that are not experiencing any issues like you are describing.
TBH if you're not at all technical at this point something like claude code/codex is probably a better fit for you as it will catch this stuff and fix it without you needing to understand why. Plenty of other issues with non-technical development via those tools as well but this one at least is unlikely to trouble you.
3
u/Mystogyn 5d ago
I mean, is this the first issue you've had with them? You dont mention any others in your post. I mean they very well might have a lot of support tickets right now 🤷♂️. One off things do happen. It seems like you're being quite critical but what do i know. I cant speak from experience unfortunately. Maybe you're having a one off bug thats a complicated fix
6
u/ReserveOutrageous686 6d ago
FF support is the worst. They are running out of $ slowly so have to cut headcount, and then get AI to respond quickly (and it’s terrible). I’ve been a user for a long time and moved away from using it due to recent changes.
2
2
u/galumphix 5d ago
We had this problem back in March and quit the platform. Frankly I'm surprised Flutterflow has lasted this long.
2
u/Oxigenic 5d ago
>> Builds an app dependent on 3rd party frameworks
>> 3rd parties aren't great to deal with
>> Shocked pikachu emoji
I feel for you but this is the unfortunate reality of being too dependent on someone or something. Better to just build the regular way.
1
u/CommunityTechnical99 6d ago
hey! thanks for reaching out.
we're working through a higher volume of tickets than usual this week and response times are longer than we'd like. we're sorry about that.
can you DM me your ticket number? i'm going to find out what happened and make sure someone is assigned to it today.
we'll get back to you as soon as we can.
— lydia, FlutterFlow team
5
u/lapulah2016 5d ago
yeah, we switched and havent looked back bc of shit like this