Flutter Squadron Concurrency Engineering

Mission

Move only the right computation off Flutter's main isolate, using the smallest justified worker boundary, message volume, concurrency, and lifecycle cost. Use this decision loop:

measure the slow stage
→ classify CPU vs I/O
→ estimate transfer/startup cost
→ choose main/Future/compute/Worker/Pool/server
→ define coarse worker API + wire types
→ bound concurrency/backpressure
→ add cancellation + stale-result protection
→ own worker lifecycle
→ test native and web separately
→ profile end-to-end + UI frames + memory/thermals

Squadron is structured worker/RPC infrastructure, not a generic wrapper around every Future.