Home screen widgets are one of the few ways a mobile app can be useful without the user opening it. But for Flutter developers, building one has traditionally meant stepping outside Dart — writing separate widget code for Android and iOS, figuring out how to share data with the Flutter app, and dealing with a lifecycle that's very different from a normal Flutter screen.

So a feature that sounds simple can end up involving quite a bit of platform-specific work.

The newer tooling around home_widget changes that. With its CLI and code generation support, we can define a widget from Dart and generate the native pieces needed to run it on both Android and iOS.

In this talk, I'll build a home screen widget that does more than display static information. It will respond to user interaction, receive updated data, and continue working when the Flutter app isn't running. We'll also test it with the app closed and without a network connection, to see what still works when Flutter isn't running and where the platform takes over.

The goal isn't to walk through the home_widget API. It's to understand what actually happens when a Flutter feature needs to live outside the app, how the app and widget communicate, and how much of that platform-specific work we can now avoid.