flutter-motion-engineering
Flutter Motion Engineering
Purpose and evidence policy
Engineer motion that communicates state, follows input, survives interruption, and delivers consistent frames. Treat Apple quality as continuity, restraint, and responsiveness, not an instruction to copy iOS styling onto every platform. Accessibility and correctness are acceptance gates, never optional performance tradeoffs.
Evidence labels used below: D = documented framework behavior; P = platform/version-specific guidance; E = engineering recommendation or inference. Selection tables and validation procedures are E unless stated otherwise. Distinguish confirmed defects, measured bottlenecks, plausible risks, and optional refinements in reviews.
Check flutter --version --machine, SDK constraints, lockfiles, and the actual renderer before applying version-sensitive advice. Official documentation is rolling: some pages still identify Flutter 3.44.7 while individual sections describe 3.47; API footers can show 0.0.0. Use the installed SDK source or a matching release tag to resolve conflicts. Do not infer a minimum supported version from a rolling API page.
Bundled reference routing
Read the core workflow first, then load only the supporting material required for the task.
| Task | Reference |
|---|---|
| Gesture state, velocity, retargeting, geometry changes, route ownership | Interaction protocols |
| Baseline capture, stage diagnosis, rendering experiments, evidence reporting | Profiling playbook |
| Runnable examples, regression coverage, integration gates, validation limits | Testing and examples |