Figma Reviews

My main use case for Figma is to design pages for the website and new features and functionality. I haven't been doing it so much lately, but I definitely used to use it quite a bit more, designing new features, although I don't actually do the design, as there's a design team that works on it.

One of the projects I worked on with Figma is a CMS system.

Figma really helped clarify the requirements during the design and planning of the CMS for analysis articles because the designers would create a visual for the CMS, how it would work, and then we would iterate on it. It was a combination of design and then collaborating and iterating on the design.

The best features Figma offers include the ability to create a design system, which the designers really appreciated, as well as the organization of design assets for the purposes of development. I would say those are the two main features.

The design system feature and the organization of design assets help our team by ensuring that the team is better able to conform to the design system. By managing the design system within Figma, it's easy for other designers to pull out materials and to quickly build new designs based on our existing design system.

Figma has positively impacted our organization because we just live in Figma and certain teams just live in Figma all the time, which has really allowed us to make sure that our designs are consistent and that there is a standard way of producing those designs and consuming those designs. It's standardization of the design process and it has an influence on our entire website.

One negative aspect about our main use case or how we used Figma in that project is that the notifications were a little bit difficult to follow. For example, if a designer marks up some part of Figma, we don't necessarily know about it on the product side, and it's hard to keep track of all of that, especially when we use Slack for our regular workflow.

Figma can be improved by enhancing the notifications to let people know that there's a new message in Figma, just to make sure that people see the notification that it's meant to go to the person who's meant to receive it.

I have been using Figma for probably a couple of years, about two or three years.

The advice I would give to others looking into using Figma is that it's a great tool. I rate Figma seven out of ten.

My primary use case for Figma is designing a hybrid superannuation solution. It involves a web-based and human-based approach, utilizing Figma as the product's base components.

The platform's most valuable features are its collaborative capabilities and interactive components. Sharing prototypes with multiple stakeholders and receiving immediate feedback is highly beneficial. The interactive features are useful for checking how designs work on different devices.

The product could be improved by addressing performance issues such as slowness, particularly with heavy or high-resolution images. It can lead to lag and slow file loading times.

The product can sometimes be unstable, especially with heavy files and high-resolution images, leading to lag and performance issues.

The platform is scalable for small—to medium-sized enterprises.

I previously used BlendedViewer but switched to Figma due to its superior collaborative features.

The initial setup was straightforward, primarily requiring compatibility with browsers or Windows versions.

We implemented the product with the help of our in-house team.

Figma's pricing is reasonable and accessible for both small and large firms.

I evaluated other options, such as Adobe XD, and found Figma more intuitive and interactive.

While Figma is effective, managing file sizes and layers to mitigate performance issues is essential.

I rate it an eight. 

There are two primary use cases. It is used to be able to visually present ideas for different features with our existing templates that we already have created inside of Figma. We also use it to create clinical prototypes for user testing.

The way you can create templates is probably most helpful because it gives us a way to very quickly play around and test ideas and different types of layouts. 

One of the areas for improvement is the onboarding experience. When you first starting using Figma, it can be a little confusing. It would be useful to have some guidance and direction. 

I have used this solution for a year and a half.

This is a stable solution. 

Prior to Figma, we used PowerPoint.

The initial setup is straightforward. 

Don't be intimidated by the user interfaces, especially if you're using it for the first time. You usually have to spend three to four hours playing around to get a full grasp of how it works.

Once you get used to using it, it is very intuitive.

I would rate this solution a 10 out of 10.

I use Figma on a daily basis to prototype web Interfaces. I'm a UX/UI designer.

Productivity has improved. The tool I used previously (Adobe XD) did not have a good performance and sometimes it crashed. It had bugs. Figma, in addition to being light, has very good performance. It hardly has bugs.

The ability to add a hover effect is great.

There's a folder system within a project/file.

File sharing is easy.

Sometimes the prototype view menu gets in the way of navigation, especially if the prototype has a menu at the top, and most of the time it does.

I've used the solution for approximately two months.

The solution hardly has any stability problems.

The scalability is very good.

I still haven't reached out to technical support.

Neutral

I used Adobe XD. I switched to Figma due to the fact that it is better in many ways.

The initial setup was simple.

We handled the setup internally.

I have not seen an ROI.

The costs are worth it if you have a team of more than two people or many projects.

I did not look at other options.