Alternative to FlutterFlow, ApparenceKit

Due to the infancy of the platform, FllutterFlow can be buggy. Unfortunately, the support function is severely lacking. It is not uncommon not to hear from them for days or on some issues, especially if the problems are relatively complex. This is on paid plans. Hoping they get the bug issues under control soon so they can focus a bit more on support.

it may not be suitable for complex applications. Since the platform is based on pre-built components, it may not be able to handle advanced customizations or complex features. Additionally, since the platform generates code automatically, developers may not have as much control over the final codebase.

...Having to redo screens that where working and then stopped for what seemed to be minor changes. I have been downloading the code from GitHub and haven't yet but want to compare the working code with the non-working code to see what is what..

...We want them to stop churning out new features and start fixing bugs. Every time they release a new update, it invariably breaks things in our application that we then have to track down and fix. We lose time and money every time we hit a bug in their interface that requires us to tunnel around it. We lose time and money every time something breaks on which we've come to depend, requiring us to find a new solution.

...The features are really limited. You still have to code for certain features.

...If you have a simple CRUD app, that is mostly fetching and creating data I think it's ok to use it, you can still export the code later and make some changes. If you have a more complex UI and app I would not use it, i will take more time to figure everything out, not to mention that if build all your code with Flow I can be hard to maintained later as your app and feature growth. So in short, I will not use it for complex app.