plugins VS flutter_gen

(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.

4)Flutter_gen:

To load assets in your Flutter app, you have to reference the asset using path strings, which is not safe. The FlutterGen package helps remove all string-based APIs in your app by generating code for all your assets.

This tool is very useful. We all know that string based APIs are not the most secure. If you insert a single character incorrectly, the whole string will stop working. The problem is that you use sting apis very often in Flutter. Assets, fonts, colors... Flutter gen is there to solve this problem.

If you have any questions regarding this package, in this link you can browse the documentation and you can also check its source code in its repo from GitHub.