(README) what are the main benefits of using this vs using the official web app?

[magicgoose]

Since this is based on Electron, it's unlikely that it can have better performance compared to browser, am I right? If so, there must be something else that makes it better than official webapp, then what is it? Couldn't find it in README.

[leinardi]

System fonts support.

[bla9kdog]

I don't see any advantages, since you can enable system fonts support with this: https://github.com/Figma-Linux/figma-linux-font-helper

[NNBnh]

You can use it offline... maybe?

[magicgoose]

You can use it offline... maybe?

I don't think so... I think it could not (last time I tried). But recently I was unable to use it at all, so I don't really know if it's supposed to be able to do that. Hence the question.

[TheRafaelFarias]

I don't know you, but i prefer to have more applications in dock instead of using 1 application (browser) with a lot websites loaded.

And if you is using Chrome or Chromium based browser , every page have one clone of every extension loaded

That is why i like to use this application

( If is a bad english, sorry, im brazilian and my english not is 100% yet )

[Israel-Laguan]

I don't know you, but i prefer to have more applications in dock instead of using 1 application (browser) with a lot websites loaded.

And if you is using Chrome or Chromium based browser , every page have one clone of every extension loaded

Actually the "extra extension" point is the more appealing one to me.

[aharish]

I'm coming from the perspective of using this on a single board computer (a Raspberry Pi 4 with 4GB of RAM). When loading FIgma in the browser, the processor would be bogged down with the open tabs, and extensions for each tab. Often, while working on artboards with images (say while designing or prototyping a website), it was hard to work because the processor was being bogged down by the load.

However, when I use the Electron app on the Pi, I see improved performance in the above use cases to the point where designing on a low powered computer is not a pain. Of course, in my case I am keeping my expectations well in check (it's a low-powered ARM computer meant to be a learning device after all), but for people that are getting started with UI/UX design and using a low-powered laptop (something like 2-4GB of RAM and a Celeron or Core i3 processor), then this will be a more ideal way for them to get started IMO.

Also, this is a sand-boxed Chromium/Chrome browser, which does mean that on Linux it takes up lesser resources than Firefox does (Firefox uses close to 800MB-1GB of RAM once started, whereas Chromium uses about 300MB of RAM once started; on Linux this has been my experience at least).