This looks really impressive. Really curious to try it out!
This is an old post, but did anyone try this out?
Hi there, I'm a proud team member from React Studio by Neonto. Please let me know how I may help you :) Looking forward to hearing from you!
I think this looks really interesting as a designer who works on a product team that users React.
Are you at all concerned (as a team) about the quality of code output? Up to this point we haven't seen (m)any design tools with the ability to output fully usable code out of the box. What makes React Studio different?
Just as a curiosity - Does it use built in React state switching tools or something like Flux/Redux built in to handle that?
I wrote most of the code generation for React Studio, so I'm glad to answer this question :)
It really comes down to three things:
1) React's design is a great match for visual tools. Declarative views, functional state, clearly separated components -- these are all fundamental good design choices by the React team that make it easier for a tool vendor like us to present the same concepts in a visual form.
2) We don't try to do everything. React Studio isn't really a Dreamweaver competitor. If you want to do a static landing page, there are already great tools out there for that. Instead we are focussing on mobile-first single page web apps. That helps a lot in designing the code generator because it's fundamentally component-oriented.
3) We have lots of experience in this already. We started at the "deep end" of app code generation with Neonto's existing product that produces native code for iOS and Android. Compared to the challenges we faced in producing clean Objective-C and Java, working with React has been immensely refreshing :D
Btw there is a free version of the iOS/Android tool on our site at https://neonto.com if you'd like to compare with that... React Studio is of course a different product, but the existing Neonto Studio will give you an idea of where we're starting from.
Finally, about state -- we're currently doing event-based state updates (to avoid getting committed to any particular library too early), but the plan is to replace that with a plug-in system that will basically allow you to decide between Redux, Alt.js (or something else) at any time. This way, state management becomes a separated concern from the visual design and view components. (This kind of design-time liberty in swapping out libraries is one of the big strengths of code generation IMO!)
Super excited to try it out thanks for the information and good luck through the beta and release! You will likely see my name in the pre order group in the coming weeks!