What is our primary use case?
I'm a senior developer, and I've been using Figma for almost four-plus years. I am still currently working with Figma, even for our projects; till today, we've been using Figma, especially for designing components.
The main use cases for Figma, especially that sits within the designer, is that we have a UX designer within our team who is majorly responsible for creating the user interfaces, such as the mockup screens. That's the case where we use Figma majorly right from defining the size of it, what the component looks like, and what the different variations of a specific component are. In a page there are approximately 12 components that we use, so we have all these different variations including the page layout for our website. The use cases also include the developer tool enabled within Figma which is very helpful for developers because we are able to extract the CSS from the components that the designer built, and we use it in our responsive pages furthermore while we develop.
What is most valuable?
What I appreciate about Figma is that it has the best features, such as working with integrated tools and external third-party tools. For example, currently we are exploring a way to extract Figma components into a codebase directly, and there are external plugins that support this, which is great. When considering a designing tool, Figma has the ability to help the development team build in a better and easier way.
I see that Zeplin can be used to extract Figma and turn it into documentation, which is very fortunate to have. I personally enjoy the grouping feature because you don't need to recreate the same components repeatedly; you can group them together and use them wherever you want. This feature gives me a feeling of micro-architecture thinking from the way it's implemented. I also appreciate how Figma allows us to share across teams, add comments, make modifications, and set permissions.
The impact of these plugins on my workflows is significant; documentation is a huge part. From the development perspective or the design perspective, it generally takes substantial manpower. Documentation itself could take at least two weeks, but with the support of these plugins alongside Figma, it makes our job much easier. We don't have to worry about extracting images, text, and all their variations because everything is completed in one mapping.
Regarding prototypes, I would assess Figma's prototyping capabilities in enhancing communication and feedback loops in our projects as an eight on a scale to ten. The use of UI libraries in Figma has helped to reduce interface building time for my projects significantly. When built-in libraries are supported, it's just a matter of using those components and libraries, along with the functions that are already there, so we don't have to write everything from scratch.
What needs improvement?
The area of Figma I would prefer to see improved is the responsiveness of the developer tool. When you enable it, you can extract variations, but these variations are not responsive. If I design a page, and there's a way to choose a view, whether it is on mobile or tablet, which then automatically converts it to the responsive layout of the page I design, that would save considerable time.
If I design for tablet view, and it automatically adjusts for mobile and different screen variations at the click of some drop-downs, that would be beneficial. Additionally, when we extract code, if it can provide variations for all different types in a responsive way using REM to adjust to different screen sizes and breakpoints, that would be extremely useful to have.
For how long have I used the solution?
I'm a senior developer, and I've been using Figma for almost four-plus years.
How are customer service and support?
My experience with the technical support of Figma is that it's entirely about designs that can be directly shared with stakeholders. Figma is the starting point of any project lifecycle because it all begins with UI design. Based on whatever we have in Figma, it serves as our source of truth to proceed with development.
I have escalated questions to Figma's customer service or technical support; not recently, but a while back, they sorted out an issue for us quickly. I remember there was one concern within our team about the feasibility of a specific approach, and their team responded promptly. We had a call, and they helped us resolve that issue.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
I have previously worked with other design solutions. While I was in India, we explored several tools. We used Adobe, and we even used Miro, although Miro isn't entirely for designing. Adobe was one we were quite satisfied with too, but I think Figma has more technical capabilities, while Adobe covers a lot of ground but isn't very dedicated to screen designs.
How was the initial setup?
To start working with Figma, my experience during onboarding was somewhat straightforward, although there was a learning curve. Initially, it was a bit overwhelming because I had no understanding of how it worked. However, one aspect I appreciated is that Figma guides you through all the options when you first use it, which was incredibly helpful.
Since I was unfamiliar, I took my time to click through all the options, and it guided me on what each option was about. This helped me learn grouping and how to segregate items, and knowing all the features was a bit time-consuming. But once I started to explore it, I found it really helpful. I haven't looked up many videos on YouTube, but it might be beneficial if Figma could integrate links to videos demonstrating how different components work.
What's my experience with pricing, setup cost, and licensing?
Regarding the pricing aspect, I do not know much about the pricing, setup costs, or licensing costs. It has been a year since I joined, and everywhere I have worked, Figma was already integrated. I think they went with an enterprise model, but I'm not exactly sure about the currently active pricing range.
What other advice do I have?
The disadvantages of Figma compared to Adobe are the capabilities when searching for plugins; we often need to rely on external ones, and it takes time to read documentation because the prototyping protocol is not very clear. If Figma could better support defining processes with external plugins, or even with the plugins integrated within itself, providing clearer and simpler documentation with readable examples and easy integration would be beneficial.
I would definitely recommend Figma, especially for the variety of external plugins that it supports. Those plugins are really a great asset. From a technical perspective, Figma has greater capabilities. Once you start to explore all these features and how to connect Figma with other tools such as Storybook and Zeplin for documentation, it's a tightly coupled system. There are many different functionalities available which make it excellent, and I will definitely recommend Figma over other designing tools for organizations because the support it provides is extensive and highly technically feasible, making your job considerably easier.
On a scale of 1-10, I rate Figma 8.5.