Packaging Plugins and Apps Workshops Now Available

[David Healey]

@resonant Most of that would be server side and would be very specific. I've already made a video about downloaders though.

https://youtu.be/ZLmCceU7QSs
https://youtu.be/mqGsqJoBxiQ

I just remembered I also posted a video on Patreon discussing how Rhapsody connects to a server and manages downloads. That might be useful for you.

https://www.patreon.com/posts/how-rhapsody-to-122636217

[resonant]

@David-Healey said in Packaging Plugins and Apps Workshops Now Available:

@resonant Most of that would be server side and would be very specific. I've already made a video about downloaders though.

https://youtu.be/ZLmCceU7QSs
https://youtu.be/mqGsqJoBxiQ

I just remembered I also posted a video on Patreon discussing how Rhapsody connects to a server and manages downloads. That might be useful for you.

https://www.patreon.com/posts/how-rhapsody-to-122636217

That's useful thanks.

Wouldn't it be possible to create a total customzable template that developers can easily use?

For users like you who use WooCommerce, a compact downloader/installer/license activator that sends a call to the server via the REST API, provides a list of purchased products, and activates licenses. Even customizable product links would be possible.

It could be sold as a template.

[David Healey]

@resonant I think there are too many variables for a one size fits all solution.

Two major factors would be:
What licensing system are they using? And where are they hosting their downloads?

Every system has a different API. You can go through WooCommerce for some of the download info but if you want to get specific details about files, like file size for example, you need to talk directly to the hosting service.

I think if you can make something generic that everyone can use then it would be better to make a single app for all, rather than every developer having a separate app. We discussed this on the forum a few years ago and I started building a prototype. A big problem is though that everyone wants something slightly different.

[resonant]

@David-Healey Yes license activation might be slightly different for everyone. But although some things are different, the basics are the same:

• Logging into a Woocommerce account (JWT Auth..etc.)

• Listing purchased products (My Products)

• Pulling and presenting the product list from the Woocommerce store (All Products) with product image and description

• Installing/uninstalling/updating products

• Even License activations (with the Woocommerce Licensing plugin you use, your way). If the user has different API endpoint links, he can change the links.

If you can do this properly, you can sell lots of licenses to the developers and every developer need this.

[bendurso]

@resonant Managing all of this takes quite a bit of time, and even with a template, I think it would be difficult to keep it updated. Maybe with AI will be a bit easier now, but still.

You can do all of this with Moonbase and much more. I moved to Moonbase two months ago and I love it.

[jeffd]

@bendurso are you using juce 8 with moonbase?

[bendurso]

@jeffd nope, JUCE 6

[jeffd]

@bendurso i setup a mock moonbase storefront on my squarespace website,
but i was curious about the JUCE module that can work with License activations, which i think only works with juce 8?

[Sifres]

@jeffd Yeah I would like to know that as well tbh. Was it hard to get it working?

[jeffd]

@Sifres
The storefront was easy to setup, but
I have a half finished website. I was just testing it out, but seems to be really great so far.
...and I havent tried that JUCE module that can work with License activations.