ResponsiveFramework VS plugins

Sign up for early access at: https://codelessly.com

At Codelessly, we're building a design to code converter that converts Figma designs into working app and website code. For those that don't know, Figma is a popular design tool. In order to achieve our target goal of 99% conversion accuracy, we realized that we needed to recreate Figma and implement the Figma API spec. Therein lies the problem, recreating Figma requires building a canvas rendering framework.

Please share your thoughts and feedback in this thread and if you have a comment on the API, I'm reworking the API to be more flexible for v0.3.0 here https://github.com/Codelessly/ResponsiveFramework/issues/76

I wrote the Responsive Framework to simplify responsiveness for building websites and apps. We've built a few websites and webapps using the package so it's pretty well battle tested. The package should help you easily implement your own customizable responsiveness system.

We're really close, Alpha invites going out in a few months! https://codelessly.com

For the past 4 months, we've been building a custom layout engine from the ground up to support converting to Flutter and HTML. If you'd like an inside look, signup for the beta at https://codelessly.com

You can sign up for our beta at https://codelessly.com

Have you tried this library for responsiveness? https://github.com/Codelessly/ResponsiveFramework

Figma to Code was a big success, this week it has passed 10k downloads. I got job offerings from every competitor and ended up accepting one of them, Codelessly, where we are building a visual editor for Flutter.

For building Flutter websites, I recommend taking a look at my Responsive Framework and website examples. It can help you get a good start.

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