FlutterFlow Reviews

Currently, I am using Flutter to make a dashboard.

I like the simplicity of making panels with Flutter. It is easy to use when you understand the code, know how to use Docs, and understand the components of Flutter. It allows you to create fragments that look good and work on both mobile and web environments. Additionally, it works for both PC and iOS devices.

Right now, I think it's a good tool. It's easy to understand when you know Dart. It helps create applications, and I am trying to see how it can be integrated with the backend. That said, I haven't gotten there yet.

Currently, I have been using it for a month.

I have not faced any issues with bugs or breakdowns so far.

Scaling depends on project requirements. It's easy to scale in certain projects, but if the project gets too complex, it might not be the best choice.

I have not had to contact their support team. I have only used the documentation and courses.

Positive

The setup is easy. You can follow Google's documentation. It's not complex.

I recommend anyone start with courses and understand Dart. Knowing how to use Dart helps you use Flutter. Understanding Dart classes will help in matching every component in Flutter.

I'd rate the solution eight out of ten.

FlutterFlow is more focused on mobile app development rather than website development. With it, I can create mobile apps for various purposes. For example, I can use it to build an app for onboarding customers, where I collect their ID details, verify them, and then create a lead or offer personalized services. It is more about creating engaging and functional mobile experiences rather than traditional website development.

The most valuable features of FlutterFlow are the integrations and workflows. Being able to define workflows based on database status codes, set up validations, and integrate seamlessly with other tools makes app development much smoother. It is like having built-in functionality similar to Adobe Forms but without the need for extensive coding. This simplicity and ease of integration are what I appreciate the most.

There is room for improvement in advanced functionality so it could cater to more complex app development needs. Additionally, I would like to see improvements in enhancing its IDE to offer more capabilities similar to its web platform. This would improve offline coding experiences and reduce dependence on bandwidth, making development even smoother.

I have been working with FlutterFlow for three months. 

I would rate the stability of FlutterFlow as a nine out of ten.

The product is scalable depending on deployment architecture, but collaboration features could be improved. I would rate the scalability as a seven out of ten. 

Around 10 to 12 users in our company are currently using FlutterFlow, and we use it every day.

I would rate the support as an eight out of ten.

Positive

I would rate the easiness of the initial setup as an eight out of ten. It is quite straightforward.

For deployment, we have a centralized team of around 250 people who handle multiple projects, including FlutterFlow. The initial deployment of the solution took about three months to get a good MVP ready for rollout. Our deployment process involves generating code, which then goes to GitHub. GitHub actions handle validation and quality checks, followed by a proprietary CI/CD process that involves image validation and deployment to an AWS repository. From there, it is ready for use. 

We integrate FlutterFlow into our app development process by first developing the code using the enterprise ID. Once the code is ready, we preview it and then download it. We have built a CI process where the code, once pushed to the gate, is processed by CI actions to generate the appropriate output, whether it is an IPA or APK file. While FlutterFlow currently focuses on website development, we write the code in a way that allows us to adapt it for mobile apps as well. We maintain a unified codebase for all three platforms, ensuring consistency and efficiency in our development workflow.

FlutterFlow accelerated my development timeline on a project where I needed a simple website with basic navigation and form submissions. While it lacks advanced design pattern options and some features are still maturing, it simplifies integration and speeds up development.

FlutterFlow's UI design capabilities have significantly impacted my app development by allowing me to communicate marketing concepts more effectively through visual flow.

Every feature in FlutterFlow, from screen design to integrations, has been valuable for my development efforts. However, having better support for multiple design patterns and ensuring compatibility with custom changes would greatly improve the development experience.

Overall, I would rate FlutterFlow as an eight out of ten.

I use it as a personal assistant application. I use several tools; for the front end, I start with FlutterFlow. For the back-end, I use two other tools: Firebase and Supabase. Firebase handles the database and some application logic through Firebase Functions. Security is also managed through Firebase. 

However, for the really large dataset, I use Supabase, which is essentially the Postgres version in the cloud. It's great for organizing frequently accessed data like customer information or the latest updates, which wouldn't be ideal for the main Firebase datastore.

It accelerates development time by addressing many environmental issues automatically. Using Flutter means everything works well on both iOS and Android without needing to duplicate development efforts. It is a huge advantage for me and it offers many out-of-the-box features as well. 

