What next? Paid components?

I love Figma, but…

  1. Paid Dev-Mode — It’s not FigJam, it’s not a separate product. It’s part of the design.
    It’s an artificial separation to appear valuable. The only value is that you don’t need to press “Alt” to see spacing - that’s it. You can’t force all developers to pay for so many places.

:ice_cube: Switching modes frezes.

:sweat: The links from the developers opens in dev mode, although I was on this page in edit mode

:left_speech_bubble: Annotations? Really? Do you remember that there are comments? Maybe they were the ones that needed to be improved?

:keyboard: 25$ seat for auto-«Alt» button???


  1. Limitations of Variables

:coin: Functionality is completely disabled for free plans, how are designers supposed to be trained to do this? From YouTube tutorials?

:name_badge: 4 rows for Pro. That’s enough for basic use, but the limitations are strongly felt. Every time you try to open the fifth column you are told you to pay more


  1. Team list — impossible dark-pattern level to imagine

:clown_face: “Edit requests” are no different from “View requests” and can easily be confused, you can give editing rights even to those who don’t need it.

:clown_face: There are no filters in the team list to see who has edit permissions

:clown_face: Any designer with edit permission can be given edit anybody. This cannot be tracked when you have 20 or more designers. And the admin will not be notified in any way about the added new editors (notify is paid in Organization plan :clap: :clap: :clap:)


Some ideas for future updates

  1. Limit components — 1000 for Pro, 10000 for Interprise.
  2. Paid color styles — 4 folders for Pro, 40 folders for Interprise
  3. Paid view accounts — 1000 views \ 5$/mo
  4. Paid prototyping mode — 25$/mo per seat
  5. Figma Creative Cloud Suite — Edit + Proto + Dev modes just for 75$/mo per seat instead of 95$! :dizzy:20% off!!! :dizzy:
24 Likes

Just saw that dev mode doesn’t work anymore for the devs and you have to pay this is ridiculous, I love Figma and we switched over a few years ago but they are nuking the product and its users, us, aren’t happy and it’s adding more work to our plate and more costs that we might switch over again and I will lose it if I have to redesign the entire thing in yet another software

7 Likes

These are very stupid restrictions, completely artificial, just to suck as much money as possible out of users. Give us the variables, remove the limit on the number of files and pages (3 pages, really???), give us the devmod. Don’t embarrass yourself, Figma.

6 Likes

I mean, what else did you expect from the closed piece of software that literally stores your personal and work files in the cloud?. This is a serious threat to privacy and security. They can literally ban you for no reason, and there have already been several cases on design twitter. They make the dev-mode a paid feature today, and the next thing could be the color picker or something like that. And this applies to every cloud service where you have no control over anything. Get real.

3 Likes

It feels like the whole pricing strategy for new features was half baked at best. I am not expecting new product features to be offered for free, although they could be free quality of life updates, but at least have a reasonable pricing point. I have worked with many devs (literally in the hundreds) in the last two decades, and I do not remember one dev who actually reads those code blocks from the design software. They especially take it as offending in most cases. The good use cases like annotations, which is basically making comments visible with some nice visual features, is suddenly $25 to view? To View? Really?

4 Likes

The problem is; I have access to annotations as a full seat designer. I prepare the designs, I prepare the annotations to show them; and suddenly, the devs cannot view it because they need to pay to see. They are there to view it, not to create, just to see.

So, I am paying for it, they are paying for it; we are being charged twice for the same function. Or I am being charged twice: once to create, and once to show. If I want to show this to a client with their own development team separate from my organization, we are asking to charge them to see their commissioned work. You can argue that it can be added to the cost, but it is a plain example of dark pattern.

Figma became Adobelized without the acquisition by Adobe.

8 Likes

I guess they are trying really hard to move us back to Sketch :slight_smile:
Freaking venture capital world, it’s so toxic it’s killing products.

Here’s the recipe:

  1. Create a product that is cheaper and better at solving a problem (Figma vs. Sketch)
  2. Attract almost all the professionals in the field, create a fanbase
  3. Start charging for previously free features, now that the exit barrier is too high for users to even think about leaving
  4. Call Adobe and try to sell and become a billionaire
  5. Fail!
    5.1. Cry in fetal position (optional)
  6. Get frustrated and start charging for everything so you can become more profitable or maybe a bootstrap billionaire
  7. See all your users start to hate you and switch back to their previous alternative or any new alternative
  8. Cry again in fetal position (not optional)
  9. Repeat!
2 Likes

Funny that there is zero reply in this thread from the community managers. Glad it’s not my job, but the lack of engagement is telling.

Maybe it’s just me, but getting a feeling of if they are “learning how to do this better and please bare with us” or if they are “sucks, but makes us money” is interesting.

2 Likes