[LAUNCHED] All plans should offer more than 4 variable modes

+1 on this one, I don’t understand the mode limitations, especially when you work on Figma plugins.
I use modes for responsive (5 breakpoints), not just light & dark.

Hello everybody, I posted here a few times already as a frustrated user, but also as someone who tried to create a solution for this longtime ignored issue. This lively discussion and also my own needs led me to a conclusion, that it’s worth it to create a decent workaround to this problem until Figma changes its ways.

It took much more time than I originally expected, but I believe I can call it a success, despite few limitations the plugin still has.

What kind of surprised me though, is that the response from the community isn’t exactly what I expected.
I shared the link and some info about the plugin here a few times, it had a few clicks, but almost no reactions, no feedback, no conversions (someone even flagged me as a spam once 😀). I’m really curious why is that.

So today, I’m kindly asking you for your constructive feedback. What is the reason you didn’t try the plugin, or didn’t convert to a paying user after the end of free trial?
Is it the price or the sole fact that it’s a paid plugin? (3$ a month currently)
Is it some specific limitation of the plugin?
Is it something not working as expected? A bug maybe?
Is it something else?

I know a plugin is still a workaround, but this one seems at least to me as a pretty decent one. It simulates the native experience very well and it offers even more modes than the expensive enterprise plan, for a fraction of the the price.

Let me know what you think about it, and if you haven’t tried it yet, give it a shot 😉

https://www.figma.com/community/plugin/1404783727338541788/infinite-variable-modes

Thanks,
Michal

Yes, it was definitely a conjoin analysis study.

My my takeaway though is from the range of options presented. When I’d taken surveys like that before, I don’t remember them being as divorced from reality. The combos were reaching farther into and staying longer in the realm of what I’d consider absurd.

Honestly your plugin flew under the radar for me. When I saw it mentioned recently in this thread, I thought it was actually a different plugin that didn’t look like it would solve what I need to do with modes.

I see now that it’s not the same one, so I’m going to test yours now. Thanks for trying to make this and following up with your posts about it.

@dvaliao is anything happening with this? Can you give us an update if Figma is tracking this at all on internal project boards?

There is one line missing, right ?

The comment they’re ignoring

Hey Michal.

I appreciate you taking the time to make a plugin to try solve this but this is the problem… its a hacky solution that adds other costs in-terms of training etc. When a feature exists - but is being gatekept for enterprise deliberately stopping the target audiences work then thats a problem worth shouting about. I cant expect the companies i work with to step up to organisation rates, and i cant expect them to aintain plugins as part of their stack to make things work.

the issue is Figma hasnt cared about users since preadobe deal. it only cares about enterprise lock-in. So lets all move to penpot

Hi Jack, thank you for responding. I absolutely agree that this isn’t something that should be handled by a plugin. I also agree that such policy is absolute nonsense (greetings to Figma 👋 @dvaliao). But I also find this solution as a viable option for many designers until Figma comes to their senses.

Adding my voice. UNLOCK VARIABLES, or at least give org level more. Not really sure why the limitation. Storage is cheap. Feels like since the failed Adobe buyout the investors are trying to sqeez as much money as they can from Figma at the expense of the people using the tool.

Remember Figma, you can go the way of other tools if you become like Adobe.