// TODO: your plugin is no longer attached to a Flutter experience.

As shown above, your plugin might (or might not)
be associated with a given Flutter experience at
any given moment in time.
You should take care to initialize your plugin’s behavior
in onAttachedToEngine(), and then cleanup your plugin’s
references in onDetachedFromEngine().

The FlutterPluginBinding provides your plugin with a few
important references:

Returns the FlutterEngine that your plugin is attached to,
providing access to components like the DartExecutor,
FlutterRenderer, and more.

Returns the Android application’s Context for the running app.

UI/Activity plugin

If your plugin needs to interact with the UI,
such as requesting permissions, or altering Android UI chrome,
then you need to take additional steps to define your plugin.
You must implement the ActivityAware interface.

public

class

MyPlugin

implements