flutter-architecture

Structure a Flutter project using a feature-first folder layout that separates responsibilities into presentation, domain, and data layers. This defines clear rules for provider placement and UI layering when using Riverpod and Supabase.

Organize Flutter features by grouping them into lib/features and core layers like data, domain, and presentation. This feature-first standardizes code organization across teams, making new feature creation and large module refactoring faster.

Separate Flutter layers by assigning UI and state to presentation, business rules and models to domain, and data access with DTOs and mappers to data. This separation of concerns ensures maintainability and clear architectural boundaries.

Yes, this Flutter architecture template works for onboarding developers by providing documented project structure guardrails. Applying these architectural conventions helps new team members scaffold features consistently without violating separation of concerns.

Apply this Riverpod architecture template when starting new features, refactoring large modules, or onboarding developers to a Supabase-based Flutter app. It provides specific rules for provider placement and UI layering to ensure codebase scalability.

Place Riverpod providers according to the defined feature-first architecture template, which specifies provider placement rules within the presentation, domain, and data layers. This ensures state management integrates cleanly without breaking separation of concerns.