How I made my plugin with zero previous knowledge about plugin development

Was it easy? No. Was it enjoyable? Generally, yes.

Here's how I approached this project – it's not for those who give up easily.

A Little Background.

I've been creating music for almost three decades. At over 50 years old, I've spent much of my life immersed in this world. When I was younger, I thought technical skills weren't my strong suit. I would never have created an effects plugin if not for tools like ChatGPT.

I decided to start small and focused, usually a good approach for something new. For inspiration, I turned to my trusted hardware sampler, the Roland SP404SX. It's a beat-making device with distinctive live effects, including my favorite, the Vinyl Sim effect, which I've used on countless tracks. So, I set out to simulate it.

Discovering JUCE.

I don't recall how I stumbled upon JUCE – perhaps a quick search or maybe a suggestion. JUCE is a cross-platform tool for building audio applications. It's built on C++, which was initially intimidating, but with ChatGPT's help, I took the leap.

Early Challenges.

It wasn't a smooth start. I was used to building iOS and Mac apps, which Xcode handles well, but cross-platform development was new to me. I learned some lessons the hard way, and here are a few of the biggest takeaways:

• Projucer is essential for managing your JUCE project.

• Avoid iCloud for development files. I encountered issues early on that disappeared once I moved my work out of iCloud.

• Multiple OS Machines: Going cross-platform means you need access to different OSs. I used a MacBook Pro M1, a Windows 11 machine, and an Intel MacBook Pro from 2017.

• Separate Projucer Projects: For each platform, create a unique Projucer project. It saves time and headaches.

• Testing is crucial. Test on all intended platforms and in various environments.

Skip Competitor Research.

If I had started by researching competitors, I might never have pursued this project. My approach is more about learning and personal growth than competing. This is a hobby, a way to challenge myself and enjoy the process.

Building in Public.

I connected with a music forum in Sweden where I've been a member for years. Their feedback shaped the plugin, and I plan to offer a discount as a thank you. Building in public is about listening to input but also staying true to your vision. Your version 1 is ready when you say it is.

Distribution Approach.

Distributing a plugin is a journey on its own. Here are a few essentials to get started:

• A Website: This might be your main sales channel, so make it count. I've used RapidWeaver Classic for years because it works for me.

• Payment and Delivery: I use Paddle Billing. It's easy to integrate, with features like discount codes that simplify the process.

• Publish on KVRaudio.com: They support indie developers, and a presence here shows you're serious. Make sure to have a solid website before applying.

What's Next?

Absolutely, I'd do it again. I'm just waiting for the right idea that fits my Lowfi Dojo vision.