Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Figma to React

figma-to-react.vercel.app

Post reply on HN
Print view View original

111–120 of 121 posts

Re: Figma to React

#111

Post by unityByFreedom »

xyzzyrz wrote: post #101
sktrdie wrote: post #96

I think all these approaches for code-generation have been around for a while and are interesting for web-agencies but as soon as you need to have more finer grained control they lose their initial benefits. SwiftUI has really shined in this regard where instead of offering a visual canvas and code-generation behind the scenes it does both things [1]. It has code and preview side-by-side so you can write code and see…

Plasmic ( https://www.plasmic.app ) enables this workflow—you can visually edit the design while editing behavioral code side-by-side—but with a different approach than what you described, since we want to include non-developers. (I work on this.)

On the pricing page, what is "Content Ownership" and why is that only granted for enterprise customers?

https://www.plasmic.app/pricing/

Re: Figma to React

#112

Post by RobertKerans »

nautilus12 wrote: post #110
RobertKerans wrote: post #98

Earlier quoted context omitted.

I mean we've had these tools for two decades now and yet front-end coding seems fine. There are numerous tools for (eg) mapping UML diagrams to code: I assume you don't feel threatened by those?

Personally, I dont feel threatened because I dont touch front end coding.

No, nothing to do with frontend code, as in auto-generation of application code. There are a vast plethora of tools for generating code that have nothing to do with web frontends: why are they somehow less threatening?

Re: Figma to React

#113

Post by [deleted] »

unityByFreedom wrote: post #111
xyzzyrz wrote: post #101

Earlier quoted context omitted.

Plasmic ( https://www.plasmic.app ) enables this workflow—you can visually edit the design while editing behavioral code side-by-side—but with a different approach than what you described, since we want to include non-developers. (I work on this.)

On the pricing page, what is "Content Ownership" and why is that only granted for enterprise customers? https://www.plasmic.app/pricing/

[deleted]

Re: Figma to React

#114

Post by xyzzyrz »

unityByFreedom wrote: post #111
xyzzyrz wrote: post #101

Earlier quoted context omitted.

Plasmic ( https://www.plasmic.app ) enables this workflow—you can visually edit the design while editing behavioral code side-by-side—but with a different approach than what you described, since we want to include non-developers. (I work on this.)

On the pricing page, what is "Content Ownership" and why is that only granted for enterprise customers? https://www.plasmic.app/pricing/

This is organizational content ownership - we'll reword this to be more clear. This is to ensure that files can be managed by the organization even as users belonging to the organization are deprovisioned.

Re: Figma to React

#115

Post by rundmc »

xyzzyrz wrote: post #103
andratwiro wrote: post #16

This is why I use Framer, they have a built-in export to React function that is really powerful for early startups (as the whole tool is built on React) My team has been using our Framer export (with a few tweaks) as the actual final UI for our early product. Designing is as easy as in Figma, with the advantage that you have actual React components out of the box (working chart libraries, video components... any pack…

Framer is an awesome prototyping tool (I use it), but I would've wanted to know up-front that "export to React" comes with two huge caveats: - There's nothing stopping you from using it in production, but it isn't designed for this. What you create does not even use real layout, does not use normal HTML elements, etc.: see https://www.framer.com/support/using-framer/creating-real-ap... . - Inevitably in any real-worl…

I'm testing and absolutely loving Plasmic right now. Sent you a dm

Re: Figma to React

#116

Post by xyzzyrz »

rundmc wrote: post #115
xyzzyrz wrote: post #103

Earlier quoted context omitted.

Framer is an awesome prototyping tool (I use it), but I would've wanted to know up-front that "export to React" comes with two huge caveats: - There's nothing stopping you from using it in production, but it isn't designed for this. What you create does not even use real layout, does not use normal HTML elements, etc.: see https://www.framer.com/support/using-framer/creating-real-ap... . - Inevitably in any real-worl…

I'm testing and absolutely loving Plasmic right now. Sent you a dm

Thanks for the kind words, that's great to hear!

We are in a very fortunate position financially (multiple years of runway), and I am YZ. :) We also have companies big and small relying on Plasmic in production. Lastly, you fully own the code that you generate, and can always eject with clean React.

Re: Figma to React

#117

Post by unityByFreedom »

xyzzyrz wrote: post #114
unityByFreedom wrote: post #111

Earlier quoted context omitted.

On the pricing page, what is "Content Ownership" and why is that only granted for enterprise customers? https://www.plasmic.app/pricing/

This is organizational content ownership - we'll reword this to be more clear. This is to ensure that files can be managed by the organization even as users belonging to the organization are deprovisioned.

Yeah a little help popup might make it more clear. Like defining what happens when it is owned vs not owned. Without any description it sounds like your organization owns anything created by the tool except for enterprise customers.

Re: Figma to React

#118

Post by Aeolun »

tenaciousDaniel wrote: post #93
Aeolun wrote: post #75

Earlier 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?

You download a desktop app exactly once. You download a web app (almost) every time you navigate to the site.

I don’t know what your caching settings are, but my users download the app exactly once, and then only again if I push any update (or their browser cache randomly decides to clear itself, don’t really have any control over that).

Aside from that, they use the app literally their entire workday, so spending 5 seconds loading the thing isn’t going to hurt anyone.

Re: Figma to React

#119

Post by Aeolun »

RobertKerans wrote: post #97
Aeolun wrote: post #76

Earlier quoted context omitted.

Isn’t that just a basic node_modules folder?

It's normally slightly larger on average. I get you're joking, but the joke doesn't even make sense. A full build of LLVM + Clang is 15-20Gb, and yet, weirdly, IOS apps are not all that size.

Sorry, not joking at all. Since it’s a React app I thought it might literally be a node_modules folder.
Post reply on HN