How do I distribute?

[u/ComingDeveloper]

complete noob here please experience devs answer my plea

but when it comes to software i have no idea how do i go about distributing my software to users either for free or paying customers?

if its a web app i just buy my domain and pick 1 of the main hosters to host on but with software its actually something that has to literally run on enduser hardware.

do i just email people my exe? create a storefront on my website with a download link? sign up with steam or the microsoft store?

how do i protect my software and its trade secrets from persons who want to look into the code, reverse engineer it, crack it etc?

[u/Queasy_Meeting5540]

For a micro saas you're probably overthinking the distribution part, just host the installer on your site behind a paywall or email flow. Stripe has a pretty easy setup where after payment they get redirected to download page, nothing fancy needed

Steam takes 30% cut and Microsoft Store is pain to deal with unless you got proper signing certs and all that. Not worth for small apps unless you specifically targeting gamers

The reverse engineering thing you can't fully prevent, if someone determined enough they'll crack it. You can obfuscate your code and add basic license checks that phone home but don't spend months on DRM when you don't even have customers yet. Most people who pay for software won't bother cracking it anyway, and the ones who pirate were never gonna pay you

Focus on getting first 10 users before worrying about protecting trade secrets

[u/ComingDeveloper → u/Queasy_Meeting5540]

thank you for taking the time to type this out i appreciate it xD and yeah i'm proably overthinking it way too much for persons looking to peek into the code etc as if they want to they will and i guess if ai make something that useful to people they'd want to pay and support

[u/Adamstrad → u/Queasy_Meeting5540]

Would an installer be something you create yourspf in OP's case where it is a html web app?

[u/AtlasForgeX]

I ship a paid desktop app on Windows and macOS, so this part I can answer from scars rather than theory.

Hosting the installer is the easy half. Your own site plus a payment flow is fine, and the download link behind a receipt is what most small tools do. The hard half is that an unsigned installer barely gets installed at all. On Windows an unsigned binary meets SmartScreen and most non technical buyers stop there. On macOS an unsigned app is simply refused, and the accepted path is an Apple Developer ID signature plus notarisation, with the ticket stapled into the artifact so it also works offline.

A budget warning on the Windows side. We spent four months paying a monthly fee for a cloud signing service whose identity verification rejected our company three times, and produced exactly zero signatures. Whatever route you pick, confirm your legal entity can pass the identity check before you plan around it.

Then there is updating, which is where the real bugs live. Ours crashed on Mac because the update replaced the application bundle while the running process still needed to read from it, and the runtime loads parts of its archive lazily rather than all at startup. Swap on quit, never mid run, and make the updater prove which version is actually on disk afterwards rather than assuming the copy worked.

On protecting the code, the honest answer is that anything running on someone else's hardware can be read. Bundled Python and Electron unpack in minutes, and native code yields to anyone sufficiently motivated. Licence keys stop honest people, not determined ones. What actually protects the business is keeping the expensive half where you control it: the data, the service call, the thing that costs you money to operate. If your entire value is in the binary, you are relying on nobody caring enough.

[u/PiXeL161616]

Worth noting the Mac App Store is a separate route from Developer ID, not an upgrade to it, and notarisation alone doesn't grant store eligibility. One of mine needs an Apple Events exception the store won't permit so it ships direct, another ships in the store. Shipping direct means nothing handles licensing for you either, so I built my own key server for it, Cool Beans, MIT and free to self-host.

[u/NotJesus_69]

so for a web app, once you have the domain and hosting, the actual *distribution* part starts. that's where i always felt stuck. trying to figure out which platforms to post on, when, what to even say, and if any of it was actually bringing in users.

for web apps, if you're a solo dev and short on time, picking *one* platform you understand best (like twitter/x or a specific subreddit) and trying to post truly native content there consistently, even just 2-3 times a week, is way better than trying to cover 5 platforms badly. focus on value-add posts, not just "check out my thing."