From the course: Figma: Handing off to Developers

Unlock the full course today

Join today to access over 22,500 courses taught by industry experts or purchase this course individually.

Asset planning: Code VS asset export

Asset planning: Code VS asset export - Figma Tutorial

From the course: Figma: Handing off to Developers

Start my 1-month free trial

Asset planning: Code VS asset export

- [Instructor] With Figma you can not only export image assets, but also code. So what is the best method, or what should you use when you have both available? As a developer if you've ever faced this question, you know the answer. But as a designer providing assets to a developer it might not be so obvious. In short if you can send it in code always use this first, because image assets will take longer to load in the official application. Having code versus image assets does have a big impact on the performance of the final application. So if you have code available and don't need an image, please do send this first. For example if you design a gradient background, use code as opposed to sending the image of the background. If your background is a natural image of a surfer, like what we have in our sample project, then send the image. But beware of the performance cost it adds to the application. As we go through…

Contents