proposal: Add LibraryComponent primitive to Flutter #187219

Document Link

https://flutter.dev/go/introduce-component-library

What problem are you solving?

Flutter developers building advanced, dynamic user interfaces—such as runtime layout translation for Generative UI (e.g., genui) or visual component playgrounds (e.g., widgetbook)—lack a standardized framework primitive to natively group and catalog a cohesive collection of widgets. Consequently, package authors must reinvent custom wrappers for annotating widgets in design systems, including semantic information (like widget description) and parameters. For example:

• Stac custom widgets (parameters a defined as fields on the widget class)
• GenUI catalog items (parameters are fed via json_schema)
• Widgetbook use cases (parameters are called knobs)
• OpenUI Library (parameters are fed via json_schema)

This structural fragmentation forces application developers to maintain redundant, boilerplate translation layers to map the exact same corporate design system across different toolsets, reducing ecosystem interoperability. This problem could become more predominant as Flutter moves to decouple Material and Cupertino from the core framework repository, which could lead to more custom design systems being adopted.