Updated roadmap (markdown)

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).

We will introduce Dart's robust air safety into Flutter and direct the transport of plugins and packaged ecosystems to air safety, including the transfer of packages and plugs directly maintained by the Flutter team.

As part of this, we plan to provide migration tools, examples and documents to help move existing codes.

We are continuing to address the issue of the performance of Cardon at the start-up.

We will work to support the incremental downloading of assets and codes from the store (subject to the limitations of each platform) to allow the application to download much smaller initial downloads than full downloads and to obtain data as required.

We will also seek to improve performance and anthropoengineering and reduce the embedding of Flutter. Android and iOS Costs for existing applications.

In addition, as usual, we plan to add support to the new functionality of iOS and Android operating systems.

Our goal for 2021 is to be Web, in addition to iOS and Android.It's not a good idea.I don't know.Windows and Linux Support for quality of production to enable developers to use the same SDK Create applications across six stand-alone platforms.

Especially for Web, our focus will be on authenticity and performance, not new functions, because we're committed to proving that Flutter can provide high-quality experience on Web.

For desktops, in addition to ensuring a high quality experience, we will also complete the work of the auxiliary functional layer and add support for displaying multiple independent windows.

We will continue to work to eliminate friction points. One of the areas of research is the reduction of the model documents needed to achieve common goals in Flutter. We will also look at the possibility of creating tools based on investment in space safety migration tools that will make it easier for developers to manage major changes, which will enable us to make our own API Some long-awaited improvements have been made, but because of their destructive nature, we have so far avoided them.

In 2021, we will continue to work with the community to develop the Flutter team support plugin. Our goal is to achieve the quality of pre-publishing plugins and to maintain them at that level through increasing responsiveness to questions and PRs. We also plan to make major improvements to the WebView plugin.

Based on the experience of an application that is actually based on Flutter, we will work to improve the memory use of Flutter, the cost of downloading the application, running time performance, battery use and the Carton phenomenon. These may take the form of engine or frame repairs and documents or videos describing best practices. We also intend to improve our tools to help debug the use of memory.

In addition, we will continue to address erroneous reports. In 2020, we solved more than 17,000 problems, and our goal is to have at least the same level of impact in 2021.

While in 2020 we focused on repairing errors, in 2021 we planned to add important new functions. Some are listed above. We also intend to improve small table components and to introduce some small tree components to support a large number of columns, rows and/or tree levels, as well as cells across columns or rows.

Flutter will continue to provide three “channels” where developers can receive updates: masters, betas and stables, with increasing stability and quality confidence, but with longer lead times for disseminating changes. Please note - Development channel is disabled. Read more on this blog.

The development channel is disabled and not updated. We plan to publish one test version per month (usually at the beginning of the month) and about four stabilization versions throughout the year. We suggest that you use stable channels for applications that are distributed to end-users. For more details about our release process, please see the Flutter construction channel wiki page.

The road map was provided against a historical background.

At the Flutter Interact event in December 2019, we announced that our support for Web had reached test-level quality. We intend to continue this work with the goal of getting Web the same support as Android and iOS. We hope that we will continue to work together to make Flutter the best way to create desktop applications.

Our goal this year is for you to be able to run the flutter create; run.

Allows your applications to run on Web Browser, MacOS, Windows, Android, Fuchsia and iOS, and supports thermal load, plugin, test and distribution mode construction. We're going to make sure that our Material Design small-assembly library works on all these platforms.

We're not going to provide a desktop version of the Cupertino Small Widget Library in 2020.

Our other main objective is to improve the quality of Flutter, repair errors and address some of the most needed functions. This covers a wide range of areas, but we are particularly concerned about our Kubitinoko and iOS authenticity, our support for Android equipment, and the development experience.

We intend to provide long-awaited functions, such as router re-engineering, case state preservation and restoration, and improved international workflow.

Overall, in 2020, we intend to focus on repairing errors rather than adding new functions.

We have mainly used the `stroke-up' emoticons of the first comment on the question to determine its importance. For more details on our priority strategy, please refer to the issue wiki page.

- Wikipedia home page

- Road map

- API Reference (Stable)

- API Reference (Main)

- Glossary

- A guide for contributors

- Chat on Discord

- Design files.

- Code of conduct.

- Publication of classification reports (update)

- Our values.

- Tree hygiene.

- Problems health and classification

- Flutter repository style guide.

- Project team

- Donor visits

- What should I do?

- Hot question.

- Run and prepare tests

- Release process

- Flutter frame gardener rotates.

- Rolling darts.

- Hand-held engine scroll and break submission

- Update material design fonts and icons

- After-action analysis and review

- Best practices in repairing programme documents

- In an emergency.

- Automatically submitted landing changes

- Framework development environment

- Framework structure

- API document code block generation

- Run examples

- Use Dart Analyzer

- Flutter run variant

- Test coverage of packages: flutter

- Producing a gold file test for package:flutter

- Manage template image resources

- Set up Engineering Development Environment

- Compiler engine.

- Debug engines.

- Use the Sanitizer with the Flutter engine

- Test the engine.

- Engine structure

- Flutter mode

- Crash.

- More...

- Setup Packages Development Environment

- Plugin and package repository structure

- Contributing to plugins and packages

- Learn about the bag test.

- Plugin Test

- Publish plugins or packages

- More...