Organizational patterns
Identical scaffolding across both architectures
The dependency rule (CA) and the module pattern (GetX) tell you where business logic goes. This chapter covers what comes before that — the scaffolding every Flutter project needs regardless of architecture. AssetsData, AppColors, AppTheme, LocalStorageService, NetworkInfoService, constants discipline, splash flow, widget organization, naming conventions, day-1 project checklist. When you open a new Flutter project on Monday, the LANDMARKS should be identical. Only the contents differ.
Tokens
Assets · Colors · Theme
AssetsData — paths as types
Never type a raw asset string
AppColors + AppTheme
Tokens at one address
Services
Prefs · Network info
LocalStorageService — preferences as types
Predefined keys, typed accessors
NetworkInfoService — single source of truth for connectivity
Online · Offline · Poor
Flow
Splash · Naming · Widgets
Splash flow — every production app has one
Branding · Init window · Auth check
Widget organization
Local first, promote on second use
Naming conventions
Pick one — apply everywhere
Discipline
main.dart · pubspec · checklist
main.dart discipline
Every line is a step with a reason
pubspec.yaml discipline
Adding a dep is a decision
Day-1 project checklist
Identical for both architectures
Sections
· click any card to expandApple Pencil draws with pressure. Fingers still scroll. Saved per pillar.