GitHub

In the interest of transparency, we want to share high-level details about our roadmap, so others can see our priorities and develop plans based on the work we are doing.

Our plans will evolve over time based on customer feedback and new market opportunities. We use our quarterly surveys and feedback on GitHub issues to prioritize work. The list presented here should not be considered exhaustive or a promise that we will complete all this work. If you have feedback on what you think we should work on, we encourage you to contact us (for example by reporting an issue or using the "thumbs up" emoji reaction on the first comment of an issue). Flutter is an open source project, we invite contributions both on the themes presented below and in other areas.

If you are a contributor or a team of contributors with long-term plans to contribute to Flutter and would like your planned efforts reflected in the roadmap, please contact Hixie (ian@hixie.ch).

You might also be interested in Google's discussion on its strategy for Flutter in 2022.

The area we will focus on the most is the developer experience. Our intention is to create a SDK that developers love. This will manifest in a myriad of different areas, for example creating widgets or plugins that solve common scenarios, cleaning up existing API, introducing new APIs to simplify commonly seen patterns, improving error messages, evolving our development tools and IDE plugins, creating new lints, fixing bugs in the framework and engine, improving documentation of the API, creating more useful samples, hot reloading on the web, and improving stack traces in Dart-to-JS. scenarios.

In 2022, we plan to expand our desktop support to the stable channel. We plan to focus on testing and announcing one platform at a time as it becomes ready, starting with Windows, then Linux and macOS. An important part of this effort is extending our regression testing suite to give us the confidence that allows us to extend these efforts without breaking existing code.

Regarding Flutter for Web in particular, we plan to work on improving performance, plugin quality, accessibility, and consistency across browsers. We also intend to make it much easier to integrate Flutter apps into other non-Flutter HTML pages.

We will be updating the Material library to support Material 3. This is primarily driven by our goal to improve fidelity with Android, although this is not limited to this platform. We intend to implement text selection between widgets. This is driven by our goal of achieving good fidelity with the web platform, although again this is not limited to the web.

We intend to improve the text editing experience across various platforms, for example by improving our fidelity to desktop text editing conventions and our integration with iPadOS handwriting recognition.

For desktop and web, we will provide a solution for menus (context menus and menu bars), including integration with the host operating system (which is particularly relevant for macOS).

Finally, also motivated by desktop, but again not limited to that platform, we intend to experiment with support for rendering across multiple windows from a single isolate.

We plan to continue evolving the language at a deliberately slow but steady pace. We plan to introduce a major feature in 2022 (likely static metaprogramming; we will make decisions based on our confidence that the feature will improve the language), as well as some minor improvements to the language, likely including improving package import syntax.

We also plan to extend Dart's build toolchain to support compilation to Wasm, subject to timely standardization of WasmGC.

In 2021, we fixed a number of issues with jank, but our conclusion was that we needed to completely rethink how we used shaders. As a result, we rewrote our graphics backend. In 2022, we intend to migrate Flutter on iOS to this new architecture and then, based on our experience, start working on porting this solution to other platforms. Additionally, we will also implement other performance improvements and performance introspection features, such as those enabled by our new DisplayList system.

We plan to drop support for 32-bit iOS in 2022.

In 2022, we will increase our investments in supply chain security, with the intention of bringing our infrastructure into compliance with the requirements outlined in SLSA Level 4.

Note: We keep an archive of previous years' route sheets on a separate page.

- Wiki Home

- Roadmap

- API reference (stable)

- API reference (main)

- Glossary

- Contributor Guide

- Chat on Discord

- Design documents

- Code of Conduct

- Issue triage reports (latest)

- Our values

- Tree hygiene

- Hygiene of problems and Triage

- Style guide for Flutter repository

- Project teams

- Contributor access

- What should I work on?

- Popular issues

- Realization and writing of tests

- Release process

- Flutter frame gardeners rotation

- Rolling dart

- Manual motor bearing with breaking engagements

- Updated material design fonts and icons

- Post-mortems and retrospectives

- Best practices for patch documentation

- In case of emergency

- Landing modifications with automatic submission

- Setting up the Framework development environment

- Framework architecture

- Generation of API Docs code blocks

- Examples of execution

- Using the Dart analyzer

- Flutter run variants

- Test coverage for package: flutter

- Writing a golden-file test for package:flutter

- Managing template image assets

- Setting up the Engine development environment

- Engine compilation

- Engine debugging

- Using disinfectants with the Flutter engine

- Test the engine

- Engine architecture

- Flutter modes

- Accidents

- more...

- Setting up the Package development environment

- Structure of the plugin and package repository

- Contribute to plugins and packages

- Understand package testing

- Plugin testing

- Publish a plugin or package

- more...