Updating the link for Repo

In the interest of transparency, we would like to share the high-level details of the road map so that others can understand our priorities and plan on the basis of what we are doing.

Our plans will evolve over time on the basis of client feedback and new market opportunities. We use quarterly surveys and yes. GitHub Feedback on issues determines the prioritization of work. The list here should not be seen as exhaustive, nor as a commitment that we will complete all of this. If you have feedback on the issues we should address, we encourage you to contact us (e.g. by submitting questions, or by responding to the first comment on the issue with the expression "Standing your thumb"). Flutter is an open source project, and we invite contributions to the themes and other areas described below.

If you are a contributor or a team of contributors with a long-term plan to contribute to Flutter, and it is hoped that your work will be reflected in the road map, contact Hixie (ian@hixie.ch).

The road map is ambitious; it represents some of the work that our most active Flutter contributors are planning to do this year. Generally, it is difficult to provide any assurance of work, especially for open-source projects with hundreds of contributors.

Our Flutter Forward keynote speech demonstrated some of the future plans!

As always, the most important thing we can do is to increase the overall speed of the project. This includes the reduction of technical debt, such as stylized testing, but it also means improving our processes, helping new people join the team and making work more efficient. To that end, we will hold regular meetings for team members at which the issue of speed can be raised, recorded and resolved. Use Discord event to announce meetings to team members on our Discord.

Depending on the economic and epidemiological climate, we may also organize a summit to bring the team together.

We also plan to spend some time this year checking the backlog, closing out obsolete or unable to act and prioritizing the remaining issues.

This year our first priority for Flutter's improvement is performance.

We want to start with iOS On top of the colored compiler, Carden, then in Android And on the desktop.

For Web, we are working to support Wasm as a target, and we are planning to study the use of multi-wire rendering, reduce download size of basic Flutter applications and improve the performance of custom colourers.

For the back end based on virtual machines, we would like to improve memory allocation strategies to improve responsiveness and application start-up.

Accessability is essential for the Flutter application, and we will continue to invest significant funds to make the Flutter application more accessible, thus improving the quality of access support on all platforms. Likewise, it is important for us to continue to improve our documents. In both cases, improvements were largely expected to take the form of wrong fixes and minor patches, rather than large projects that could easily be described on the road map, but that would not make them less important.

We will also continue to achieve the functions required for full authenticity on each platform, especially the fast-growing Android and iOS. For example, we expect that this year our Cupertino small parts collection will make significant progress in updating and increasing the number of small components supported, and we plan to achieve support for Android predictive retreat and Android handwritten input. We're also planning to transplant the camera plugin to Android's latest CameraX. APII don't know.

We will remain committed to SLSA compliance (supply chain integrity), with the goal of reaching SLSA-3 in our main repository this year and with a view to continuing to reach SLSA-4 next year. We also want to expand our tools so that the Flutter package and application developers can achieve the same level of security.

We do want to spend some time developing new functions. These are usually driven by one of the following three motivations: popularity (we look at how much of a problem has received a “string-up thumb” reaction to help determine the priority of the job), equivalence and portability (when a platform supports a function, we think it is important to make it work anywhere), and support other jobs (e.g., new functions that can further improve performance).

The most prominent functions that we expect to achieve this year are:

- Customized asset converters because they can improve some performance.

- Efficient 2D rolling small components (e.g. tables and trees) to enhance the performance of applications with such interfaces.

- Multiple windows, especially for desktop platforms, as this is a much-needed feature.

- In response to popular demand, It's not a good idea. and Windows Look on the platform.

- Drag and drop, which also meets the needs of the population.

- iOS on wireless debugging, this is our second-largest demand function.

- Customizing the “flutter condition” template, which makes it easier for third parties (e.g. Flame engines) to guide developers.

- Support elements embedded (see also #32329) to allow Flutter content to be added to any standard Web