Remove the obsolete link.

A road map for 2021 is under development. 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).

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). Flutter is an open source project, and we invite contributions to the themes and other areas described below.

At the Flutter Interact event in December 2019, we announced that our support for Web had reached test-level quality. We're going to continue this work. The goal is for Web to get along. Android and iOS Same support. 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.

Let your application on the Web Browser,It's not a good idea.I don't know.Windows, Android, Fuchsia and iOS run and support 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.

Flutter developers can choose the channel for receiving updates. We have four channels: Master, Dev, Beta and stable, with increased stability and quality confidence, but with longer lead times for transmission of change.

Based on the implementation of some additional tests, we publish the version to the development channel every few days. 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 refer to the launch process wiki page.

If you are interested in observing our monthly plan, you can view the milestone page on GitHub. That said, note that the problem often changes milestones and that no milestone should be considered a commitment date.

We have also followed up on a number of specific time requests from suppliers to the Platform.

- Wikipedia home page

- Road map

- What? API References (stability)

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