9/23/2023 0 Comments Flutter firebase course![]() Which one do you recommend or prefer (from like the Flutter Architecture Samples’ examples)? Also, as flutter was initially built for mobile apps in reactive programming in mind, that needs some different type architectural patterns than the old MVC/MVP/MVVM etc., so like RxVM /w RxCommand (for example achieving to retrieve only read-only data from some underlying cache/db i.e. How would you split a complex app to different dart or flutter packages by the used services/features/storyboards (like in Flutter Architecture Samples, though it has only a very simple splitting to only repository or like services in ).Ĥ. What is your thoughts on some hybrid style development like TDD+BDD+DDD in flutter?ģ. Do you prefer TDD + Clean to DDD in flutter?Ģ. Why do bother creating dozens of separate UseCase classes?Īll my respect, you’re one of the very rare species in the Developers community who is seeking for deep understanding and try to find the best and simple solutions and ofc thanks all your tutorials.ġ. UI listens to the state changes (enum for instance) and rebuilds itself correspondingly. So what’s the difference if instead BLoC class we have ChangNotifier class? It gets business logic streams and inputs from UI (by calling its methods), decides what’s the next state should be and yield the states by calling notifyListeners() or emit Stream events. ![]() UI listens to the state changes and rebuilds itself correspondingly. You get the streams of changes and Events from UI there and decide what’s the next state should be and yield it. Learn more from the mysterious uncle.”Īs far as I know, it’s recommended to have one BLoC class for each page. I’d recommend creating reusable, one-purpose UseCase classes. “If you’re not using BLoC, do yourself a favor, and don’t put the application logic into View Models. My concern is about Application layer for those who use BLoC and those who use for instance ChangeNotifier + Provider with MVVM pattern. ![]() Notice that splash folder in the presentation layer? There is no inherent "splash screen logic", so it doesn't make sense to put it into other layers.Īll in all, we can mix and match the dependencies in between features as long as we keep true to the dependency flow outlined in the diagram above ( domain layer has to have ZERO dependencies on other layers). It's also worth noting that some features don't even have to necessarily be represented in all layers. What does this mean? Well, we can have both a good folder structure and a separation into architectural layers at the same time □□ ![]() While the main notes folder is present inside every layer (application, domain, infrastructure, presentation), its subfolders are different! This will still keep the code readable but, most importantly, it will ensure that adding more features and sub-features is going to be a pure bliss! Layers will hold features, not the other way around. With DDD, we're going to take a different approach. I'm the first to admit that the folder structure outlined in the Clean Architecture course is a pain to deal with. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |