| name | flutter-concurrency |
| description | Execute long-running tasks in background isolates to keep the UI responsive. Use when performing heavy computations, parsing large datasets, or choosing between async/await and isolates. |
| metadata | {"triggers":{"files":["**/*isolate*.dart","**/*worker*.dart"],"keywords":["Isolate","compute","Isolate.run","Isolate.spawn","ReceivePort","SendPort","background"]}} |
Dart Concurrency and Isolates
Priority: P1 (HIGH)
Core Concepts
Dart uses a single-threaded event loop. All Flutter code runs on the Main Isolate by default. Blocking it causes jank.
- async/await: For non-blocking I/O (network, file). The event loop continues while waiting.
- Isolates: Dart's lightweight threads with isolated memory. Communicate via message passing only.
Decision Matrix
| Condition | Approach |
|---|
| I/O bound (HTTP, database) | async/await on Main Isolate |
| CPU-bound, < 16ms | async/await on Main Isolate |
| CPU-bound, one-off heavy task | Isolate.run() |
| Continuous background processing | Isolate.spawn() with ports |
Workflow: Offloading Heavy Computation
Workflow: Long-Lived Worker Isolate
See examples for complete code.
Anti-Patterns
- No JSON parsing on Main Isolate: Large JSON decoding (>1MB) blocks frames. Use
Isolate.run.
- No shared mutable state: Isolates cannot share memory. Pass data via messages.
- No FutureBuilder in build without caching:
FutureBuilder re-fires on every rebuild if the future is created inline.
Verification
References
Canonical response anchors
When this skill applies, preserve the following domain terminology or equivalent concrete examples in the answer when relevant:
- Dart Concurrency and Isolates