r/FlutterFlow • u/Moumentos • Aug 11 '24
I stopped using FlutterFlow - and why you shouldn't
Hey Everyone,
I’ve been on quite a journey with development over the years. I started with Objective-C, transitioned to Swift, and spent a good chunk of my dev career building mobile apps. But recently, I’ve been diving deep into web development, learning Svelte and Go has taken up most of my focus. That’s why I stepped back from FlutterFlow.
But here’s the thing – if I ever return to mobile app development, and I will, FlutterFlow will be my first choice, hands down. The power and flexibility it offers to developers are unparalleled, and I’ve seen firsthand how it can accelerate the development process like nothing else.
Even though I’m currently focused on web projects, I’m still very much a part of this community. I’ll be here to help you out and answer any questions you have about FlutterFlow. Over time, I’ve noticed a lot of recurring questions and challenges that many of you face, so I decided to create a template that addresses these common pain points.
This template is designed to save you tons of headaches when setting up new FlutterFlow projects – whether it’s integrating Stripe subscriptions or setting up a custom API endpoint for your app. Everything is well-documented, so you can hit the ground running without getting stuck on the basics.
So, while I'm not using FlutterFlow for now, it’s a tool I’ll always come back to when mobile development calls. If you’re thinking about migrating your mobile app to the web, or if you’re looking to expand into web development, I’d love to chat and see how I can help you out on your journey!
Let’s keep building great things together! 💪