@caseycrogers Iβve used them a lot too, both in Flutter and React and I abandoned them on Flutter after having to onboard some devs to use them. They just feel too alien in a Flutter codebase and are so easy to mess up with
@caseycrogers Also async handling goes beyond just forms too. Internally standardising (as much as possible) loading, success + error states and just overall async flow in general is a must
@caseycrogers I'd also argue StatefulWidgets aren't tedious for init/disposal compared to the extra complexity of another abstraction layer, I actually have grown to quite like the in your face explicit lifecycles compared to something like hooks
@caseycrogers I'm all for abstracting the logic into functions/classes outside the widget, just not the part that directly interacts with the form or other ephemeral state. Flutter already handles that well within widgets - adding extra controllers just adds unnecessary boilerplate
@caseycrogers imo a form controller here creates unnecessary indirection when Flutter already has built in support for forms and local state, so you're just fighting the framework π