@dotnetdave.bsky.socialStill creating and disposing `HttpClient` on every request?
That “clean” code can quietly destroy performance.
In my benchmark, reusing a shared `HttpClient` was 12,109× faster and reduced allocations by 10×.
dotnettips.com/2026/06/28/i...
#dotnet #MVPBuzz #HttpClient
@y3l1n4ung.bsky.socialStream an HTTP response without turning it into a model first.
Declare Stream<List<int>> for bytes or Stream<String> for decoded text.
https://dust-codegen.pages.dev/blog/2026-10-04-http-response-streams/
@y3l1n4ung.bsky.socialPost one JSON body.
The client owns the request shape.
https://dust-codegen.pages.dev/blog/2026-09-16-json-body-to-api/
@y3l1n4ung.bsky.socialFind one Flutter request on the server.
That is basic full-stack debugging.
https://dust-codegen.pages.dev/blog/2026-09-15-trace-request-flow/
@y3l1n4ung.bsky.socialServe the API and Flutter app from one Dart server.
That is a simple full-stack setup.
https://dust-codegen.pages.dev/blog/2026-09-14-serve-flutter-api/
@y3l1n4ung.bsky.socialValidate before the request. Validate again on the server.
That is normal app work.
https://dust-codegen.pages.dev/blog/2026-09-13-server-mobile-validation/
@y3l1n4ung.bsky.socialOpen a product link in Flutter. Read the product from a Dart server.
That is one app flow.
https://dust-codegen.pages.dev/blog/2026-09-12-product-link-flow/
@y3l1n4ung.bsky.socialFlutter’s current full-stack developer series is a useful frame for Dust too.
The repeated work is often not one widget. It is the path between the form, request model, API call, state updat…
https://dust-codegen.pages.dev/blog/2026-09-11-signup-flow-tutorial/
