Kenji Morisaki

FlutterFlow9 August 2026

I bill for Flutter work and this is where I start it

One project, both stores, and the source export is real Flutter I can open and extend when the visual editor runs out. I have delivered four client apps this way and handed the repository over each time. Web output is heavy, so I do not use it for anything that needs to be found in search.

Draftbit9 August 2026

A pleasant head start on React Native screens

If your team is committed to React Native rather than Flutter, this saves the boring part and gives you a normal Expo project afterwards. The editor maps cleanly onto component structure, which most visual tools get wrong. My concern is momentum, not quality: the changelog has been quiet.

Adalo29 July 2026

A client asked me to rescue one and I could not

Their app had grown to about forty screens and performance was unacceptable on mid-range Android devices. There is no export, so there was nothing to optimise and nothing to migrate. We rebuilt in FlutterFlow over six weeks. Fine for a prototype, and a trap if the prototype succeeds.

Rork29 July 2026

Prototype tool with production marketing

Impressive for a first pass. Once I introduced shared state across five screens it started contradicting itself and I spent longer correcting it than writing it myself would have taken. Export is genuine and that saves the situation. Treat production claims with the caution any 2025 product deserves.

a0.dev29 July 2026

Perfect for two days, wrong for two months

Superb for exploring an idea, and I keep it for exactly that. There are no integrations worth the name, no API, and no collaboration, so a second person joining is where it ends. Export gives you an Expo project to continue elsewhere, which is the right escape hatch.

Agreed on the speed. Watch what happens when you add authentication and shared state, that is where my enthusiasm cooled.