We’re looking for an App Developer with at least 1+ year of experience to help create smooth, high-quality applications. This role focuses on building reliable features, improving performance, and delivering a great user experience.

Details:

• $22–$42/hr (based on experience)

• Remote with flexible schedule

• Part-time or full-time available

• Develop, update, and maintain applications with attention to performance, usability, and security

Interested? 🚀📱

I’ve been developing an app with FF since 2024, the cross-platform capability was very convenient for me. However, I’ve recently been considering switching to native development with the help of AI, as FF now seems to be more of a hindrance than a help to my app's evolution not to mention the costs involved.

Have any of you gone through a migration like this? And what is your general take on FF these days?

I get the feeling they’re losing ground compared to what AI and low-code tools can offer for app creation.😕

PS: my app has thousands users so the decision is for me very important, that's why Im asking about your opinion.

FlutterFlow: Stop breaking existing production apps with forced “security” changes

I’m seriously fed up with FlutterFlow.

I have an existing production app that has been working with FlutterFlow and Supabase for a long time. Today I open the project after a FlutterFlow update and suddenly I have 12 project errors because FlutterFlow now flags my Supabase anon key in API headers as an “Exposed API Credential”.

This is a Supabase anon/public key. It is specifically designed to be used in client applications. Security is enforced by the user JWT, RLS and backend permissions. This is not a service_role secret.

Nothing in my application changed.

Nothing in my backend changed.

The exact same API calls have been working for months.

But FlutterFlow changes its validation rules and suddenly an existing production project is treated as broken — AGAIN AFTER A FLUTTERFLOW UPDATE! - potentially preventing me from building or releasing the app until I restructure API calls that did not need restructuring in the first place.

This is not acceptable for a production development platform.

Security improvements are welcome. Breaking existing projects without migration, grandfathering, an override, or even recognizing legitimate public credentials is not.

If FlutterFlow wants to warn me: fine.

If FlutterFlow wants to explain a better configuration: fine.

But turning a previously valid production configuration into hard project errors after a platform update is a breaking change.

And this is not the first time FlutterFlow changes something underneath existing projects and developers are left cleaning up the consequences.

A development platform that hosts production applications needs to provide stability. Existing projects cannot constantly become unbuildable because FlutterFlow decides to introduce another mandatory rule after the fact.

At minimum FlutterFlow needs:

• a distinction between public client keys and actual secrets
• a migration path for existing API calls
• warnings instead of hard errors where appropriate
• an explicit override for legitimate client-side credentials
• clear release notes before introducing build-breaking validation

Developers should not open a working production project in the morning and discover that the platform has arbitrarily created a dozen new errors.

Stop introducing breaking changes into existing production projects without a proper migration path.

I SHOULD NEVER, EVER HAVE STARTED USING THIS F*** APP!

Hi everyone,

Also woke up to a surprise with the FF update!

Anybody find a fix for Supabase api's without doing this whole Firebase thing?

If not, should I be patient until a fix is deployed?

TIA

My test app launches to a blank screen. It compiles successfully, and I’m not receiving any error messages, but no content is displayed. Has anyone encountered this issue or know how to resolve it? I contacted support but have not yet received a response.

Hi everyone,

I'm looking for advice from developers who have experience with both FlutterFlow and pure Flutter.

I'm building an AI-powered journaling app.

Current setup:
- FlutterFlow
- Firebase
- GitHub
- AI agents (Cursor, Codex, Claude Code)
- Around 35+ screens
- A lot of custom Dart code
- My goal is to keep developing mostly through AI agents by writing prompts.

I’m a solo founder, so I care a lot about long-term productivity and AI-assisted development.

I'm at a point where I'm wondering whether I should:

A) Stay with FlutterFlow and continue using its AI + custom code.

or

B) Export the project and continue entirely in pure Flutter.

My priorities are:
- Long-term maintainability
- Working efficiently with AI agents
- Scalability
- Code quality
- Development speed
- Avoiding unnecessary technical debt

If this were your startup, what would you do?
If you’ve actually migrated a medium or large FlutterFlow project to pure Flutter, how long did it take and would you do it again?

I'm especially interested in hearing from people who have actually migrated from FlutterFlow to Flutter (or decided not to).

Thanks!