Hi r/pcgaming,

If you haven’t heard, macOS Catalina comes with a set of stringent requirements for gamedevs, one of which requires new app builds to be **notarized** by apple before release. This adds a new layer of complexity for devs, and some have already announced their intention to leave the OS entirely. Example and context here (not my blog):


On Steam, this change will occur on October 14th. The end result could be an exodus of indie devs (especially smaller ones) from Apple. A hilarious side note, the new interface system is called Gatekeeper.

Personally, I’m looking into the notarization process and it seems to be a headache that comes with a side of additional fees. I’m also not too sure I like the idea of every game being released on MacOS being forced to a notarization process, as that mandates devs to list themselves with Apple. Very 1984 of them.

View Reddit by AMemoryofEternityView Source

9 thoughts on “New requirements from Apple might cause devs to leave macOS”

  1. Gatekeeper was introduced in *2012*. The only recent change to it is that Apple forces you to go to the command line or jump through Finder hoops to run **unsigned** apps, which is a perfectly reasonable security feature. That change was implemented *last year*.

    The adjacent howling about 32-bit support being dropped is equally trollish, because Apple has been warning developers for the better part of a decade that it would eventually go away, and started announcing concrete plans for its retirement *two years ago*.

    tl;dr: [mad_max_thats_bait.gif]

  2. Why is this at all going to affect gaming on MacOS? Buying games form the app store only allows you to buy cheap ports of mobile games anyways for the most part. This only affects apps downloaded from the app store. All of the games we are looking to play come from game clients, or can be downloaded and installed outside of the app store already.

    Also if indie devs are okay with a 70 percent cut, why arent they using steam anyways? Loads more features than the app store, and its where people actually buy pc/mac games.

    Also of note – Game Launchers with MacOS suppport:
    Blizzard Battlenet,
    Epic Games Store

    None of these have ever been in the app store, or will be. None of these and all of their games are affected by this news from apple.

  3. Found this when Apple announced this a few mounths ago – [https://news.ycombinator.com/item?id=19609653](https://news.ycombinator.com/item?id=19609653)

    > There’s no interaction with Gatekeeper there. An executable you’ve built yourself will just run normally (assuming it has the x attribute of course).
    >OK, quick lesson in how Gatekeeper works:
    >When you download a Mac app from the web, or save it from an email, a bit of metadata called the “quarantine attribute” is attached to it. When you try to run an app with the QA, Gatekeeper checks whether it’s allowed to run; by default this will be allowed if it’s signed. If it doesn’t pass GK, you can still run it anyway by right-clicking on it and choosing “Open”. When the app runs, regardless of whether GK passed it or you overrode GK, the QA is removed. After that GK no longer cares about it, and the app will just run normally without further fuss.
    >Safari and Apple Mail automatically add the QA to anything they download, and most 3rd party browsers and email clients now do the same. But if you download an app using most command line tools (curl, wget, ftp, scp, etc), or if you build it yourself from source, then the QA never gets attached to it in the first place, so GK doesn’t care about it and the app just runs normally.
    >As far as I can tell the new notarization system doesn’t change any of this, it just adds another form of code signing.

    Has this changed in the new OS. In which the OS would just not allow any untrusted software to run?

  4. Oh man, do you think Macos will essentially become dead with this? Hopefully Apple can make the process somewhat convenient tho.

  5. 1st they’ve deprecated OpenGL and didn’t bother to update it beforehand so it’s stuck in 4.1 forever, then they’ve removed 32 bit support and now this.


    They just shot themselves in the foot 3 times in a row.

Leave a Reply

Your email address will not be published. Required fields are marked *