Add checkmarks to completed items.

In the interest of transparency, we would like to pass on general details of our roadmap so that others can see our priorities and create plans based on our work. Our plans will evolve over time on the basis of customer feedback and new market opportunities. We use our quarterly surveys and feedback GitHub- problems to prioritize work. The list listed here does not claim completeness or represents a commitment that we will complete the entire work. If you have any feedback on what you think we should work on, we recommend that you contact us (e.g. by submitting a problem or by using the emoji action “ thumb up” on the first comment of a problem). Flutter is an open source project, we invite you to contribute to both the topics presented below and in other areas. If you are a contributor or a team of contributors and have long-term plans for contributing to Floter and want your planned efforts to be taken into account in the Roadmap, please contact Hixie (ian@hixie.ch). Note: Articles with a Θ are completely finished and released. You may also be interested in the discussion of Google on his strategy for floodters in 2022. The area we will focus on is the development experience. Our goal is to SDK to create that developer loves. This will manifest in a variety of different areas, for example when creating widgets or plugins that solve common scenarios, when cleaning existing ones APIss, when introducing new APIs to simplify frequently occurring patterns, improving error messages, developing our developer tools and IDE plugins, creating new lints, eliminating errors in the framework and in the engine, improving API documentation, creating more useful examples, hot reloading on the web and improving Stack Traces Darts. In 2022 we plan to bring our desktop support to the stable channel. We are planning to focus on testing and announcing a platform as soon as it is ready, starting with Windowsthen Linux and macOS. One essential part of these efforts is the expansion of our regression test suite to give us the security to expand these efforts without damaging the existing code. Especially in terms of floodters for the web, we plan to work on improving performance, plugin quality, accessibility and consistency across all browsers. We also intend to embed floodter applications into other, non-flooded applications HTML- to significantly simplify pages. We will update the material library to support material 3 . This is mainly attributable to our goal, which is to Android but is not limited to this platform. We intend to implement a text selection across widgets. This is motivated by our aim to achieve good playback with the web platform, even if this is not restricted to the web. We intend to improve the text editing experience on different platforms, for example by improving our loyalty to desktop text editing conventions and our integration with iPadOS handwriting recognition. For desktop and web we provide a solution for menus (context menus and menu bars), including integration into the host operating system (which is particularly relevant for macOS). Finally, we intend to experiment with the support of rendering in multiple windows from a single isolate, also motivated by the desktop, but not limited to this platform. We plan to develop the language consciously slowly but continuously. We assume that we will introduce an important function in 2022 (probably static metaprogramming; we will make decisions based on our confidence that the function will improve the language) as well as some minor speech improvements, probably including an improvement in the import syntax for packages. We also plan to expand Dart’s compilation toolchain to support the compilation after Wasm, depending on the timely standardization of WasmGC. In 2021, we solved a number of problems related to Jank, but we have concluded that we have to completely reconsider the use of Shader. This is why we have rewritten our graphics backup. In 2022 we intend to, tide on iOS migrate to this new architecture and then, based on our experience, start working on porting this solution to other platforms. In addition, we will also implement further performance improvements and performance inspection functions, such as has enabled our new DisplayList system. We plan to stop support for 32-bit-iOS in 2022. In 2022, we will increase our investments in the security of the supply chain, with the intention of finally adapting our infrastructure to the requirements described in SLSA Level 4. Note: We conduct an archive of the roadmaps of recent years on a separate page. - Home of the Wiki

- Roadmap

- API reference (stable)

- API reference (main)

- Glossary

- Guide to contributors

- Chat on Discord

- Design documents

- Code of Conduct

- Create Triage Reports (currently)

- Our values

- Tree hygiene

- Thematic hygiene and triage

- Styleguide for Flutter-Repo

- Project teams

- Contributor access

- What do you want me to work on? - Popular topics

- Conducting and writing tests

- Release process

- Flutter Framework Gardener Rotation

- Rolling arrow

- Manual motor reel with Breaking Commits

- Update Material Design fonts and symbols

- Postmortems and retrospectives

- Best Practices for Hotfix Documentation

- In case of emergency

- Landing changes with auto submit

- Set up the framework development environment

- The Framework Architecture

- Generating API Docs Code Blocks

- running examples

- Use of Dart Analyzer

- Flatter variants

- Test the cover for package:flutter

- Write a Golden File Test for package:flutter

- Manage template image sets

- Set up the engine development environment

- Compiling the engine

- Debugging the engine

– Use of disinfectants with the flooded engine

- Testing the engine

- The engine architecture

- Flutter modes

- crash

- more... - Set up the development environment for packages

- Repository structure for plugins and packages

- Participation in plugins and packages

- Understanding package tests

- Plugin tests

- Publication of a plugin or package

- more...