By all accounts, Figma has been an amazing tool for designers. We've used it extensively at 37signals, and I'm sure most every other software shop has too. Adobe didn't pay $20 billion for nothing. But we don't do the bulk of our design work with or in Figma when developing Basecamp or HEY for the web. That's all done directly in HTML ...

Not sure I entirely agree with the article but there is a good point in there about understanding the constraints that development is bound by. But it takes a lot for designers to become proficient enough to do what they need in code, just as the opposite is true with developers doing design.

  • h00x@lemmy.worldEnglish
    1·
    1 year ago

    I’ve been doing this for the past years as freelance webdeveloper and designer. I can really make a difference with my clients in terms of speed. No more handovers from designer to developer. I just get a wireframe and out comes a working page. I do agree that in design programs you are not bound to limitations. I do see a trend in Figma limiting the freedom of designs by standardisation in turn for speed of design and development. But what use does Figma then hold in the end if you can just do it in code? Or are we going to let Figma create the responsive frontend instead of a frontender building it?

    • NoiseColor @lemmy.worldMEnglish
      2·
      1 year ago

      I guess that the latter is much more likely, that Figma will become the creation tool. That is the direction.