Can I create challenge response kind license system
-
OK... is it applicable for subscription based things ?.. ok.. cool.
Yes of course, since it is a C/R system, you can use it what ever you want.
If you use Wordpress/Woocommerce, You'll also need a subscription plugin for it to take the recurring payments. Then on the vst plugin, you'll need to check if the subscription license is still valid or not with using the Woocommerce Subscription Plugin's API.
-
@orange said in Can I create challenge response kind license system:
OK... is it applicable for subscription based things ?.. ok.. cool.
Yes of course, since it is a C/R system, you can use it what ever you want.
If you use Wordpress/Woocommerce, You'll also need a subscription plugin for it to take the recurring payments. Then on the vst plugin, you'll need to check if the subscription license is still valid or not with using the Woocommerce Subscription Plugin's API.
I am only interested in the HISE part authentication. How can I check if the subscription license is still valid in HISE?
Can I get a minimal snippet ? -
@DabDab you will need to read and implement this;
HISE Development for hire.
www.channelrobot.com -
@Lindon No, I asked for a little snippet covering, How to make Authorization panel (Plugin side) ?
-
@DabDab if you can‘t implement it on your own based on the API provided by the server end point then don‘t bother doing this at all - it‘s way to complex and customizable for a snippet to work like you intend. There are enough snippets out here that show regular usage of the Server API.
I usually try to not discourage people to do stuff but I think this is a bit over your head and you‘ll save a lot of time by either letting this idea go or hire someone with the skillset to pull this off.
-
@Christoph-Hart said in Can I create challenge response kind license system:
@DabDab if you can‘t implement it on your own based on the API provided by the server end point then don‘t bother doing this at all - it‘s way to complex and customizable for a snippet to work like you intend. There are enough snippets out here that show regular usage of the Server API.
I usually try to not discourage people to do stuff but I think this is a bit over your head and you‘ll save a lot of time by either letting this idea go or hire someone with the skillset to pull this off.
Ohh.. Sorry for bothering you all. very sorry .
No problem. In one life people can not learn many things.
If I could HIRE somebody to do my work first I would purchase @d-healey courses on Patreon. People can not be lucky often. When he tries to survive after many closed one losses in Corona. People sometimes may not be lucky enough to learn somethings when he starts living in another country due to some situation.
Anyway, alright I amletting this idea goSorry for annoying you all @Christoph-Hart @d-healey @Lindon @Matt_SF & @orange with my silly questions repeatedly.
-
@DabDab You're questions are not bothering anyone, so no need to apologize and keep them coming, it's just that I've been through that process often enough (and see people getting stuck with stuff over their head) so I just wanted to save you some time. After all it's just license management shenanigans and not a core feature of your product, which I think is a better target to spend your resources on.
Also I think while the subscription model is a very (very) lucrative model for developers, end users (especially audio folk, myself included) really hate it and the most recent Waves clusterfuck shows that the majority of people are not willing to pay rent for their audio plugins.
There are a few companies that have a working subscription model, but what they have in common is a ridiculously large product catalogue (EastWest) or a large team cranking out content on a regular basis (Output). For single developers who are starting out, it's almost impossible to generate an offer that's worthy of a subscription (even if it's just a few bucks per month).
-
@DabDab Christoph is 100% right on point here.
What I suggest is to start simple and focus on delivering an excellent product that is 100% solid. Make it affordable to the masses. Then, based on user feedback, start adding additional features and functionalities via product updates. If you continually deliver improvements to your products, then your users will be happy to pay a fair fee for the updates.
As a user, I don't like the idea of paying for products I will never own. But, I am happy to pay to update the products I use if the developer continues to maintain them. That way, a developer is motivated to keep his products up to date, at the very least, and to improve them, while the user gets value for their money.
-
@Christoph-Hart said in Can I create challenge response kind license system:
(and see people getting stuck with stuff over their head)
I hope that's a direct shot so I can redeem myself :grinning_face_with_sweat:
Dan Korneff - Producer / Mixer / Audio Nerd
-
@Dan-Korneff No I didn't have anyone specific in mind, but I can imagine that everybody thinks that this applies to them (myself included) - it's just too easy to get lost in the possibilities today :)
