Move API Model Conversion off the UI Path

Flutter’s docs call out a common issue: large parsing work can block the main isolate and cause jank.

For API clients, the repeated work is often the same. Fetch the response. Decode the payload. Convert each item into a model.

Dust HTTP clients can move only the generated model conversion step to another isolate.

Dio still handles the request. Your endpoint still stays in one interface. Dust handles the response shape you declared.

Use it when model conversion is the part you want to move away from the UI path.

Read the Dust HTTP client guide.

#Dust #HTTPClient #Flutter #Dart #CodeGeneration