Memory is making Macs dearer. Here is what I would do with my Mac app

On Monday Apple reported its September quarter, and the line I keep thinking about wasn't the revenue. It was memory. MacRumors' write-up of the call says Apple expects the Mac and iPad to be constrained in the December quarter, "primarily driven by memory", and that it thinks memory prices will keep rising beyond that. John Ternus, on his first call as CEO, called the memory situation "unprecedented".

I don't sell RAM and neither do you. But the Macs our apps run on just got more expensive, and the cheapest one has 8 GB. That changes a few things for anyone making a Mac app.

What actually happened

• Prices went up in June. On June 25, 2026, Apple raised Mac and iPad prices. The MacBook Air went from $1,099 to $1,299, the MacBook Pro from $1,699 to $1,999, the Mac Studio from $1,999 to $2,499, and the MacBook Neo from $599 to $699. Apple's statement at the time: "We have never seen a component price increase this much, this quickly."
• Macs are still selling. Mac revenue was $10.8 billion for the quarter, up from $8.7 billion a year earlier, despite the constraints, per MacRumors.
• The cheapest Mac has 8 GB, full stop. Apple's MacBook Neo specs list 8 GB of unified memory on both models, with no option for more. The MacBook Air starts at 16 GB.
• It isn't over. Apple expects higher memory costs this quarter and rising prices after it. Nobody outside Apple knows what that means for 2027 prices, so I won't guess.

Why a Mac app maker should care

Two things follow, and neither is a prediction, just arithmetic.

First, more of your new customers will be on 8 GB. The Neo is the Mac that costs the least, and memory on it can't be added later. If your app was quietly tuned on a 36 GB MacBook Pro, it has never met its newest users.

Second, people hold on to the Mac they have when the new one costs $200 more. That means more customers on older chips and older macOS versions than you'd see in a normal year. Your minimum macOS version and your update feed matter more than usual.

What I'd check this week

These are my own steps, not Apple's.

1. Measure your app on 8 GB, with other apps open. Nobody runs your app alone. Open Safari with a dozen tabs, a chat app and your app, then do the heavy thing your app does. Watch the Memory column in Activity Monitor and the Memory Pressure graph at the bottom. Yellow is a warning, red means macOS is struggling.
2. Get a real number. In Terminal, footprint YourApp prints how much memory your app is really using, and leaks YourApp looks for memory you forgot to free. In Xcode, the memory gauge in the Debug navigator and the Allocations and Leaks instruments show where it goes. Apple's guide to reducing your app's memory use walks through it.
3. Look hard at caches. The usual offenders in small Mac apps are image caches that never shrink, whole files read into memory when a stream would do, and history lists that keep everything forever. Cap them.
4. Be careful with local AI models. If your app downloads a model to run on the Mac, its size competes with everything else on an 8 GB machine. Offer a smaller model, or say plainly that the big one needs 16 GB.
5. Say what your app needs. Put the minimum memory and macOS version on your site and in your listing. A customer on a Neo would rather know before buying than after.
6. Don't push updates to Macs that can't run them. If you ship outside the Mac App Store with Sparkle, set sparkle:minimumSystemVersion on each release, and, from Sparkle 2.9, sparkle:hardwareRequirements with arm64 for an Apple silicon only build. Both are in the Sparkle publishing docs. Then someone on an older Mac keeps the last version that works instead of getting one that won't open.
7. Check what your app runs on. If you dropped Intel without meaning to, the universal binary checker reads your lipo output and tells you.

None of this needs a rewrite. Most apps I've looked at have one or two caches that grew without anyone noticing, and fixing them is an afternoon.

What I wouldn't do

I wouldn't put "optimized for 8 GB" in a launch post unless I'd measured it on one. And I wouldn't raise my own price just because Apple raised theirs. Your costs didn't change, and people on tighter budgets notice. If you're weighing a price change anyway, the pricing calculator compares a one-time price with a subscription after fees.

The MacPip angle

On MacPip, listings are scanned automatically when they're submitted, and a blue tick only means a person tried the app on a date. Neither one tests memory, so the honest answer about what your app needs has to come from you. Small, light apps do well here anyway: have a look at menu bar apps and productivity apps. If you're running a launch price for people watching their spending this season, Deals is where it goes, with an end date.

Also new today: the Sparkle appcast checker. Paste your appcast.xml and it checks each release for the version, the download size and signature, the minimum macOS version and the hardware rule, and tells you in plain words what is missing. It runs on the page and nothing is sent. And if your Mac app isn't on MacPip yet, listing it is free.

Sources

• MacRumors: Apple's Q4 2026 Earnings Call Takeaways
• TechCrunch: Apple raises Mac and iPad prices, spares iPhone for now
• Apple: MacBook Neo technical specifications
• Apple: MacBook Air technical specifications
• Apple Developer Documentation: Reducing your app's memory use
• Sparkle: Publishing an update

Keep reading

• Apple now lets you talk to people who cancel. Here is what I would do with my Mac appSince November 4, App Store subscriptions can show a message or offer when someone cancels. The rules, what Apple says it does, and what to check on the Mac.
• Apple is adding two age rating questions. Here is what I would do with my Mac appFrom November 16, App Store Connect asks about shared location and dating features, and every app must answer by January 12, 2027. What changed and what to do.
• Siri AI is open to every developer now. Here is what I would do with my Mac appApple opened Siri AI to all developers in the macOS 27.3 beta. What changed, what you can and cannot ship yet, and a short plan for a small Mac app.
• Touchscreen Macs ship on November 6. Here is what I would check in my Mac appApple's first touch Macs arrive November 6. What changed, what Apple tells developers to do, and a short list of things to test in your own Mac app.
• Introducing MacPipWhat MacPip is, why I built it, how listing and launch day work, what a blue tick really means, and the real numbers from its first days.
• How to launch a Mac app: a checklist that fits on one pageWhat to do before, on and after launch day for a Mac app: signing, your page, directories, Product Hunt, Show HN and what to measure.
• How to write a one-line description that says what your Mac app doesA plain way to write the one line under your Mac app's name: name the job, cut the hype, and test it on someone who has never seen the app.
• Signing and notarization, in plain words, for people making their first Mac appWhat code signing, notarization and stapling each do, in what order, what your users see without them, and how to check your own build.
• What a dofollow link is honestly worth, from a site that offers oneWhat dofollow means, what Google says about links, why a link from a new directory is worth little today, and what to do instead of buying links.

Submit your appFree tools for makers