3 ms·

I think you're onto something. I'm not sure what you mean by 'components' on the roadmap, but if it's the ability to bring react components back into the editor

by ENGNR 2y ago

I think you're onto something. I'm not sure what you mean by 'components' on the roadmap, but if it's the ability to bring react components back into the editor, and have the designer WYSIWYG modify the props - that's the exact thing we've been saying "suuurely this must exist" for a long time (rant mode enabled). The key pain for us that I think you're touching on is that "design/dev mode" isn't how teams actually work. Devs do far more design than we think. My experience is that designers do the pretty or complex pieces, while dev does the long tail "boring" designs. Often devs do the screen layouts since nav and routing can get a bit complex. Secondly, designers don't just hand off a design and that's it. The design system gets implemented as components, which have tweaks due to usability/issue reports/further design, and then the designers really want to be taking those components and recomposing them back into sections and screens. Ideally designers would be just setting props like images, text and ids faaaar up the abstraction layers, with dev components being automatically synced back in as they're built and updated. So definitely think your setup is potentially hitting a sweet spot between dev/design. Just to validate it as as product - plus one for open source with a paid hosted tier for convenience. Devs get to tinker, and designers don't have to think about how to run it.

hoakiet98 2y ago
> but if it's the ability to bring react components back into the editor, and have the designer WYSIWYG modify the props Haha yeah this is the plan. I really like Storybook for this reason but I loath the setup you need to do to expose every single prop. It seems straightforward for me to parse the React node and expose the inputs such that you get a Storybook experience that is also editable. I'm sure there are unknowns that will show at implementation time. > Devs do far more design than we think. I also think devs do more design than we should. I've never been handed a design where I don't run into edge cases at implementation time. At this point, I have to go back to the designer to clarify. The hope is that if designers are more involved in building front-end, they will hit these edge cases before handing them off. > a paid hosted tier for convenience This is a great idea, the goal is to get a point where designers just don't have to think about it
tmcdos 2y ago
This is exactly what Delphi does for desktop Windows applications - arranging components on a "form", tweaking their properties (props) through the ObjectInspector, assigning event listeners and quickly navigating to their handler functions in the code. It is such a breeze compared to Web development ...

by ENGNR 2y ago

hoakiet98 2y ago

> but if it's the ability to bring react components back into the editor, and have the designer WYSIWYG modify the props Haha yeah this is the plan. I really like Storybook for this reason but I loath the setup you need to do to expose every single prop. It seems straightforward for me to parse the React node and expose the inputs such that you get a Storybook experience that is also editable. I'm sure there are unknowns that will show at implementation time. > Devs do far more design than we think. I also think devs do more design than we should. I've never been handed a design where I don't run into edge cases at implementation time. At this point, I have to go back to the designer to clarify. The hope is that if designers are more involved in building front-end, they will hit these edge cases before handing them off. > a paid hosted tier for convenience This is a great idea, the goal is to get a point where designers just don't have to think about it

tmcdos 2y ago

This is exactly what Delphi does for desktop Windows applications - arranging components on a "form", tweaking their properties (props) through the ObjectInspector, assigning event listeners and quickly navigating to their handler functions in the code. It is such a breeze compared to Web development ...