I found myself working on FF after deciding to use Firebase for auth/principal data. I started using react/native on VS Code and relying a lot on Github Copilot. (I have written code and am a technical product exec who at least knows what good code and architecture looks like, which helps a lot working with AI-generated code.) But then I 'chickened-out' (j/k) on writing front-end code and auth functions from scratch. And there are hypotheses about the service I'm developing that involve both mobile and web use assumptions, so unified build sounded pretty good to me...even if we split things up in future after production refactoring (or maybe not!). So FF it is! I'll admit that in a way it would have been faster for me to not add a learning curve around a new tool atop the learning curve of developing from scratch, and AI is much less helpful when I run into snags on figuring out how to do something in FF. Everything from C-GPT to Phind will come back typically with code (dash or js) unless I hector them to remember to give me the visual builder worksteps, which they often don't know and revert to general 'common sense' instructions that clearly show they don't have the knowledge on how to implement things in the visual tool. So...that was an interesting eye-opener. That said, the more adept at FF I get with each new instructional video on YouTube, the happier I am about the choice. It's the way I like to work...wysiwyg. When FF handles secret manager without requiring from-scratch cloud functions and custom code and manually configuring google secret manager -- and when you can get a github sync that you can modify and see changes (or errors saying "you did something we don't like") in FF, rather than a one-way export -- I'll have very few things preventing me from telling everyone in enterprise development that FF is the way to go.