Add a runtime switch guide to control Impeller usage #11568
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of what this PR is changing or adding, and why:
Impeller has been causing issues on lower-end or older devices.
While stabilizing Impeller remains a priority, it is essential
to provide app developers with runtime control over its usage.
This allows decisions to be made on a per-device or per-SoC basis.
This patch introduces a guide for controlling Impeller usage at runtime
using the
getFlutterShellArgs()
method.Issues fixed by this PR (if any):
Partially fixes flutter/flutter#160902
PRs or commits this PR depends on (if any):
Presubmit checklist