Sweet! I want this but for Svelte! Figma to Svelte would be the dream team and probably trivial to make thanks to .svelte files supporting vanilla html, css, and js.
Dream fulfilled: https://github.com/BuilderIO/figma-html
Figma to React
81–90 of 121 posts
Re: Figma to React
#82Call me old-head, but I design with code first. In my practice this is effective. I usually start with low-fidelity prototype with some tool and move directly in html/css to create design system containers. My final step is to work on visual parts, fonts, illustration, ui elements, animation.
Re: Figma to React
#83Call me old-head, but I design with code first. In my practice this is effective. I usually start with low-fidelity prototype with some tool and move directly in html/css to create design system containers. My final step is to work on visual parts, fonts, illustration, ui elements, animation.
But how do you make the entire developer community conform to your idiosyncratic preferences if you don’t create a poorly designed DSL mixing multiple abstractions in a soup of future technical debt?
Re: Figma to React
#84Earlier quoted context omitted.
I think a good parallel of this is Webflow, which I find to be an incredibly powerful tool and gives design teams a lot of freedom to build and deploy their designs, however it’s incredibly cumbersome if you’re using it to mock up options and explore iterations. That work still happens in Sketch for our team, and when it’s approved that same team brings it into Webflow and “does it for real.” I expect exporting from…
What can you do in Solidworks that does not work in Rhino? Do you have a list of top five points, maybe?
Judging by partlysean’s response, “our industrial design team would use Rhino and then hand it off to the mechanical engineers to rebuild it in Solidworks.” I would think Rhino lacks the entire Computer Aided Engineering (CAE) capabilities that Solidworks has.
The Wikipedia page for Rhino says it’s a CAD tool, but Solidworks says CAD and CAE. So Rhino has a subset of Solidworks’ capabilities.
Engineers use CAE to help with determining how the materials, dimensions, and other engineering choices will be have under loads. So these have some similarities in that Solidworks can also do 3D modeling, which is used as an input to performing CAE.
Different audiences and different use cases.
Re: Figma to React
#85If Figma has their eyes open, they'll run with this idea. Design once in Figma, generate UIs for React, Vue, Jetpack and SwiftUI. Designers become way more productive, doing part of the work of front end devs.
The /idea/ of going from a design tool to working app is obvious. It's figuring out a way to do it that works which is hard.
Re: Figma to React
#86Call me old-head, but I design with code first. In my practice this is effective. I usually start with low-fidelity prototype with some tool and move directly in html/css to create design system containers. My final step is to work on visual parts, fonts, illustration, ui elements, animation.
But how do you make the entire developer community conform to your idiosyncratic preferences if you don’t create a poorly designed DSL mixing multiple abstractions in a soup of future technical debt?
I don't remember having a single problem with developers with my idiosyncratic preference. Actually my process is driven by the lack of good prototyping tools and optimisation in implementation time. Mixing multiple abstractions? DSL?
No. Last I checked - HTML and CSS are not soup of technical debt. Actually I am quite shocked to find out the lack of knowledge of CSS in developer community.
Re: Figma to React
#87Sweet! I want this but for Svelte! Figma to Svelte would be the dream team and probably trivial to make thanks to .svelte files supporting vanilla html, css, and js.
Ah yes, Svelte. What we're witnessing is a mass migration from an established society with great infrastructure, education, governance and stability moving to a barren uninhabitable land of opportunity and unlimited possibilities albeit full of traps, broken pipes, dangerous bugs and vicious wildlife. Troves-full are jumping on these new bandwagons, cramming themselves in, clueless but hopeful from the allure of a fa…
Lol, I've tried Svelte and it worked fine for business operations. Experience > conjecture.
Re: Figma to React
#88Earlier quoted context omitted.
I disagree. How did 1-5mb become an acceptable size to ship to your users? That's actually quite a lot. In a slow connection, this isn't even going to load anything except a blank screen for such a long time.
A desktop app quickly runs to 200mb. Why do we think it is so unreasonable for a full app on the web to take even 5% of that amount?
Because there's a LOT of people out there who have slow mobile data or poor signal strength. I think assuming that everyone everywhere has extremely fast internet is a bad assumption. Also there's an enormous amount of bloat in package sizes now, I don't think this really should be as bad as it currently is.
Re: Figma to React
#89Earlier quoted context omitted.
A desktop app quickly runs to 200mb. Why do we think it is so unreasonable for a full app on the web to take even 5% of that amount?
Because there's a LOT of people out there who have slow mobile data or poor signal strength. I think assuming that everyone everywhere has extremely fast internet is a bad assumption. Also there's an enormous amount of bloat in package sizes now, I don't think this really should be as bad as it currently is.
I agree 100%, in the use case I mentioned we were looking to either prove or disprove product hypothesis with real users fast so efficient code wasn't a priority, but rather to confirm wether what we were about to develop was valid.
Re: Figma to React
#90Earlier quoted context omitted.
I disagree. How did 1-5mb become an acceptable size to ship to your users? That's actually quite a lot. In a slow connection, this isn't even going to load anything except a blank screen for such a long time.
I think they’re talking about testing prototypes exported from the design app, not what they’d necessarily ship as a finished product?
Yeah testing is its intended usage, but on the initial phases of the product we did use it as the finished product clients were paying for.
It can be slightly hacked around to add user authentication & analytics, so if you are handling a small amount of users its a really efficient way to iterate fast.