Plugin Directory Rules

Projects Directory
7

I am afraid that I completely disagree with @anon71687268 about the need for a freemium category. I think it’s absolutely essential.

As a user, I never consider using any premium plugin that I cannot try out first. So the distinction between freemium and pure premium is very important to me. I can investigate those in the former category, while completely ignoring the latter. If you merge the two, you are expecting me to have to go through each one to find out which form of offering it is. That negates a major part of having a directory in the first place. There is certainly no benefit to users in merging the freemium and premium categories.

But there is no benefit to developers either. In fact, if you merge the two, you take away any incentive for the developer to offer a free version, while also disincentivizing those who want to offer a free version from having a premium upgrade.

So I think it’s essential to stick with @azurecurve’s original idea of three categories: free, freemium, and premium. Transparency is fundamental here just as much as it is with every other aspect of ClassicPress.

2 Likes
8

I also think that is important to have the Freemium category and why I think that being an author of a Freemium plugin?

I think it’s more important for the user than for the author, for me it doesn’t make a difference because there are always other ways to tell the user that there is a premium version with more features.

Why is it better to download a Free plugin that has a Pro version vs Just Free version?

Probably it has better support since there is a premium version that keeps the money rolling so both versions (Free and Premium) are actively developed and supported. So its a more stable solution that helps the user to decide.

At the end of the day is about giving options to the users, and having a Premium version of a Free plugin is always cheaper than customizing the Free version for specifics(that sometimes still happens with the Premium version).

And if the hosting is made in Github don’t see any problem of having also the Premium versions.

1 Like
9

For what it’s worth I also agree with having a freemium category. I use a lot of plugins that are just that and pay for the extra features on sites that need them.

Would you exclude a plugin such as Elementor simply because it has optional upgrades?

10

I can update 17 to include these requirements.

I’ll wait for more on 11 before making any changes.

1 Like
11

I’m happy to add back Freemium to the rules,if that is the way the community is leaning,but don’t want to keep toggling between them.

1 Like
12

Let’s have a poll on it on it.

How should the categories in the plugin directory be broken down?

  • Free, Freemium, & Premium
  • Free & Premium only

0 voters

In the second option, freemium plugins would fall under the Premium category.

Note: this poll is to see which the community favours, and is no way an official vote. It is used to allow the community to join in on this discussion without the fear of choosing sides.

Edit: edited for clarity following feedback, the edit is made available so you can see the original.

3 Likes
13

To me, the difference between premium and freemium is semantics. Update: I meant interpretation, not semantics.

1 Like
14

To me, “freemium” means “this plugin has some features that are available for free and some that are paid”.

“Premium” means “the entire plugin is paid and does nothing (you can’t install or use it) unless you’ve paid”.

5 Likes
15

This is the definition I use.

2 Likes
16

I’ve done away with the freemium verbiage on my end in favor of using the term premium, but am happy to wait until the directory opens up to premium plugins.

1 Like
17

Maybe I’m wrong but for me the Freemium isn’t about the plugins, it’s about the business model. Freemium is a business model, not a plugin version or something like that.

Just like Google that has their Free stuff and try to upsell the premium features.

In terms of code doesn’t make sense to include blocked features(and it isn’t allowed in the WordPress repo) to potential thousands of people that will never use that code.

So usually there are 2 versions. The Free and the Premium. That’s my POV.

4 Likes
18

I disagree with the logic (to me, Google is a premium service even though it’s free; it costs your data, habits, etc.) but do agree with your conclusion. The way I want to do it (on my end) is to offer all my premium plugins for free (premium, because they’re exceptional quality, not because they cost money) with the option to upgrade to a paid version for those who want more features or even just to support the work.

1 Like
19

My mind was talking about that Google that maybe 15 years trapped us with the Free Email, etc. At that time all seemed beautiful and “Free” :slight_smile:

1 Like
20

I figured. :slight_smile: The old adage applies, “If a service is free, it’s us who are the product.”

3 Likes
21

haha I like that one. Will take note.

1 Like
22

It always seems odd to me that, when discussing code, developers want things to be semantic. Then, when we get to discussing things in English, meaningful distinctions are dismissed as “(mere) semantics.”

3 Likes
23

I think I should have used the word interpretation, rather than semantics.

2 Likes
24

This is exactly my opinion as well. I’m not going to pay money for a plugin that may or may not work for me. Freemium versions give me a chance to check out the developer - is it buggy? are there spelling mistakes? (my pet peeve), etc. I have cast my vote!

That’s my interpretation too.

1 Like
25

I believe you have misinterpreted…or I haven’t been clear. My premium plugins will be free. Anyone can download and use them without paying a cent. They will be functional plugins. For those who upgrade to a paid version, they will get more features, dedicated support, et al. To clarify: it’s my work that is premium, not necessarily the features in any given plugin I release. Subsequently, I will consider all my plugins premium, whether they’re completely free or not. :slight_smile: I think we’re essentially talking about the same thing, but I’m just moving away from the freemium terminology because I feel it’s gimmicky and implies that free plugins are lesser.

1 Like
26

That’s freemium. :grin:

I don’t mind moving away from that terminology, but then we need to think of some other way to describe the above that makes it very clear to the user.

1 Like