plugins VS plus_plugins

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

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

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.

Flutter Google map API helps to implement location-aware services in the Flutter application. It allows developers to display a map, configure the attributes, and render markers of places at respective geolocation.

I find the https://github.com/flutter/plugins repository to be hard to parse these days. It contains 19 different packages and 86 PRs as I write this, which makes it really difficult to follow what is happening inside it.

Image Picker - Images Selection by Collin Jackson.

Most of the packages in flutter/plugins can be used as an example of this architecture (See url_launcher).

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.

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.