flutter_tflite VS plugins

For imageMean and imageStd, looking at the android implementation, we can see that these are passed along from dart to java eventually used at this point. Looking at the rest of this method, we can see this is in the context of converting the image data pixel by pixel into a bytearray that is eventually fed into the android tensorflow library. The actual conversion of pixel to bytearray is done by looking at the pixel RGB values separately and subtracting the mean then dividing by the std. This is meant to normalize your input data into "reasonable" data for your model.

(This new version will be endorsed by google_sign_in: ^6.0.0, once this PR lands: https://github.com/flutter/plugins/pull/7191, probably next week. This was made a major version change so people can test and update at their own pace.)

Looking at the web version of the video player package which doesn't use textures but VideoElement DOM nodes, I'd guess that textures aren't supported.

It's not 100% true that Flutter doesn't offer any first party native features. These plugins are maintained by the Flutter team: https://github.com/flutter/plugins/tree/main/packages

Here's an example: https://github.com/flutter/plugins. As you can see, that repo has no "issues" tab. And it mentions that issues should be created on the Flutter repo itself

There's work in progress to create a new camera plugin using CameraX: https://github.com/flutter/plugins/pull/6158

Find the example wiring in the Google sign-in example application.

image_picker

shared_preferences

The plugins is missing Issues tab currently. It's hard for developers who need to raise or find issues on packages.