With the introduction of plugin editions in Craft 3.1, a standardised way of displaying the availability of more features in Lite/Plus editions is being proposed.
In a discussion with some other plugin developers today, we discussed possibilities for indicating the availability of Pro features in Lite editions of plugins. Commerce Lite currently hides any pages that are Pro features (Settings → Shipping; Settings → Taxes) and the only indicators of more features are the badge on the plugin settings page and the plugin page in the plugin store.

Some ideas we discussed are as follows. The intention is to be as unobtrusive as possible, while making it obvious that there are more goodies to be had.
The badge is displayed in places where pages with Pro features exist. The links could be either disabled completely, or enabled and link to placeholder pages. The mark-up for these badges already exists (in Utilities and Updates).


The placeholder page is a page that would be available in the Pro edition of the plugin. In a Lite edition the user could still visit those pages but would see a placeholder image of what the page would offer in the Pro edition. This image could take the form of a silhouette or of sample output, along with a call-to-action.

Perhaps there is a better place to post this question, but it would be great to get the opinion of developers as well as end-users of plugins that are currently offering or considering editions. Specifically, would you consider this a useful feature or more of a naggy feature?
This came up in our discussion, and I think the main reason for _making available_ some kind of standardization is just to give the user a good experience.
Plugins that may be free, but have a paid tier... or may be paid, or have another paid tier need:
This would solve the issues of discoverability & CTA that probably all plugin developers will encounter (including P&T with Commerce) in a standardized way that provides a good experience for the end-user.
We’re not adamantly opposed to it, but I’m not ready to establish a specific recommendation yet. I think plugins should play around with ideas first and we’ll see if a convention emerges from that.
Fair enough. In an ideal world, Craft developers and end-users will help guide us as to whether this is something they even want us to add to plugins and how they would like to see it implemented.
Only tangentially related, but I wish lite was always free, and the base paid tier was plus. Just so when people see lite, they know what it means.
Right now, lite can be paid, or it can be free.
@khalwat Interesting. We had a (very) long internal debate about edition names. We had sort of the opposite thought though – that Lite seems like it implies cheap (but not free), and that there should be some other tier below it reserved for free editions. But in the end we decided against that.
A moment interruption, so they got a chance to speak, lets me just agree with @brandonkelly and team here.
I suspect it's very nice (and commercially effective) to be able to offer a 'lite' version, without 'pro' features as the telling point.
And especially, it seems free should be: in the case when that word is used....
For commercial thinking, it's another differentiator...
@khalwat @brandonkelly "Lite" means cheap to me, "Free" means free.
That said, plugins should be able to have a "Free" edition.
That’s how we felt too @lindseydiloreto, but can’t stomach calling an edition “Free”.
Ah, looks like I misinterpreted you, @brandonkelly. And yes, 'free' has many effects on people.
Even a good thesaurus didn't help: introductory, unrestricted, priceless(!)...
hmm
Solo
And a 👎 for the idea to advertise Pro editions in the sidebar and client facing UI in general. What’s next? Sponsored by Xy banners?
What about the placeholder page, @carlcs, does that also feel commercial rather than educational?
And as a note, I'd rather avoid a discussion about Free/Lite editions in this thread.
In a restaurant where you ordered a main course only, they accept your decision. This placeholder feels like being served an empty plate with the message on it “Here could have been your appetizer”.
I don’t mind “being educated” in the plugin installation or plugin store area of the CP. The system report utility could be a place for curious clients to get this information, or with a redesign even have links to plugin (external) landing pages.
Thanks @carlcs, noted.
I had a waking thought this morning about the naming problem. I suspect the solution lies in separating concepts: getting pricing thoughts out of the names. Then price, is just price, no, and listed separately?
So we could have Stage 1, Stage 2, etc. for capability levels. And this means also that Stage 2 or N could also be free, if that's the provider's choice. Or could get free, or get a price, in some future. Flexibility.
Alternatives for 'Stage'? This is where @carlcs Carl's slant with 'Solo' gets important, as you want something friendly instead of project management words.
It might be good just to let the provider provide the names. As in 'Basic' or 'Base' or 'Introductory' etc.. Which also would let the clever do something like Tokyo Dawn did for their non-free versions of audio plugins, call those the 'Gentleman's Edition'...
To be helpful and guiding, Craft Store might propose a name which can be edited.
And then a neutral possibility for the default shows: 'Edition' . Thus, Edition 1, 2, etc., which could easily become Edition A, Edition B, Entry Edition, Édition superlatif, etc..
Thanks for the input @narration-sd. Pixel & Tonic have made it clear that the naming convention for editions is fixed, and as I previously stated, I'd prefer that this thread not become a discussion about that, but that it stay focused on the original question. @carlcs's opinion was quite clear and I'd welcome any other opinions on the proposed ideas.
Well, in my own thoughts I probably missed that, Ben. A little less formal than some I admit they are ;) -- privilege of elderness, I imagine...
Anyway, I think what I said won't hurt, as the future is always becoming, isn't it, and not less certainly with Craft and its persons...
Also, did quite appreciate what @carlcs Carl was getting at, to be sure
Most helpful comment
In a restaurant where you ordered a main course only, they accept your decision. This placeholder feels like being served an empty plate with the message on it “Here could have been your appetizer”.
I don’t mind “being educated” in the plugin installation or plugin store area of the CP. The system report utility could be a place for curious clients to get this information, or with a redesign even have links to plugin (external) landing pages.