r/FlutterFlow

Hello guys, im working on my app project, I had an Idea and tried to fullfill it. So far im doing great but I got stuck at some point, If any of you can help me, please comment and I will text you. Its about adding scores from different pages to scorebase

Hey team, anyone traveling from SoCal?

I want to build an app that will not have any user login or any need for a database, it will just process sounds on the fly. I'm a total noob and flutterflow is giving me error messages that I need firebase. Is there any way to make it not use firebase or another DB? thanks!

help us get the MVP across the finish line.

This is NOT a huge upfront-budget project right now. I can send some cash immediately (not much), but this could grow into a longer-term opportunity with equity, future revenue share, or ongoing paid work as we scale.

I've been trying for days to setup a new FF/Firebase project and it keeps failing. Following all the steps to the letter in each tutorial I can find and still getting errors.

I'm starting simple- just trying to create a user.
The user's identity is being created in the Firebase Authentication table but it's not creating a document in the Users collection. In fact, the users collection isn't being created at all. And, if I refresh the screen then it auto navigates to the logged in screen as it should, so it's actually authenticating but there's an issue somewhere.

I keep getting errors like-

1. Failed to load resource: net::ERR_CONNECTION_RESET
2. the server responded with a status of 400 ()
3. Uncaught (in promise) RethrownDartError: [cloud_firestore/unavailable] Failed to get document because the client is offline.

I'd setup FF projects with Firebase before without issue. So I'm really flummoxed here. I've spent days going down rabbit holes with no actual fixes and the documentation doesn't help.

What have you tried so far?

I've tried using the wizard, I've tried doing it manually, AppCheck is disabled. I've tried creating the Firebase db outside of FF. I've tried creating it from in FF.

I've done this all before without issue but that was a couple years ago. Now, it's a total cluster and I'm starting to look for alternatives to FF.

So I need to vent for a second because I’m genuinely frustrated with FlutterFlow’s billing/support process.
A while ago I decided to stop using FlutterFlow and switch to another platform. I vividly remember canceling my subscription but apparently it either didn’t go through or something glitched because I suddenly got charged another $80.
The second I noticed the charge, I contacted support asking for a cancellation/refund since I wasn’t even actively using the platform anymore. Their response was basically that they could only offer account credits instead of refunding the actual charge.
I’m sorry but account credits for a service I already tried to leave makes zero sense to me.
What makes this even more frustrating is that I genuinely remember canceling it, so now I’m sitting here wondering if their cancellation flow is buggy or unclear. I can’t prove it beyond my own experience but this whole thing feels really shady.
Has anyone else dealt with this with FlutterFlow subscriptions? Were you able to get an actual refund through support, your bank or anything else?
At this point I’m considering filing complaints/reviews because this experience has been insane

Can you describe what problem you app does in 30 seconds or less. Is it clear that your app saves the client time and or money? Why do I choose to use your app over others?

After weeks of struggling with the standard player limits, I finally finished my Audio Pro Suite. Included a 7-language manual too. Hope this saves you guys some headaches! Link in comments.

I’ve been using FlutterFlow for a side project and the actual build phase went smoother than I expected for a small app, it’s been genuinely useful for getting UI, logic, and backend setup done without spending weeks wiring everything manually.

At first it felt like I was moving fast and actually getting somewhere.

The slowdown came after that. There's this thing called WebViewGold I found that lets you wrap your existing site into an app without rebuilding everything was looking into that for a bit.

Once the app reached a usable state I started looking into publishing and that’s where things stopped feeling simple app Store requirements, build exports, deployment steps, and then all the different opinions about whether FlutterFlow projects should be shipped as is or refactored into proper Flutter code it’s a lot of conflicting advice to sort through.

What stood out to me is that the app already works fine through a mobile browser from a user perspective, there isn’t really a huge gap in functionality but the moment you start thinking about App Store distribution, the expectations change completely.

I’ve seen different approaches from people at this stage some fully rebuild in Flutter, some refine the exported code, others delay shipping until everything feels more production ready. All of them make sense depending on the situation, but for smaller projects it feels like there’s a decision to make between moving fast and building something more long-term stable.

Right now I’m just trying not to overthink it or overbuild too early, while still figuring out the cleanest way to actually get it shipped on iOS and Android.