Hi, I'm PipThese Featured apps take turns in my notch.
iPipSubmit
Blog

Apple closed its Support Community. Here is where I would go for Mac help now

By Justinas Rolando, maker of MacPip

Short answer

Apple's Support Community, the user forum at discussions.apple.com that began in 1998, went read-only on November 10, 2026 and closed on November 20. Apple points people to its Support site, getsupport.apple.com and the Apple Support app, and gave no reason. It is not clear how long old threads stay readable. For community help, MacRumors Forums and r/applehelp are still open. Every Mac with Apple silicon runs macOS Golden Gate 27, and the newest any Intel Mac runs is macOS Tahoe 26. Mac app makers should put their own answers, minimum macOS, permissions and a support email on a help page on their own site.

Apple's Support Community, the forum at discussions.apple.com, went read-only on November 10 and closed for good on November 20, 2026. For Mac help now, Apple points you to its own Support site and app. Here's where else I'd go, and what I'd change as a Mac app maker.

It had been around since 1998, first as the Apple Tech Exchange, then Apple Discussions, then Apple Support Communities, MacRumors notes. Apple's notice was two lines. The forum "will permanently close on November 20, 2026", and you can still get help on the official Apple Support site. Apple didn't give a reason, and Macworld couldn't get one either.

When I checked on November 22, the forum's welcome page sent me straight to support.apple.com. Whether the old threads stay readable is less clear. Macworld wrote on November 11 that existing threads could still be viewed. MacRumors said on November 19 that it understood the forums would eventually be removed entirely, but not when. So I wouldn't count on finding an old answer there again.

Where do I ask a Mac question now?

This is the part that matters if you just use a Mac. For years, half the answers I found on Google were a thread there with a green "solved" tick. Here's where I'd go instead, in this order:

And for finding apps, not fixing them, I wrote down where I look for good Mac apps a while ago. It's still how I do it.

The question I'd answer first: can my Mac run it?

The most common thread type on that forum, as far as I remember, was "can my Mac run this?". Which macOS will it take, will this app open on it, is it Intel or Apple silicon.

So today's free tool answers exactly that. The macOS compatibility checker lets you pick your Mac and see the newest macOS it can run, every version from Big Sur 11 to macOS Golden Gate 27 with a yes or a no. The short version, from Apple's own list: every Mac with Apple silicon runs macOS 27, and no Intel Mac does. The newest any Intel Mac gets is macOS Tahoe 26, and only four Intel models get that far.

If you want apps that run natively on those newer Macs, there's a list of Mac apps built for Apple silicon on MacPip.

What it means for small Mac app makers

Here's the bit I keep thinking about. A lot of support for small Mac apps quietly lived in that forum. Someone posted "App X won't open on Sonoma", someone else answered, and the next person found it on Google. None of us wrote those answers, and now we can't count on them being there.

So the answers have to live on your own site. Three reasons I'd do it this month:

  1. People will search, and land on whatever answers them. If that's not your page, it's a Reddit thread you can't edit, with an answer from 2023.
  2. AI answers need something to quote. When someone asks ChatGPT or Google why your app won't open, the answer is built from pages it can read. A plain help page on your own domain is one of them. I can't promise it gets quoted, but a page that doesn't exist never does.
  3. Your support email gets shorter. Every question you answer once on a page is one you don't answer by hand ten times.

What I would put on a Mac app's help page

Nothing fancy. One page, plain text, one question per heading:

1. What it needs. The minimum macOS, and whether it runs on Intel, Apple silicon or both. If you're not sure what your build holds, run lipo -archs on it, or paste the output into the universal binary checker. The compatibility checker's second part shows which Intel Macs your minimum macOS leaves out.

2. The warnings people see. If you sell outside the Mac App Store, explain the "Apple could not verify" warning in your own words, and say your app is notarized if it is.

3. Permissions. If your app asks for Accessibility, Screen Recording or Full Disk Access, say why, and where the switch is in System Settings. macOS 27.3 changes Full Disk Access, which I wrote about in this post on macOS 27.3.

4. How to reach you. A real email, and what to put in it. I'd ask for three things, because they answer half my questions before I read the rest:

sw_vers -productVersion
sysctl -n hw.model
Your app's version, from its About window

5. A date. "Checked on" at the top. A help page that says which macOS it was written for is worth more than one that might be from 2019.

If you're on the Apple Developer Forums

Apple's notice was about the Support Community, the place for Mac and iPhone users. The Apple Developer Forums are a separate site, and none of the reports I read say they're affected. Still, if there's an answer there you rely on, I'd save a copy. This month showed that a forum can go read-only overnight and close ten days later.

The MacPip angle

Every MacPip listing has a Requires line for the minimum macOS. The automatic scan compares it with the app's own site and, if it's there, its Mac App Store record, and flags it when they don't match. So if someone asks whether your app runs on their Mac, your listing is one more page with the answer. A blue tick only means MacPip checked the app on a date. Listing your app is free.

Sources

Keep reading

Making apps for iPhone and iPad too? They have their own free home on iPip, MacPip's sister directory.

Submit your appFree tools for makers