snippets_flutter-stream-widget_skill

Overview

This skill teaches how to build dynamic Flutter UIs by emitting Widgets from a Stream inside a widget's build method. It demonstrates a small StreamWidget base class that integrates with Flutter lifecycle hooks and handles empty and error states. The examples include a Riverpod-powered implementation showing stream, future, and generated widgets together. The approach encourages reactive, incremental UI updates instead of rebuilding whole subtrees synchronously.

How this skill works

The StreamWidget exposes a build(BuildContext) method that returns Stream<Widget>. A private State uses StreamBuilder to listen to that stream and render snapshots. Optional callbacks provide initState, dispose, reassemble, buildEmpty, and buildError so you can manage resources and handle loading or error visuals. The pattern can also be adapted for Future<Widget> but streams fit continuous, time-based, or event-driven UI changes better.

When to use it

• When UI should update incrementally from a sequence of events (timers, sockets, sensors).
• When you want to separate widget-producing logic into asynchronous producers.
• When integrating with Riverpod providers that produce streams of Widgets.
• For dashboards or live feeds where parts of the UI change without full rebuilds.
• When you need explicit lifecycle control for stream controllers or timers.

Best practices

• Keep stream-to-widget mapping lightweight to avoid expensive rebuilds each tick.
• Close controllers and cancel timers in dispose to prevent leaks.
• Use buildEmpty to show a placeholder or loader while awaiting initial data.
• Use buildError to present friendly error UI and optionally retry controls.
• Avoid emitting large widget trees on every event; emit small, composable widgets.

Example use cases

• A live counter or clock where each tick yields a small Text widget.
• A chat message pane that yields new message row widgets as they arrive.
• A sensor dashboard that updates individual metric cards from streams.
• Integrating with Riverpod providers that expose Stream<Widget> for composition.
• Progressive content loading where portions of the screen appear as data streams in.