4 PrevalentThemes in the Discussion
| Theme | What the community is saying | Representative quote |
|---|---|---|
| 1. Gatekeeper friction is too clunky – Users want a one‑click or GUI way to run unsigned binaries without digging into Terminal or System Settings each time. | “Any user who does not like Gatekeeper can turn it off … in ten seconds …” – many still find the extra manual step (open‑settings, click‑through) annoying. | “> without disabling security features?” – Wowfunhappy |
| 2. Apple’s $99/year developer fee and notarization process lock out hobbyists – The cost and bureaucracy are seen as barriers that discourage free/open‑source distribution. | “I’ve written off Apple as a target system for hobby/open source projects … quarantine, code signing, and notarizing (which requires $99 a year) … not worth it.” – ryandrake | “It has a chilling effect on releasing free apps.” – copperx |
| 3. Apple’s security model is a trade‑off between protecting non‑technical users and restricting power users – The platform is marketed to “normies,” yet power users feel forced into a binary choice (full lock‑in vs. full disable). | “Apple … would rather keep users inside the App Store where they can collect that sweet 30% and analytics.” – Zetaphor | “Either you keep Gatekeeper because you like the friction it introduces, or you don’t like that friction and you should turn it off.” – Wowfunhappy |
4. Notarization and code‑signing are obscure, multi‑step, and often undocumented – Developers struggle with bundling layouts, stapling receipts, and using the new notarytool. |
“You have to distribute a ‘bundle’ in a particular directory layout.” – pjc50 “My guide walks you through the exact steps; Apple’s docs are surprisingly poor.” – ofek (linked in the thread) |
“There’s no way to keep secure boot but bless your own changes … you have to turn it all off.” – wolvoleo |
Bottom line: The discussion centers on how Apple’s security mechanisms—Gatekeeper, notarization, and the $99 developer program—create friction for developers and users who simply want to run unsigned software on macOS. Many commenters call for simpler, more transparent pathways, while others defend the protections as necessary for the broader, less‑technical user base.