How do you handle CPU-bound tasks without freezing the Flutter UI?

WHAT THIS TESTS: The interviewer wants to know if you understand the difference between concurrency and parallelism in Dart. Async and await handle I/O bound work by yielding control back to the event loop, but they do not create new threads. CPU intensive tasks like image decoding, heavy JSON parsing, or mathematical computations will block the UI isolate if run directly. You must demonstrate knowledge of Isolates as Dart's unit of parallelism and know that compute simplifies their use.

A GOOD ANSWER COVERS: First, clarify that Dart code runs in an isolate with a single event loop and memory heap. Async await merely pauses function execution until an I/O future completes, allowing other events to process, but all code still runs on the same thread. Second, define an Isolate as an independent worker with its own memory heap and event loop. Isolates do not share mutable state; they communicate strictly by passing messages through ports, which makes them safer than traditional threads but requires serialization overhead. Third, explain that spawning an isolate manually involves ReceivePort, SendPort, and message handling boilerplate. Fourth, describe compute as a high level utility function that wraps Isolate.spawn. It accepts a top level or static function and its argument, runs it in a new isolate, and returns a Future containing the result while automatically managing ports, message passing, and error propagation.

COMMON WRONG ANSWERS: A red flag is suggesting Future.delayed or a Timer to unblock the UI; these merely schedule work later on the same thread. Another mistake is claiming that async await automatically moves work to a background thread. Some candidates suggest running CPU work inside a Stream or StreamTransformer, which does not parallelize execution. Confusing isolates with web workers is acceptable in concept but you must know they are Dart specific constructs. Also, stating that compute uses a thread pool is incorrect; it spawns a new isolate per call.

LIKELY FOLLOW UPS: The interviewer may ask when to use an isolate directly instead of compute. You should answer that manual isolate management is needed for long lived workers, bidirectional communication, or when you need to spawn multiple isolates and reuse them. They might ask about the performance cost: isolate spawning takes milliseconds and message passing requires copying data, so isolates suit heavy batch work rather than trivial calculations. Another follow up is how this differs on the web, where Dart isolates compile to web workers with similar message passing semantics but different constraints.

ONE CONCRETE EXAMPLE: Suppose you receive a one megabyte JSON string from a network request and must parse it into a Dart model. Parsing is CPU intensive. Using jsonDecode on the main isolate will drop frames. Instead, you call compute with a static parse function and the raw string as the argument. Compute spawns an isolate, passes the string via message port, runs jsonDecode in the new isolate, serializes the resulting map back to the main isolate, and completes the Future with the parsed data, all without blocking the UI thread.