How does Big Sur convince older software that it’s macOS 10.16, but to newly-built app it’s macOS 11.0?
Both apps now detect and report apps which have been built using the 11.0 SDK, and ArchiChect reports non-Intel architectures too.
Will they be locked down completely, or run iPadOS? How could they run existing Mac apps? Some potential answers.
In a public recruitment advert, Apple has effectively announced that it’s developing new cloud-based services for third-party developers. […]
Even basic store facilities like restrooms contact details of who to contact when there’s a problem. Not so with Apple’s Notary Service. It just gives you spurious errors instead.
How long should it take for Apple’s Notary Service to notarize an app of yours? Analysis of over 100 runs over 8 months.
You don’t have to add an Info.plist to a standalone Mach-O tool in order to sign it, or to get it notarized successfully. And more tips.
Preparing software for distribution shouldn’t be harder than writing the code in the first place.
Over 10 months, I’ve run over 100 notarisations on more than 30 apps. How reliable and responsive has Apple’s service been?
Before we worry about new apps to manage and play media, replacing iTunes, shouldn’t we think about the loss of 32-bit software, including QuickTime, and requirements for hardening and notarization?