text
stringlengths
1
474
Released in Flutter 3.16
<topic_end>
<topic_start>
Released in Flutter 3.13
<topic_end>
<topic_start>
Released in Flutter 3.10
<topic_end>
<topic_start>
Released in Flutter 3.7
<topic_end>
<topic_start>
Released in Flutter 3.3
<topic_end>
<topic_start>
Released in Flutter 3
<topic_end>
<topic_start>
Released in Flutter 2.10
<topic_end>
<topic_start>
Released in Flutter 2.5
<topic_end>
<topic_start>
Reverted change in 2.2
The following breaking change was reverted in release 2.2:<topic_end>
<topic_start>
Released in Flutter 2.2
<topic_end>
<topic_start>
Released in Flutter 2
<topic_end>
<topic_start>
Released in Flutter 1.22
<topic_end>
<topic_start>
Released in Flutter 1.20
<topic_end>
<topic_start>
Released in Flutter 1.17
<topic_end>
<topic_start>Flutter compatibility policy
The Flutter team tries to balance the need for API stability with the
need to keep evolving APIs to fix bugs, improve API ergonomics,
and provide new features in a coherent manner.To this end, we have created a test registry where you can provide
unit tests for your own applications or libraries that we run
on every change to help us track changes that would break
existing applications. Our commitment is that we won’t make any
changes that break these tests without working with the developers of
those tests to (a) determine if the change is sufficiently valuable,
and (b) provide fixes for the code so that the tests continue to pass.If you would like to provide tests as part of this program, please
submit a PR to the flutter/tests repository.
The README on that repository describes
the process in detail.<topic_end>
<topic_start>
Announcements and migration guides
If we do make a breaking change (defined as a change that caused one
or more of these submitted tests to require changes), we will announce
the change on our flutter-announce
mailing list as well as in our release notes.We provide a list of guides for migrating code affected by
breaking changes.<topic_end>
<topic_start>
Deprecation policy
We will, on occasion, deprecate certain APIs rather than outright
break them overnight. This is independent of our compatibility policy
which is exclusively based on whether submitted tests fail, as
described above.Deprecated APIs are removed after a migration grace period. This grace
period is one calendar year after being released on the stable channel,
or after 4 stable releases, whichever is longer.When a deprecation does reach end of life, we follow the same procedures
listed above for making breaking changes in removing the deprecated API.<topic_end>
<topic_start>
Dart and other libraries used by Flutter
The Dart language itself has a separate breaking-change policy,
with announcements on Dart announce.In general, the Flutter team doesn’t currently have any commitment
regarding breaking changes for other dependencies.
For example, it’s possible that a new version of
Flutter using a new version of Skia
(the graphics engine used by some platforms on Flutter)
or Harfbuzz (the font shaping engine used by Flutter)
would have changes that affect contributed tests.
Such changes wouldn’t necessarily be accompanied by a
migration guide.
<topic_end>
<topic_start>Codelabs
The Flutter codelabs provide a guided,
hands-on coding experience. Some codelabs
run in DartPad—no downloads required!<topic_end>
<topic_start>
Good for beginners
If you’re new to Flutter, we recommend starting with
one of the following codelabs:Building your first Flutter app (workshop)
An instructor-led version of our very popular
“Write your first Flutter app” codelab
(listed below).Your first Flutter app
Create a simple app that automatically generates cool-sounding names,
such as “newstay”, “lightstream”, “mainbrake”, or “graypine”.
This app is responsive and runs on mobile, desktop, and web.
(This also replaces the previous “write your first Flutter app”
for mobile, part 1 and part 2 codelabs.)Write your first Flutter app on the web
Implement a simple web app in DartPad (no downloads