Orientação gerada a partir de informações públicas. Apenas para referência.
Flutter Modular é um framework poderoso para organizar aplicativos Flutter com uma estrutura de projeto inteligente, injeção de dependência embutida e gerenciamento centralizado de rotas. Ele promove arquitetura limpa ao separar preocupações por meio de módulos, tornando aplicativos em grande escala mais fáceis de manter e escalar. O pacote simplifica a navegação entre telas e gerencia dependências automaticamente, reduzindo o código repetitivo. Com suporte em todas as principais plataformas, permite fluxos de trabalho de desenvolvimento consistentes desde mobile até web e desktop. Seu design modular incentiva colaboração em equipe e testabilidade.
Casos de uso
Aplicações Flutter em grande escala
arquitetura de aplicativo modular
Injeção de Dependência
roteamento centralizado
Desenvolvimento baseado em equipe
Consistência entre plataformas
Principais recursos
Injeção de dependência embutida
Arquitetura baseada em módulos
Gerenciamento automático de rotas
Suporte para todas as plataformas
Navegação fácil
Separação clara de responsabilidades
Indicado para
Desenvolvedores construindo aplicativos complexos no Flutter
Equipes que precisam de organização estruturada de código
Projetos que exigem arquitetura escalável
Aplicações destinadas a múltiplas plataformas
Desenvolvedores que querem menos código boilerplate
Considerações
Curva de aprendizado mais acentuada para iniciantes
Requer compreensão de padrões de design modulares
Pode adicionar sobrecarga para projetos muito pequenos
Recursos comunitários limitados em comparação com pacotes principais
README original
Snapshot do README original do repositório-fonte vinculado. Consulte o repositório para o conteúdo mais recente.
Flutter Modular
A smart, modular project structure
Route management, dependency injection and scoped state — organized by feature, the Flutter way.
Let's find out how to implement a Modular structure in your project.
What is Modular?
Modular proposes to solve two problems:
Modularized routes.
Modularized Dependency Injection.
In a monolithic architecture, where we have our entire application as a single module, we design our software in a quick and
elegant way, taking advantage of all the amazing features of Flutter💙. However, producing a larger app in a "monolithic" way
can generate technical debt in both maintanance and scalability. With this in mind, developers adopted architectural strategies to better divide the code, minimizing the negative impacts on the project's maintainability and scalability..
By better dividing the scope of features, we gain:
Improved understanding of features.
Less breaking changes.
Add new non-conflicting features.
Less blind spots in the project's main business rule.
Improved developer turnover.
With a more readable code, we extend the life of the project. See example of a standard MVC with 3 features(Auth, Home, Product):
What we did in this structure was to continue using MVC, but this time in scope. This means that
each feature has its own MVC, and this simple approach solves many scalability and maintainability issues.
We call this approach "Smart Structure". But two things were still Global and clashed with the structure itself, so we created Modular to solve this impasse.
In short: Modular is a solution to modularize the route and dependency injection system, making each scope have
its own routes and injections independent of any other factor in the structure.
We create objects to group the Routes and Injections and call them Modules.
Ready to get started?
Modular is not only ingenious for doing something amazing like componentizing Routes and Dependency Injections, it's amazing
for being able to do all this simply!
Go to the next topic and start your journey towards an intelligent structure.
Common questions
Does Modular work with any state management approach?
Yes, the dependency injection system is agnostic to any kind of class
including the reactivity that makes up state management.
Can I use dynamic routes?
Yes! The entire route tree responds as on the Web. You can use dynamic :params,
query strings, relative paths, nested routes and persistent shells (RouterOutlet).
Use a route guard to redirect (e.g. to a 404 or a login page).
Do I need to create a Module for all features?
No. You can create a module only when you think it's necessary or when the feature is no longer a part of
the scope in which it is being worked on.
✨ Usage
flutter_modular 7 is a ground-up rewrite. A Module is now exactly the two things that couple a Flutter app — Dependency Injection + Routes — declared with a small functional API. State is page-scoped, tied to the route lifecycle, so ownership and disposal stop being your problem and the durable truth lives in a repository/service registered in DI. Full, runnable demonstrations (nested routes, RouterOutlet shells, route guards, per-module DI lifecycle, arguments/pop-results) live in example/.
Install
dependencies:flutter_modular:^7.0.0
or run flutter pub add flutter_modular.
Declare a module
A module groups routes and dependency injection. Shared dependencies are registered with addSingleton/add*, routes with route(...), and submodules with module(...).
context.pushNamed('/details/42'); // stacks a page (push stays out of the URL)
context.navigate('/'); // replaces the stack (owns the URL, resets history)
context.pop(result); // pops, delivering a result to the awaiting pushNamed
Page-scoped state
State lives 1:1 with a view via provide — built in a page-local scope and disposed when the route leaves, so there are no floating globals and no manual dispose.
c.route('/counter',
provide: (s) => s.addChangeNotifier<CounterViewModel>(CounterViewModel.new),
child: (ctx, state) => constCounterPage(),
);
// inside the page:final vm = context.watch<CounterViewModel>(); // rebuilds when the VM notifies// granular: rebuild only when the selected value changes (provider-style)final count = context.select<CounterViewModel, int>((vm) => vm.count);
🧑💻 Contributing
Contributions are what make the open source community such an amazing place to learn, inspire, and create. Any contributions you make are greatly appreciated.
If you have a suggestion that would make this better, please fork the repo and create a pull request. You can also simply open an issue with the appropriate tag.
Don't forget to give the project a star! Thanks again!
Fork the Project
Create your Feature Branch (git checkout -b feature/AmazingFeature)
Commit your Changes (git commit -m 'Add some AmazingFeature')
Push to the Branch (git push origin feature/AmazingFeature)