Skip to main content

Architecture

Purpose​

  • Define how Flutter applications are structured

Covers​

  • Repository structure
  • File organization
  • Component definitions
  • Component interactions
  • Where business logic lives
  • Separation of UI and logic
  • Data flow patterns

Repository Structure​

  • Group files by feature or capability
  • Avoid deep nesting that hides key files

When to Use Subfolders​

  • Use subfolders when a feature grows beyond a few files
  • Keep structure easy to scan before optimizing for purity

Example (Flutter, short):

lib/
  features/
    profile/
      data/
      ui/