The ability to connect the backend service and the improvements with Supabase were significant. It's a good direction for collaboration.

FlutterFlow offers a lot, but one feature that really helps me is the debugging features that allow me to test everything on the spot. This is really helpful. 

Another aspect that I find useful, though not unique to FlutterFlow, is the ability to use multiple data sources, such as Firebase and Supabase. This means I can have two backends and use them in one application. It's not just about connecting them; it feels like a multiplication of power when using these two backends together. You can integrate more than one backend. 

Another valuable feature is the testing capability that allows me to test everything on the fly, which significantly improves the quality and speed of the development process.

For my development efforts, the vast amount of components that are readily available and fit my needs stands out. FlutterFlow has a large, suitable library of components that I can use right out of the box. I don’t have to create new ones at all. If I need to create something with a variation, I can take an existing component and immediately make it a template.

The UI components could be more standardized. Sometimes, for certain properties, I have to search more than I do with other platforms. With other platforms, once you know one, you know all. But with FlutterFlow, sometimes you have to look around for what you need.

The properties of different objects or controls should be standardized. There needs to be some uniformity.

Moreover, integrating permissions management could be improved, especially since I'm using two backends. It would be beneficial to edit the name of permissions for a form once rather than separately for each backend. If FlutterFlow could handle permission management more seamlessly, it would greatly simplify the process, but currently, this feature isn't fully developed.

I use the platform whenever possible. I use the cloud version, so it's always the latest.

With the experience I have, I'm happy with the stability. 

I would rate the stability an eight out of ten.

Our usage is currently very low. So, I don't have enough experience with massive usage to rate its scalability accurately.

There are just two of us in my company who use it to create and deploy applications. 

About 30% of my time, I use it in my development processes. 

I occasionally use the community for support. 

I haven't tested the support directly, but from what I've seen in the community, the support seems adequate.

Positive

I used Mendix and a few other tools for local development. I decided that differentiating the backend was important, which led me to choose cloud components, including Firebase, for building with a backend service.

For me, it was okay. I would rate my experience with the initial setup a nine out of ten with ten being easy to deploy. 

Compared to other low-code platforms, it is easy. For simple applications, it's very good for most users or developers. 

The integration might be more complex for those extending or integrating with their organizational backend rather than starting anew. But from scratch, it's not an issue. It becomes more challenging when integrating existing systems.

Only two people were involved in the deployment process. 

The deployment time depends on the version timing. For version changes, once it's ready, it only takes a few minutes. '

Once the application is ready, deploying with FlutterFlow is straightforward since we're already integrated with GCP, where both the application and database reside.

We're two people handling the maintenance process.

I find the pricing quite fair. I would rate the licensing costs a three out of ten, with ten being expensive and one being cheap.

Currently, I use the free versions, but I expect some costs as we scale.

For now, I'm on the free plans. Once we go live and scale up, there will be costs, but compared to competitors, FlutterFlow and its database costs are below average.

FlutterFlow was a deliberate choice. After evaluating several options, FlutterFlow stood out for our needs.

Mendix was one option, known for its success in local development. Besides, I could develop directly on FlutterFlow or opt for a split approach, using separate tools for the frontend and backend. Depending on the phase of development, especially in the early stages of a startup, the initial development approach needs to be strategic.

The robust architecture of FlutterFlow serves as a comprehensive organizational solution. It facilitates service connectivity without taking on data management responsibilities directly. This combination assures me that we're well-prepared for scaling up. Thus, I'm confident in our ability to handle a significant user load and provide adequate support through the growth phase.

Good design is essential. Don't fall into the trap of thinking you can skip design and jump straight into development. Using local development tools won't help you much here. You still need to solidify your design before coding begins.

There's also a misconception that if you work with low-code, you can bypass testing entirely with FlutterFlow. It's tempting because building seems faster initially. However, I found myself in a situation where frequent builds eventually broke the application due to accumulated changes. It became a cycle of rebuilding and fixing, essentially starting from scratch each time.

My suggestion: Stick with established design tools like Figma or Microsoft Designer to define your screen layouts, data structures, and everything else. Then, move to FlutterFlow for a more organized and documented development process.

Overall, I would rate the solution a nine out of ten.