Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@knopp What's the main difference in the approach from #165072?

To use a custom WindowingOwner implementation, out-of-tree embedders would use a custom binding, right? Like this:

class MyBinding extends WidgetsFlutterBinding {
  static late final _instance = MyBinding();
  static MyBinding ensureInitialized() => _instance;

  @override
  WindowingOwner createWindowingOwner() {
    return FlutterpiWindowingOwner();
  }
}

And then how do you make use of that? Call MyBinding.ensureInitialized() before the app's main? (Similar to how plugin platform interfaces are currently registered)?

@ardera, given the feedback in #165072 I think we'll just make the defaultWindowingOwner writeable, no subclass needed.

@ardera, given the feedback in #165072 I think we'll just make the defaultWindowingOwner writeable, no subclass needed.

All good 👍 my concern would've just been that that makes it harder for apps to use custom widgets bindings. Other than that I actually like the approach of handling embedder-specific stuff in the bindings