14 Matching Annotations
  1. Jun 2024
  2. Jan 2024
    1. Although, the discussion above has only been considering Figma, we need to keep in mind that there are other design tools out there.
    2. Connecting with Figma should be done via an integration because not all orgs use Figma.
    3. Two way commenting is a good idea as it would allow a natural way of others to interact with designers without requiring to understand how to use Figma.
    4. Personally I think we could get a ton more benefits and would also be able to pull new users into our platform by finding better ways to integrate/link/connect/display Figma in our work item objects. Today the biggest downside for "Design management" is that it's basically just a copy of what's happening inside of Figma that has to be manually kept in sync and requires users to constantly switch back and forth:
  3. Dec 2023
    1. Fifteen months into the regulatory review process, Figma and Adobe no longer see a path toward regulatory approval of our proposed acquisition.Figma and Adobe have reached a joint decision to end our pending acquisition. It’s not the outcome we had hoped for, but despite thousands of hours spent with regulators around the world detailing differences between our businesses, our products, and the markets we serve, we no longer see a path toward regulatory approval of the deal.



  4. Nov 2021
    1. Because our product is written in C++, which can easily be compiled into WebAssembly, Figma is a perfect demonstration of this new format’s power.

      Figma is written in C++, which can easily be compiled into WebAssembly

  5. Sep 2020
    1. Figma is browser-first, which was made possible (and more importantly performant) by their understanding and usage of new technologies like WebGL, Operational Transforms, and CRDTs. From a user’s perspective, there are no files and no syncing that needs to be done with others editing a design. The actual *experience* of designing in Figma is native to the internet. Even today, competitors often talk about cloud, but are torn over how *much* of the experience to port over to the internet. Hint: “all of it” is the correct answer that they all eventually will converge on.

      Company's struggle to figure out how much of their experience they should port over to the cloud. Figma pioneered the idea of porting all of it and call it a "browser first" application.

      For the Figma user there are no versioned files and there is no syncing.

      Kwok claims all companies will converge to having all of their experience be "internet native".

    2. In many ways Figma’s Communities are a reflection of Github’s philosophy and intent, but built with design in mind. Duplicate a shared design, and a copy is instantly saved to your workspace and ready to be edited.

      The idea of a click-to-fork-repository was brought to Figma in the form of communities.

    3. This impacts monetization and purchasing at companies. Paying for a new design tool because it has new features for designers may not be a top priority. But if product managers, engineers, or even the CEO herself think it matters for the business as a whole—that has much higher priority and pricing leverage.

      If a tool benefits the entire team, vs. just the designer, it becomes an easier purchase decision.

    4. By bringing both designers and non-designers alike into Figma, they create a cross-side network effect. In a direct network effect, a homogenous group gets more value from a product as more of them join. In contrast, a cross-side network effect involves two (or more) distinct groups that grow in size and value as the other group does, too. Figma’s cross-side network effect between designers and non-designers is one of the primary and under-appreciated sources of their compounding success over the last few years. As more designers use Figma, they pull in the non-designers they work with. Similarly, as these non-designers use Figma, they encourage the other designers they work with to use Figma. It’s a virtuous circle and a powerful compounding loop.

      By bringing non-designers into the design process, Figma created cross-side network effects for itself.

      Where typically the designers would get their designer peers to use the tools they're excited about, now non-designers would experience the value and recommend Figma to designers and non-designers alike.

    5. Much of Figma’s current success is driven by its ability to spread within companies. Figma becomes more useful as more people within a company use it, driving advantaged speed and scale of penetration within companies. Figma was quick to recognize that the constraints on design at companies is often not a problem of pixels, but of people. Many of Figma’s competitors are great tools for designers. But that’s who they are for—designers. Figma is a tool for teams to design. Not for designers alone.

      Much of Figma's success is due to the fact that Figma spreads easily within a team, because the barrier to entry is so low (you only need a browser and a link).

    6. The core insight of Figma is that design is larger than just designers. Design is all of the conversations between designers and PMs about what to build. It is the mocks and prototypes and the feedback on them. It is the handoff of specs and assets to engineers and how easy it is for them to implement them.

      The key insight the Figma team had was that the design process involves a wide range of people, conversations and artefacts within an organization. Figma brings all those into one place.

  6. Jul 2020
    1. Deep Search Find the right file faster with the ability to search for files that contain a given word or phrase.

      Фигма теперь может находить файлы, которые содержат определённое слово внутри макетов. Проверил на «эвакуация», работает!