{"repo":"ShadyBoukhary/flutter_clean_architecture","free":true,"listed":false,"github":"https://github.com/ShadyBoukhary/flutter_clean_architecture","clone":"git clone https://github.com/ShadyBoukhary/flutter_clean_architecture.git","description":"Clean architecture flutter: A Flutter package that makes it easy and intuitive to implement Uncle Bob's Clean Architecture in Flutter. This package provides basic classes that are tuned to work with Flutter and are designed according to the Clean Architecture.","language":"Dart","stars":735,"topics":["clean-architecture","clean-code","flutter","dartlang","flutter-package","design-pattern","uncle-bob","dart","dart2","hacktoberfest"],"license":"MIT","category":"mobile-apps","readme_excerpt":"flutter clean architecture Package Overview A Flutter package that makes it easy and intuitive to implement Uncle Bob's Clean Architecture in Flutter. This package provides basic classes that are tuned to work with Flutter and are designed according to the Clean Architecture. Installation 1. Depend on It Add this to your package's pubspec.yaml file: 2. Install it You can install packages from the command line: with Flutter: Alternatively, your editor might support flutter packages get . Check the docs for your editor to learn more. 3. Import it Now in your Dart code, you can use: Flutter Clean Architecture Primer Introduction It is architecture based on the book and blog by Uncle Bob. It is a combination of concepts taken from the Onion Architecture and other architectures. The main focus of the architecture is separation of concerns and scalability. It consists of four main modules: App , Domain , Data , and Device . The Dependency Rule Source code dependencies only point inwards . This means inward modules are neither aware of nor dependent on outer modules. However, outer modules are both aware of and dependent on inner modules. Outer modules represent the mechanisms by which the business rules and policies (inner modules) operate. The more you move inward, the more abstraction is present. The outer you move the more concrete implementations are present. Inner modules are not aware of any classes, functions, names, libraries, etc.. present in the outer modules. They simply","default_branch":null,"files":null,"tree":[],"storefront":"/r/ShadyBoukhary","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/ShadyBoukhary/flutter_clean_architecture/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}