abelsm

thanks! we wanted to put it out there and see if there's interest before investing more time in polishing it. it's been really helpful to see the discussion here.

Cofounder of FlutterFlow here. Not atm, as it started as an internal project. But it's something we're considering.

Awesome video. It's interesting, informative, and entertaining.

Founders I talk to that are doing hardware, broadly speaking, say it's a competitive advantage as it's not as crowded. Content like Aaed's will hopefully nudge more people into it.

Hi HN, I’m one of the founders of FlutterFlow (YC W21). We launched Dreamflow earlier this year.

What it is: Dreamflow generates a Flutter app from a prompt, then lets you keep working in a real dev environment with a visual editor, AI agent, and full code (code is the source of truth).

Why we built it: 1) make small changes dead simple: tweak properties, move widgets, add components without editing code or prompting; and 2) give the agent precise context: select a widget to add it to the prompt (screenshot included automatically); the agent has access to read runner logs.

What’s different:

- Bi-directional editing: canvas ↔ code; standard Flutter. - Runs in the browser: hot reload, preview. - Agentic edits with diffs; widget-aware context + log access.

How to try: Prompt: “Fundraising CRM for founders: pipeline (Targeted -> Closed); investors (name/firm/check size/intro source); notes + next steps + due date; goal $X/$Y; tabs Pipeline/Investors/Tasks/Settings”

Then preview, rearrange visually, integrate a backend or keep it local, and export/publish.

Current gaps: Visual coverage isn’t complete; GitHub integration is in progress; importing existing Flutter projects isn’t supported yet.

We’d love your feedback. Where does the visual editor help or get in your way? Which integrations would you expect first?

Agreed, making it more natural to create apps in a way that follows Flutter best practices is a desirable end goal. There's so much to improve, it's exciting :-)

It's not quite an apples-to-apples comparison, but the memory use of FlutterFlow is comparable to WebFlow. Our landing page is built using WebFlow, and I compared memory use of that to a comparably sized project in FF.

Performance could certainly be improved (especially for Web), but it's gotten much better over the last year.

thank you!

Thanks for the suggestions! Yes, there's definitely room for improvement with the generated code ... I think the padding -> SizedBox conversion at least in some cases (only when main-axis padding is added) can be automated. We can experiment with code improvement features such as that and see how it works.

Expanded + Percentages for widths are possible already

There were a lot of issues with custom widgets when we first launched the feature, we've deployed several fixes since then. But there's still more to do on our end to make it clear what errors you're getting. Thanks for the suggestion!