Skip to content
pubscout

Compare

The strongest value in each row is marked.

Attributeintegral_isolates

Easy to use isolates for Dart and Flutter using a long-lived isolate.

pub.devRemove
isolate_pool_executor

Manages a pool of Dart isolates to run CPU‑intensive tasks without blocking the main isolate.

pub.devRemove
ScoresHealth5058 (best)
Maintenance150 (best)
Quality96100 (best)
Popularity56 (best)22
Community46 (best)41
Compatibility8585
UsageDownloads (30 days)12k (best)610
Likes43 (best)18
Pub points150 / 160160 / 160 (best)
GitHub stars19 (best)13
MaintenanceLatest release0.5.1, 3 years ago2.2.2, 11 months ago (best)
Major versions in 12 months00
Contributors2 (best)1
Publisherlohnn.seaymtools.com
FitPlatformsAll (pure Dart)All (pure Dart)
WASM-readyNoNo
KindPure DartPure Dart
Code generationNoNo
Direct dependencies20 (best)
LicenseMITMIT
Setup effortLowLow
JudgementStrengths
  • Long-lived isolate execution avoids repeated spawn overhead
  • Built-in backpressure strategies to prevent memory exhaustion
  • Tailored stateful isolates for type safety
  • Reduces isolate creation cost by reusing them.
  • Highly configurable pool parameters (core size, max size, keep‑alive, custom handlers).
  • Supports Flutter MethodChannel usage in isolates.
Weaknesses
  • API is not final and is subject to change
  • Requires manual disposal of isolates to free resources
  • Adds complexity compared to plain compute() or async Futures.
  • Limited to Dart/Flutter; no built‑in task prioritization or scheduling beyond a simple queue.
  • Documentation is concise; advanced features may require reading source code.
WarningsNoneNone
integral_isolates vs isolate_pool_executor: which Flutter package should you use? | pubscout