☂️ Reinforcement: Add more basic components to the core framework
This issue tracks proposals and development for net-new widgets and functionalities to be added to the core widgets library. This effort is the other side of the coin to our reinforcement work, see the [refactoring side](https://github.com/flutter/flutter/issues/53059) as well. While the refactoring issue focuses on moving existing code, this issue is dedicated to identifying and building new, foundational, style-agnostic primitives that are missing from the core widgets library today. The goal is to fill gaps in the core and make it an even more powerful foundation for building any design system. > [!NOTE] > Some of these may be best informed by a UXR study. Before considering contributing one of these net-new widgets, reach out to the team on Discord to confirm. ### Propose a New Core Widget! 💡 What foundational widget or capability do you wish existed in Flutter's core? If you have an idea for a new, un-opinionated "headless" widget that would be broadly useful, this is the place to propose it. Please provide a clear use case and rationale for why it belongs in the core framework. ### _Last update Mar 4, 2026_ So far, we have investigated many of the existing design components to determine if any refactoring can be done *before* decoupling, moving existing APIs to the widgets layer to a common surface (which is tracked in [https://github.com/flutter/flutter/issues/53059](https://github.com/flutter/flutter/issues/53059)). In some cases, we have decided not to break w
Posted by Hawmex on Jan 30, 2022, 2:13 PM
Tags
Related issues
Raise real-world problems, find people facing the same issue, and discuss solutions.2,500 issues0 comments
complaint (Software)
☂️ Reinforcement: Add more basic components to the core framework
This issue tracks proposals and development for net-new widgets and functionalities to be added to the core widgets library. This effort is the other side of the coin to our reinforcement work, see the [refactoring side](https://github.com/flutter/flutter/issues/53059) as well. While the refactoring issue focuses on moving existing code, this issue is dedicated to identifying and building new, foundational, style-agnostic primitives that are missing from the core widgets library today. The goal is to fill gaps in the core and make it an even more powerful foundation for building any design system. > [!NOTE] > Some of these may be best informed by a UXR study. Before considering contributing one of these net-new widgets, reach out to the team on Discord to confirm. ### Propose a New Core Widget! 💡 What foundational widget or capability do you wish existed in Flutter's core? If you have an idea for a new, un-opinionated "headless" widget that would be broadly useful, this is the place to propose it. Please provide a clear use case and rationale for why it belongs in the core framework. ### _Last update Mar 4, 2026_ So far, we have investigated many of the existing design components to determine if any refactoring can be done *before* decoupling, moving existing APIs to the widgets layer to a common surface (which is tracked in [https://github.com/flutter/flutter/issues/53059](https://github.com/flutter/flutter/issues/53059)). In some cases, we have decided not to break w
Comments (0)
No comments yet. Start the discussion.