ui-editor VS gallery

Find what drives you nuts, and work towards it

What drives me - Why the hell the machine is not working for me, it feels like I'm working for it.

How I work towards it -

Latest

Private project - https://www.youtube.com/watch?v=KHpf8h0JMuo

Public project - https://github.com/imvetri/ui-editor

My side project, my office goals, my plan to sell a product, all around the same.

this is great!. Real time design to developed code Checkout https://github.com/imvetri/ui-editor.

I took a step to solve framework bloatware for web interface. Frameworks are meant to speed up development.

Here is my project https://github.com/imvetri/ui-editor.

It started as a challenge to find single syntax to generate code for all framework, then it scales to low code, and right now at design to code

I have built a design system builder concept that can generate code as well. It's called ui-editor, you can check it out here https://github.com/imvetri/ui-editor.

Design to code will increase productivity and revolutionary bridging gap between designer and developer. I'm writing to you if you think there would be an opportunity to experiment my concept at your organization.

With design system builder concept in place, it can be integrated with a open source collaborative whiteboard project called excalidraw, which can also be used as a prototyping tool.

I add features to it as I get ideas, last year I applied to YC just like that, but didnt get selected.

I'm creator, ideated, maintainer of https://github.com/imvetri/ui-editor. Back then when I started it, I wanted to build a tool to automate my job, I'm a frontend developer and I wanted to build a tool where I shouldn't have to learn framework code, so I somehow solved a major problem in the web industry, it was fun.

Hi there, This was the first time I applied to ycombinator with an idea based on https://github.com/imvetri/ui-editor.

how about developers building a designers tool that generates code? check my hobby project out. https://github.com/imvetri/ui-editor

I found a (now archived, but still useful) example repository at https://github.com/flutter/gallery, which showcases a number of example views and components.

I was pessimistic about flutter 4 years ago but rechecked it recently (learning right now) and IMO it's really good user/developer proposition these days. They resolved most of issues on mobile devices and desktops - only web version still off but once wasmGC is ready (hopefully this year) probably things will improve.

Best way for developer elevator pitch just download few flutter apps and see how you like the experience:

1. wonderous - https://flutter.gskinner.com/wonderous/

2. flutterflow (low code + gui editor for flutter) - https://https://flutterflow.io/

3. appflowy (notion alternative) - https://appflowy.io/

4. flutter gallery (official flutter kitchen sink) -

Android (Google Play Store, .apk) - https://play.google.com/store/apps/details?id=io.flutter.dem...

web (gallery.flutter.dev) - https://gallery.flutter.dev/

macOS (.zip) - https://github.com/flutter/gallery/releases/latest

5. official material 3.0 demo - https://flutter.github.io/samples/web/material_3_demo/#/

I recommend to checkout and play with material 3.0 demo (just keep in mind this is web version will have even better when using native compiled version on mobile or desktop):

https://flutter.github.io/samples/web/material_3_demo/#/

4) Try web flutter gallery to see numerous app samples (more complex) and widgets

https://gallery.flutter.dev/#/

again even better to download mobile or desktop version that there is in app store:

play store: https://play.google.com/store/apps/details?id=io.flutter.dem...

macos dmg (.zip): https://github.com/flutter/gallery/releases/latest

I tried both macos flutter gallery and on iOS and surpassingly is pretty good these days and smooth and feel native - even text selection works these days, moving cursor with long press on keyboard space etc. Occasionally was more difficult to dismiss keyboard on iOS and back/next mouse keys or touchpad gestures didn't work on macOS flutter gallery. But overall I'm quite satisfied and surprised comparing how it looked 4 years ago.

I remember the first time when I looked at the Flutter Gallery and was surprised at how things felt just broken in a web browser, for example: https://gallery.flutter.dev (I think it was the Reply example in particular)

Ctrl + click or middle mouse button didn't work on links, right click didn't work, selecting and copying text didn't work, inspect element didn't work (due to how the technology is built), even attempting to zoom the page did nothing.

This article does ring true both because of that experience, as well as some of the SPA implementations I've seen even with more conventional technologies.

Google Docs. Figma. Any Flutter app like https://gallery.flutter.dev/. Short answer, they're really not handling accessibility.

Even when you did that, scrolling was completely wrong. The web simply doesn’t expose primitives from which you can build native-feel scrolling, and the best you can manage on precise touchpads (that is, all laptops now) will normally feel terrible, and lack things like inertia which are rather important. https://gallery.flutter.dev/, for example, scrolls less than half as fast as it should, and lacks inertia. (… and renders text in the wrong font, and doesn’t do links at all where it obviously should, and uses scrollbars that behave all wrong quite apart from being overlay which my native aren’t, and get typing emoji wrong, and… and… seriously, it’s just a litany of awfulness.)

Oh wow. I had thought the claim that they were not producing any semantic web elements was almost certainly exaggerated. That said, for the number of things that are on https://gallery.flutter.dev/#/reply, there are a surprisingly low number of elements. Wow.

example: https://gallery.flutter.dev (and Flutter Gallery on the playstore)

You could just need to clear your cache, but I suspect might have something going on because of how you're loading your theme. Not sure about having two runapp functions. I would suggest inspecting gallery.flutter.dev and then implementing a splash screen the way they have, as you will get the benefit of having a slash while flutter is being loaded, vs a splash screen that won't start until after, which imho, defeats the purpose.