flutter-architecture

Provides architectural guidance and best practices for building scalable Flutter applications using MVVM pattern, layered architecture, and recommended design patterns from the Flutter team. Choose the right project organization based on your app's complexity and team size. Organize code by business features: When to use: Benefits: See Feature-First Guide for complete implementation details. Organize code by architectural layers: When to use: Benefits: Start with these core concepts: For detailed concepts, see Concepts . Flutter apps should be structured in layers: See Layers Guide for detailed layer responsibilities and interactions. Common patterns for robust Flutter apps: See Design Patterns for implementation details. Use this skill when: - Medium to large apps (10+ features) - Team development (2+ developers) - Frequently adding/removing features - Complex business logic - Features are self-contained units - Easy to add/remove entire features - Clear feature boundaries - Reduced merge conflicts - Teams work independently on features - Small to medium apps - Few features (<10) - Solo developers or small teams - Simple business logic - Clear separation by layer - Easy to find components by type - Less nesting - Separation of concerns - Split app into UI and Data layers - MVVM pattern - Use Views, ViewModels, Repositories, and Services - Single source of truth - Repositories...