How did you handle the WASM backend? That part was extremely impressive to me. But aren't the binaries practically too large for WASM?
In any case, really love what you're doing and will be following progress. Outstanding work!
How did you handle the WASM backend? That part was extremely impressive to me. But aren't the binaries practically too large for WASM?
In any case, really love what you're doing and will be following progress. Outstanding work!
What are compiled binaries like with this and Dart? I've been building a sort of similar framework and engine in Nim, mostly because I can get binaries under 200Kb. I looked into implementing the concept in other languages but don't recall much with Dart.
Also, how does this carry over to Flutter? Is this similar enough that minimal changes would be needed to move a TUI app into Flutter's graphical domain?
Binaries in Dart are definitely larger than 200kb, I just AOT compiled one of the examples and it was ~7.4MB (arm64 MacOS). Dart has a few different targets it can compile to, but it generally requires a couple of MBs, as it packages the whole runtime.
Yeah, my goal definitely is to have to as close to Flutter where it makes sense. You should mostly be able to copy it over 1:1, with a couple of caveats (GUI and a TUI app have a few differences here and there).
My value proposition is to make developers more productive by skipping the boring stuff, while FlutterFlow is more of an "all-in-one" app platform.
While Cursor stops after writing great code, Vide goes the extra mile and has full runtime integration. Vide will go the extra mile & make sure the UI looks on point, works on all screen configurations and behaves correctly. It does this by being deeply integrated into Flutters tooling, it's able to take screenshot/ place widgets on a Figma-like canvas and even interact with everything in an isolated and reproducible environment.
I currently have a web version of the IDE live but I'm going to launch a full native desktop IDE very soon.
Reason I'm asking is because I'm trying to write a new app from scratch but I'm getting demotivated having to implement things like users, organisations, and other things that is essentially just re-inventing the wheel.
Your example does not convince me that it would save time ('probably' isn't enough) or be generally useful enough that a designer could be convinced to drop Sketch for it.
As a designer, I want to use Sketch.
As a developer, I want a Sketch design over generated code.
For sure, it is a neat experiment to create something like this, but time and time again, people always resort back to tools like Sketch. I think this developer would be better off spending their time building out a super epic component widget library than trying to build a visual designer.
Right now, I wouldn't call it production-ready. It is too complex for non-coders and too trivial for actual developers.
I've been working on this for quite a while and I wanted to get something released so I wouldn't keep coding in my basement without feedback.
Right now, I'd say this tool is handy for Flutter beginners getting to know the layout system.
Addressing the problem regarding this being just a "Klickibunti" application.
I feel strongly about having this tool produce actual code a human developer would have written, therefore this could be considered the "groundwork" for future actually useful features.
Such features could include a full sketch integration that strongly connects to the actual widgets which work with different screen sizes and gesture behaviors.
One big feature which I've been planning for a while is a full 2-way code integration, meaning you'd be able to open up a random Flutter project in the widget-maker, tweak something and proceed with writing code.
Again, the points mentioned are very valid and I'm trying my best to build something which doesn't fall into the category of being a "nice idea that just doesn't work".
I was able to get a WASM binary as small as ~234 KiB!