Show HN: A Visual IDE for React

Yes, there are many attempts trying to fix the problem, that designing requires coding and yes, that is a very, very hard problem to do right.

But just shitting on something because you feel bitter about the topic (or whatever your motivation is) probably won't lead to anything interesting.

> I made this because building UIs in a lexical medium like code is super annoying. I have to pre-render what I’m making in my head

I'd call the pre-rendering in your head a benefit, tbh. Also.. watching your vid, the property editor being "far away" from the selected item renders this tool much less useful to me than writing code. My eyesight's bad, so I can't keep the editor and the selected object in focus at the same time. The head & eye switching is probably more annoying to someone in my position than switching apps because at least I know I'm changing context when I switch apps (although I admit, I've put up with that for 20 years so perhaps I just don't notice).

> I was inspired by the developer console in chrome and safari since I end up editing css there because it’s ironically more convenient.

Conversely, I agree with this entirely. I don't like having to bob my head around the screen when I edit CSS in the browser, but it's still MUCH faster and intuitive than doing it in a separate code editor. I strongly dislike Tailwind and similar tools because they prevent this kind of coding/debugging. A similar tool got shown here on HN recently, and the conversation circled the idea that a visual tool to edit CSS is a) so handy but b) really hard to build because it's not programmatically obvious which file to make updates too... it's still easier to keep the file hierarchy in your head (even though that's quite hard). I guess focusing on React components lets you assume the CSS is "beside" the given component.

Keep up the good work - maybe jetbrains will buy / fund you!