Congrats to the team here. Let it be a lesson for anyone worried that “their idea has been taken” or “there already solutions for this” out there.
Figma files for proposed IPO
61–70 of 255 posts
Re: Figma files for proposed IPO
#62Earlier quoted context omitted.
> The rendering engine handles curve rendering, images, blurs, masking, blending, and opacity groups, and optimizes for high visual fidelity. And thats how you get designers whining that their design looks great in figma but not in a real webpage
This, so much this. I’ve been thinking about a box-first approach to design tooling. The overall layout workflow would consist only of adding boxes (block-level elements) to a blank web page, or inside other boxes. Boxes could also contain other elements like inputs, buttons, images, etc.
Huh?
Re: Figma files for proposed IPO
#63And the cycle continues. Who's working on the "Figma but not enshittified" at the moment?
Honestly the cycle continuing is a breath of fresh air relative to the AI-ification of our entire industry.
Re: Figma files for proposed IPO
#64If you’re tired of it all, and the inevitable, and you have agency, try penpot.app
Also Sketch [1]. Everyone abandoned it when Figma became the pOpUlAr tool, but I still use it every day, nearly 15 years later and it's continued to improve. [1] https://sketch.com
I never switched away from Sketch for personal use. Figma’s collab tools are great, but I find it somewhat clunky for usage beyond prototyping (such as creating image assets).
Figma’s cloud-first nature never also sat well with me… I still have the source PSD files for my earliest works from 25 years ago, which can still be viewed and edited perfectly. Will that be true of my Figma documents in 25 years? It’s not even a question with Sketch.
Re: Figma files for proposed IPO
#65[deleted]
Re: Figma files for proposed IPO
#66They don't link to the Form S-1 prospectus from their announcement, but it's publicly available at https://www.sec.gov/Archives/edgar/data/1579878/000162828025... Their highlighted metrics page: $821M LTM revenue, 46% YoY revenue growth, 18% non-GAAP operating margin, 91% gross margin. It's an incredible success story, and the engineering they did upfront (primarily led by co-founder Evan Wallace) that set the stage…
As a former figma engineer, let me be the first to say that Evan Wallace is, in fact, a legend. A true 100x-er. There's still parts of the codebase basically no one at Figma really understands that Evan wrote back in the day. One example of that is something like he adapted a shader we use internally to render font glyphs, which no one has touched ever since. The engineer who told me this had spent a few days trying…
That's... not a screaming testimony, dude.
Re: Figma files for proposed IPO
#67Congrats to the team here. Let it be a lesson for anyone worried that “their idea has been taken” or “there already solutions for this” out there.
Actually, that's a fair point! Thanks for making it :)
Re: Figma files for proposed IPO
#68They don't link to the Form S-1 prospectus from their announcement, but it's publicly available at https://www.sec.gov/Archives/edgar/data/1579878/000162828025... Their highlighted metrics page: $821M LTM revenue, 46% YoY revenue growth, 18% non-GAAP operating margin, 91% gross margin. It's an incredible success story, and the engineering they did upfront (primarily led by co-founder Evan Wallace) that set the stage…
As a former figma engineer, let me be the first to say that Evan Wallace is, in fact, a legend. A true 100x-er. There's still parts of the codebase basically no one at Figma really understands that Evan wrote back in the day. One example of that is something like he adapted a shader we use internally to render font glyphs, which no one has touched ever since. The engineer who told me this had spent a few days trying…
I don’t mean this to throw shade, but isn’t the whole point of writing code that someone else can understand it? I worked with some crazy smart people when I was in academia, and when one of them left it was not worth trying to maintain what they left behind because it was so often inscrutable.
Re: Figma files for proposed IPO
#69Earlier quoted context omitted.
> The rendering engine handles curve rendering, images, blurs, masking, blending, and opacity groups, and optimizes for high visual fidelity. And thats how you get designers whining that their design looks great in figma but not in a real webpage
This, so much this. I’ve been thinking about a box-first approach to design tooling. The overall layout workflow would consist only of adding boxes (block-level elements) to a blank web page, or inside other boxes. Boxes could also contain other elements like inputs, buttons, images, etc.
Don't quite follow you, but if you're talking about a box-based layout for the web, that's a little overly simplistic as "the" layout, but is already possible. Keep in mind the historical underpinings; web documents were always more like scrolls than screens.
Re: Figma files for proposed IPO
#70They don't link to the Form S-1 prospectus from their announcement, but it's publicly available at https://www.sec.gov/Archives/edgar/data/1579878/000162828025... Their highlighted metrics page: $821M LTM revenue, 46% YoY revenue growth, 18% non-GAAP operating margin, 91% gross margin. It's an incredible success story, and the engineering they did upfront (primarily led by co-founder Evan Wallace) that set the stage…
> The rendering engine handles curve rendering, images, blurs, masking, blending, and opacity groups, and optimizes for high visual fidelity. And thats how you get designers whining that their design looks great in figma but not in a real webpage
Designers complaining that their pixel perfect mockup in any software not aligning with layout in actual browsers is a literal decades old complaint.