Flutter Deer: a production-shaped practice project

Not every learning repo ages well. Deer remains useful because it shows a complete app skeleton: flavors, common components, integration tests, and a shop domain that is boring on purpose.

What to copy

• Feature folders over layer-only mega-folders at scale.
• Shared widgets library with design tokens/mockups in-repo.
• Integration tests as part of “done.”

What to update

State management opinions have moved (Riverpod/bloc/etc.). Keep Deer’s structure, refresh the state layer for your team.

Pitfalls

Do not paste UI without extracting design tokens. Templates rot when they hardcode API hosts.