Michael Bushe 💙🧘‍♂️🌎⚾

Michael Bushe 💙🧘‍♂️🌎⚾

Users
Tweets

@michaelbushe

13 May 2025

My apologies, I should not write at 2AM. UseCases should not depend on presenters. Got a repo I can look at? This presents the typical problem when you're applying Uncle Bob's CA to Flutter. It just makes it too complicated. I often follow some level of clean architecture, usually at the higher levels but the more you throw out the better. KISS - Keep it simple, silly. This often results in disgruntled people on the team thinking there should be more complexity. 🙂 I don't think you need a controller and a presenter. And both are bets inside the widget. I use to give talks in MVC, MVVM, etc in various UI platforms. The point of the talk is "it's all BS." It's too simple and doesn't give the whole picture, things are often misnamed. In all platforms. In Flutter it's even worse. It sounds like you are intentionally trying to show all layers, that's the point of your exercise. So the way you could go that is have the UseCase passed to a presenter, presenter passed to controllers (StatefulWidget?) and the View is a StatelessWidget. Each later calls functions on the other. That'd a lot of work. Another great way to detangle the mess is to use FlutterBus to decouple each part from each other and just use the event as the router of the messages. (Or my formerly popular Swing EventBus for Swing) Because "widgets all the way down" this really makes no sense at all in Flutter, despite the bazillion blog posts on how it does. In Swing it would make sense, kinda, the component has a controller. Higher level useCases can compose them and you pass references around. In C#, MVVM is beautiful. Again, there's a composition of UI components by other code. It's procedural and not declarative. In Flutter, you declare Widgets. It's not a procedural paradigm like Swing or C#. The entire build method and all the methods it depends on, is a controller, but you don't have to name it. YAGNI - You ain't gonna need it - adding in more layers just adds unnecessary complexity. A StatefulWidget already has a model and its methods are the presenter or controller, whatever you might call it, adding in another layer shifts away from the beauty that is flutter. The view and controller/presenter is a Widget, similar to Swing (not surprising since Dart comes from Java and was led by many of the same people). Beyond the widget tree, there's only reactive state that's not in a widget. A BLoC, Cubit or Provider (Riverpod) is passed to the widget. The widget updates the state and the useCase reacts. So your widget calls ref.read(incrementUseCaseProvider).call(), the use case does its thing, and state is updated. The updated state triggers The rebuild, the widgets rebuilds declaratively. No Presenter. No Controller. Clean and idiomatic.

Ahmed Abu_eldahab 💙

Ahmed Abu_eldahab 💙@dahabdev

20 Feb 2020

بسم الله توكلت على الله Heading to Saudi Arabia #GDR 8000 km of travelling in one week 6 @FlutterDev talks 5 cities see you all soon :) @abid_salim @nlycskn @Omranic @GCDCSaudi @GoogleDevExpert @FlutterEgypt #Flutter #FlutterBus