The Library Analytics modal is unstable at scale, needs fully-featured export function

My (large) team uses hundreds of libraries, and we try to rely on Library Analytics daily to improve our design system. It can be quite unstable at that scale, with the modal being super laggy and unresponsive. It’s very painful for us to actually employ the data because of the tool-- it would be great for analytics to live in a dedicated tab with more fully-featured UX so that page load isn’t having to worry about populating a few hundred Teams (large org) in the background/at the same time.

In addition, it would be !LIFE CHANGING! if there were a way to export the full data-set for libraries to CSV!

Create a tagging system, allowing the user to tag library files within the org as being part of the dataset/design system. Then export to CSV:

Columns:

  • Total Instances
  • Inserts (at current intervals, or use the tool to customize intervals before export)
  • Detaches (at current intervals, or use the tool to customize intervals before export)
  • Detach Rate
  • Usage
    • Rank
    • % of Instances
    • Insert Survival Rate [Instances are what percentage of Inserts]
5 Likes

Agreed, the library tool itself has a lot of great data, but the implementation is lacking.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

I’d also like to see this featured in the APIs. Imagine automating the export and feeding it into either an app or a spreadsheet of some kind! OR into a living Figma file <3

1 Like

+10000 Analytics are often impossible to get because it regularly crashes. And even when it’s working, it’s so slow and tedious to transfer the data to another platform to analyze and share.

Suggestions

  1. Fix access issues in the current workflow
    a) if accessing via the org, don’t try to load all libraries. Force (and enable) users to search for a team or file name to find the libraries they need to avoid extreme latency and crashing.

  2. Add access to analytics from more intuitive places
    a) Create a shortcut directly from a library file to open its analytics directly.
    b) When viewing a team, add a tab next to members and settings for libraries, just like at the org level.

  3. Create paths to use data externally
    a) Enable a CSV download of a single library’s analytics based on specified dates (e.g. let me export just 2021, or just Q4, just January, etc. for annual, quarterly or monthly metrics
    b) enable analytics through API

  4. Develop automated reporting.
    I want Figma to email me the CSV of analytics for my library weekly, monthly, quarterly, and annually. Encode hyperlinks in the CSV file for every component to link to its frame in Figma.

  5. Serve our analytics needs in Figma.
    Create a customizable analytics & stats dashboard.

7 Likes

Any updates on this? Anyone able to find an easy way to export the data so you can track usage over time? It’s great for snapshot but not much else.

Unfortunately no. I’ve been extracting manual pulls into a sheet on a cadence out of necessity. Brutal! Pleaaassse help us Figma!

Oof. Yeah, that’s what I’m worried I’ll have to do, too.

Bein able to export the data as .csv or .excel for further analysis would be great.

I did this for a few select components recently. (As you all know, doing it manually is super painful so I couldn’t do it for the whole library)

But even with just a few components, the results were interesting and even surprising. I think there is a lot of value hidden here to make design systems better and more efficient. Also, supporting your decisions with data is always good. The window as of now is not really more than a proof of concept, but it could be developed into an essential tool for design.

2 Likes

We’ve been monitoring them - super useful. But also such a pain! Definitely need it to be full-featured!