plus_plugins VS plugins

You could write your own bash script or CLI to help manage these tasks. However, this costs you some time. In order to deal with these tasks more quickly, you can use community tools, like Melos, Very Good CLI, or Sidekick. In this article, we are going to use Melos. Melos is also used by repositories like FlutterFire, AWS Amplify (Flutter), Flame, and Plus Plugins.

Here's the PR: https://github.com/fluttercommunity/plus_plugins/pull/753

I think you should learn how to conduct due diligence properly. https://github.com/fluttercommunity/plus_plugins

The Issues tab should be enable same as another repos, such as plus_plugins

For example https://github.com/fluttercommunity/plus_plugins which is a fork of some of the plugins in flutter/plugins with some extras and web & desktop support. There's a lot of legacy issues that should be solved, as well you can help to migrate packages to null safety.

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