-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Android] Add migration documentation to handle API 35 edge-to-edge changes #10755
Comments
I spoke offline to Camille. This is needed for the Q4 release, not Q3. I've asked her, when the time comes, to publish a public design doc and a breaking change page. |
To clarify (I'm not clear on how this aligns with the release schedule), I plan to do this work in Q3 and will publish the breaking change page in Q4. |
@sfshaza2 Going to start working on migration docs soon (not the breaking change documentation as we have not made that change yet), which will tell developers either how to opt out of edge to edge themselves or (if I can't make this work myself in the next week) tell developers how to migrate to edge to edge. Where on the website would be an appropriate place to put this documentation? |
Decided to split this into two parts:
|
SG! |
…11068) _Description of what this PR is changing or adding, and why:_ Adds a migration guide telling folks how to opt out of edge-to-edge mode when their Flutter on Android app targets Android 15+. This (targeting Android 15+) will happen by default in the next Flutter stable version, so the described migration steps will be necessary if folks do not explicitly use edge-to-edge mode in their app. Folks may also change the Android version they target, so the steps apply if their target Android 15+ themselves, as well. _Issues fixed by this PR (if any):_ Part of #10755 _PRs or commits this PR depends on (if any):_ flutter/flutter#153795 (merged) ## Presubmit checklist - [x] This PR is marked as draft with an explanation if not meant to land until a future stable release. - [x] This PR doesn’t contain automatically generated corrections (Grammarly or similar). - [x] This PR follows the [Google Developer Documentation Style Guidelines](https://developers.google.com/style) — for example, it doesn’t use _i.e._ or _e.g._, and it avoids _I_ and _we_ (first person). - [x] This PR uses [semantic line breaks](https://github.com/dart-lang/site-shared/blob/main/doc/writing-for-dart-and-flutter-websites.md#semantic-line-breaks) of 80 characters or fewer. --------- Co-authored-by: Shams Zakhour (ignore Sfshaza) <44418985+sfshaza2@users.noreply.github.com>
According to Android 35 docs, once an Android app targets API 35, edge to edge will become the default layout mode and there are several changes coming to edge-to-edge, most notably for Flutter the coloring of the system (status and navigation) bars. In order to support Flutter apps that target API 35 and edge-to-edge mode more generally as we plan to make this the default mode on Android (see flutter/flutter#86248), we need to develop migration documentation on how to modify one's Flutter app to adopt edge-to-edge mode.
The text was updated successfully, but these errors were encountered: