design-patterns-dart VS plugins

Better say "software design patterns", is a general, reusable solution to a commonly occurring problem within a given context in software design. Here is a nice resource on patterns: https://refactoring.guru/design-patterns

Over the years, I've also developed a bit of an obsession with design patterns. I bought the GoF book which I consult regularly. I also study the code on websites such as refactoring.guru or sourcemaking to try to get a better grasp on OOP and truly implement this in my code.

If it seems to you that you have achieved everything and are not mistaken, read about the Dunning-Kruger Effect. Try to understand your area deeper (if it's a WEB, then study the architecture of WEB applications, how the browser works, the TCP /IP protocol), for general development, try to study the most popular design patterns and then try to adapt them to your environment. You can also upgrade well in algorithms and structures - https://www.codewars.com/.

This course is great for fundamentals, but design patterns deserve a study in of themself. There are some other courses (don't know any Harvard courses though, but feel free to share them if someone does) that cover design patterns though and plenty of youtube videos of decent quality. But a good book or website will do just fine too if you've already have the basics down.

Dart source code: https://github.com/ilopX/design-patterns-dart/tree/master/patterns/composite/products_and_boxes

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