Very interesting topic! :) Just a quick piece of feedback: at 3:54, there is some noise in the video (I think someone else already pointed that out). I am not sure whether it is environmental noise or from your audio setup. If it is from your surroundings and you have an Nvidia GTX or RTX card, then I can really recommend Nvidia RTX Voice. It removes all noises and is free. (And it works with some GTX cards as well, so don't be fooled by the name :)). Other than that, it's a very cool topic and an interesting conversation you struck with the FlutterFlow team. :)
Have you decided? I didn't know there were issues with Flutter web apps. So, thanks for making this video. But now I have the same question. Look forward to learning what you decide to do.
@@ambitiouslabs Interesting. Are you using the database in Xano, as well? Or did you just go Xano (+ other database) over Buildship (+ other database) because of lack of maturity in buildship?
I'd do it with flutterflow. Bubble and Draftbit could also be options because of the use of js but I think that flutter is continuously making improvements and I think by the time people actually start learning it will only become better and better. Plus the FF team is always innovating and I think they will make even more features for PWA's in the future. I mean your channel is primarily about FF I think theres enough there to make it work but you may have a different perspective.
Great point and I have considered the same argument. Flutter WILL get better, I’m sure of it. I have a call soon with the Head of DevRel at FlutterFlow & we’re gonna talk about this.
I feel ya. For me, for MVP/user experiment, I like wysiwyg FF and having single code base to test both web and mobile user assumptions. I’ll be interested to see your video on specifics around performance and stability. If I were doing a game, even a few milliseconds of load, mouse, or click lag would be a deal killer. But for most social or LLM oriented applications right now, users have a built-in expectation for certainly up to a few seconds on a database call, and load/mouse/click lag can be up to a second or so without them generally feeling like the UI has unacceptable frictions. Do those specs seem right from your perspective, and what are the specs you’re seeing from flutter on web?
Flutterflow is not a No-code. It is more of a low-code. Dont use their built-in integration functions, but run your processes on serverless, say, cloud functions that does processing on firebase. Then FF would be an interference.
Why would flutterflow suffer with web? is it overload or due to struggling HTTP requests? I feel like web app is essentially an mobile app but with more data load and a bigger resolution screen?
I went all in from Ionic (Capacitor) / React to FlutterFlow (for quicker run and gun jobs) but for web, I am still sitting on Wappler (Bootstrap Frontend and it's own visual server actions -> exports either Node, PHP or ASP). Similar to FF, you own the code at the end. Perhaps something for you, guys?
I watched the whole video. Your struggle is interesting and so were the comments that were left. What I found unprofessional was the sound. Really annoying to have to listen to that humming sound. What was it?
Very interesting topic! :) Just a quick piece of feedback: at 3:54, there is some noise in the video (I think someone else already pointed that out). I am not sure whether it is environmental noise or from your audio setup. If it is from your surroundings and you have an Nvidia GTX or RTX card, then I can really recommend Nvidia RTX Voice. It removes all noises and is free. (And it works with some GTX cards as well, so don't be fooled by the name :)).
Other than that, it's a very cool topic and an interesting conversation you struck with the FlutterFlow team. :)
Have you decided? I didn't know there were issues with Flutter web apps. So, thanks for making this video. But now I have the same question. Look forward to learning what you decide to do.
Yes, we went with WeWeb & Xano. I’m building another web app in FF too, however.
I’m so sorry about the hum. I’ll refilm this :(
@@ambitiouslabs Yeah. I guessed WeWeb. I've been looking into it. Looks pretty good.
@@ambitiouslabs Interesting. Are you using the database in Xano, as well? Or did you just go Xano (+ other database) over Buildship (+ other database) because of lack of maturity in buildship?
Did I miss the main reasons why you wouldn’t build it in FF? Whats the down side? (Love your content btw)
I'd do it with flutterflow. Bubble and Draftbit could also be options because of the use of js but I think that flutter is continuously making improvements and I think by the time people actually start learning it will only become better and better. Plus the FF team is always innovating and I think they will make even more features for PWA's in the future. I mean your channel is primarily about FF I think theres enough there to make it work but you may have a different perspective.
Great point and I have considered the same argument. Flutter WILL get better, I’m sure of it. I have a call soon with the Head of DevRel at FlutterFlow & we’re gonna talk about this.
Flutter is a mobile language. You'll have to be desperate to use such a language.
I feel ya. For me, for MVP/user experiment, I like wysiwyg FF and having single code base to test both web and mobile user assumptions. I’ll be interested to see your video on specifics around performance and stability. If I were doing a game, even a few milliseconds of load, mouse, or click lag would be a deal killer. But for most social or LLM oriented applications right now, users have a built-in expectation for certainly up to a few seconds on a database call, and load/mouse/click lag can be up to a second or so without them generally feeling like the UI has unacceptable frictions. Do those specs seem right from your perspective, and what are the specs you’re seeing from flutter on web?
after the midle of the video you get a noise in the audio and makes hard to understand what are you saying, hope you can fix it ;)
I might have to refilm & re-upload. Wish I noticed that earlier. Promise it won’t happen again!
Flutterflow is not a No-code. It is more of a low-code. Dont use their built-in integration functions, but run your processes on serverless, say, cloud functions that does processing on firebase. Then FF would be an interference.
Why not, you never know if you dont try. You could make a series about it, and show people what capabilities it has.
It has the capabilities. Just flutters web performance is questionable. I’ll make a video showing why.
Why would flutterflow suffer with web? is it overload or due to struggling HTTP requests?
I feel like web app is essentially an mobile app but with more data load and a bigger resolution screen?
Why not framer. I think with Figma you can also export the code so you’re not locked in.
Framer locks you in.
I went all in from Ionic (Capacitor) / React to FlutterFlow (for quicker run and gun jobs) but for web, I am still sitting on Wappler (Bootstrap Frontend and it's own visual server actions -> exports either Node, PHP or ASP). Similar to FF, you own the code at the end. Perhaps something for you, guys?
I watched the whole video. Your struggle is interesting and so were the comments that were left. What I found unprofessional was the sound. Really annoying to have to listen to that humming sound. What was it?
why not bubble?
No code export options, you are locked in and at their mercy forever.
Drafbit?
That’s React Native right? I’m looking at WeWeb and others
There are def issues with flutterflow web, especially on mobile web
FlutterFlow. Build it in public.
why not bubble 2:14
dart is just weird for web
mobile yes, web no.
Why?