Editing MacOS (section)

== Architecture ==
{{Main|Architecture of macOS}}
At macOS's core is a [[POSIX]]-compliant operating system built on top of the [[XNU]] [[kernel (operating system)|kernel]],<ref name="inside_mac_osx_kernel">{{Cite web |last=Lucy |year=2007 |title=Inside the Mac OS X Kernel |url=https://events.ccc.de/congress/2007/Fahrplan/attachments/986_inside_the_mac_osx_kernel.pdf |access-date=June 13, 2012 |publisher=24th Chaos Communication Congress 24C3 |archive-date=August 29, 2017 |archive-url=https://web.archive.org/web/20170829233357/https://events.ccc.de/congress/2007/Fahrplan/attachments/986_inside_the_mac_osx_kernel.pdf |url-status=live }}</ref> (which incorporated large parts of [[FreeBSD]] [[kernel (operating system)|kernel]]<ref name="apple_bsd_overview" />) and [[FreeBSD]] userland<ref name="apple_bsd_overview" /> for the standard Unix facilities available from the [[command line interface]]. Apple has released this family of software as a [[free software|free]] and [[open source software|open source]] operating system named [[Darwin (operating system)|Darwin]]. On top of Darwin, Apple layered a number of components, including the [[Aqua (user interface)|Aqua]] interface and the [[Finder (software)|Finder]], to complete the [[Graphical user interface|GUI]]-based operating system which is macOS.<ref name="aqua23">{{Cite web |last=Grothaus |first=Michael |date=April 12, 2011 |title=Mac OS X Lion to tone down the Aqua |url=https://www.tuaw.com/2011/04/12/mac-os-x-lion-to-tone-down-the-aqua |url-status=live |archive-url=https://web.archive.org/web/20110828084840/https://www.tuaw.com/2011/04/12/mac-os-x-lion-to-tone-down-the-aqua |archive-date=August 28, 2011 |access-date=April 9, 2012 |website=The Unofficial Apple Weblog |publisher=[[AOL]] |df=mdy-all}}</ref>

With its original introduction as Mac OS X, the system brought a number of new capabilities to provide a more stable and reliable platform than its predecessor, the [[classic Mac OS]]. For example, [[pre-emptive multitasking]] and [[memory protection]] improved the system's ability to run multiple applications simultaneously without them interrupting or corrupting each other. Many aspects of macOS's architecture are derived from [[OpenStep|OPENSTEP]], which was designed to be portable, to ease the transition from one platform to another. For example, [[NeXTSTEP]] was ported from the original [[68k]]-based NeXT workstations to [[x86]] and other architectures before NeXT was purchased by Apple,<ref name="nextstep_history" /> and OPENSTEP was later ported to the [[PowerPC]] architecture as part of the [[Rhapsody (operating system)|Rhapsody project]].

Prior to macOS High Sierra, and on drives other than [[solid state drives]] (SSDs), the default [[file system]] is [[HFS Plus|HFS+]], which it inherited from the classic Mac OS. Operating system designer [[Linus Torvalds]] had criticized HFS+, saying it is "probably the worst file system ever", whose design is "actively corrupting user data". He criticized the [[case insensitivity]] of file names, a design made worse when Apple extended the file system to support [[Unicode]].<ref>{{Cite web |first1=Swapnil |last1=Bhartiya |date=January 13, 2015 |title=Linus Torvalds: Apple's HFS+ is probably the worst file system ever |url=https://www.itworld.com/article/2868393/linus-torvalds-apples-hfs-is-probably-the-worst-file-system-ever.html |url-status=dead |archive-url=https://web.archive.org/web/20150525041019/https://www.itworld.com/article/2868393/linus-torvalds-apples-hfs-is-probably-the-worst-file-system-ever.html |archive-date=May 25, 2015 |website=ITworld |df=mdy-all}}</ref><ref>{{Cite web |author=Junio C Hamano (Gitster) |date=Dec 22, 2014 |title=CVE-2014-9390 aka "Git on case-insensitive filesystems" |url=https://plus.google.com/+JunioCHamano/posts/1Bpaj3e3Rru |url-status=live |archive-url=https://web.archive.org/web/20150514102424/https://plus.google.com/+JunioCHamano/posts/1Bpaj3e3Rru |archive-date=May 14, 2015 |website=Google+ |df=mdy-all}}</ref>

The [[Darwin (operating system)|Darwin]] subsystem in macOS manages the file system, which includes the Unix [[File system permissions|permissions]] layer. In 2003 and 2005, two [[Macworld]] editors expressed criticism of the permission scheme; Ted Landau called misconfigured permissions "the most common frustration" in macOS, while Rob Griffiths suggested that some users may even have to [[Repair permissions|reset permissions]] every day, a process which can take up to 15 minutes.<ref>{{Cite web |last=Griffiths |first=Rob |date=January 23, 2005 |title=Prevent Mac Disasters |url=https://www.macworld.com/article/174143/preventmacdisasters.html |access-date=December 31, 2023 |website=[[Macworld]] |publisher=[[International Data Group|IDG]] |df=mdy-all |archive-date=December 31, 2023 |archive-url=https://web.archive.org/web/20231231225401/https://www.macworld.com/article/174143/preventmacdisasters.html |url-status=live }}</ref> More recently, another Macworld editor, Dan Frakes, called the procedure of repairing permissions vastly overused.<ref>{{Cite web |last=Frakes |first=Dan |date=August 5, 2006 |title=Repairing permissions: what you need to know |url=https://www.macworld.com/article/52220/2006/08/repairpermissions.html |url-status=dead |archive-url=https://web.archive.org/web/20090219210621/https://www.macworld.com/article/52220/2006/08/repairpermissions.html |archive-date=February 19, 2009 |access-date=February 8, 2009 |website=[[Macworld]] |publisher=[[International Data Group|IDG]] |df=mdy-all}}</ref> He argues that macOS typically handles permissions properly without user interference, and resetting permissions should only be tried when problems emerge.<ref>{{Cite web |last=Frakes |first=Dan |date=June 2, 2008 |title=Five Mac maintenance myths |url=https://www.macworld.com/article/133684/2008/06/maintenance_intro.html |url-status=dead |archive-url=https://web.archive.org/web/20090123230040/https://www.macworld.com/article/133684/2008/06/maintenance_intro.html |archive-date=January 23, 2009 |access-date=February 8, 2009 |website=[[Macworld]] |publisher=[[International Data Group|IDG]] |df=mdy-all}}</ref>

The architecture of macOS incorporates a layered design:<ref>{{Cite web |title=About Developing for Mac |url=https://developer.apple.com/library/mac/#documentation/MacOSX/Conceptual/OSX_Technology_Overview/About/About.html |url-status=live |archive-url=https://web.archive.org/web/20120602013413/https://developer.apple.com/library/mac/#documentation/MacOSX/Conceptual/OSX_Technology_Overview/About/About.html |archive-date=June 2, 2012 |access-date=April 4, 2012 |publisher=[[Apple Inc.|Apple]] |df=mdy-all}}</ref>
the layered frameworks aid rapid development of applications by providing existing code for common tasks.<ref>{{Cite web |last=Zepko |first=Tom |date=November 6, 2003 |title=Why Cocoa? |url=https://homepage.mac.com/tom_zepko/cocoa/why-cocoa.html |url-status=dead |archive-url=https://web.archive.org/web/20090804073346/https://homepage.mac.com/tom_zepko/cocoa/why-cocoa.html |archive-date=August 4, 2009 |access-date=April 15, 2009 |df=mdy-all}}</ref> Apple provides its own [[software development]] tools, most prominently an [[integrated development environment]] called [[Xcode]]. Xcode provides interfaces to [[compiler]]s that support several [[programming language]]s including [[C (programming language)|C]], [[C++]], [[Objective-C]], and [[Swift (programming language)|Swift]]. For the [[Mac transition to Intel processors]], it was modified so that developers could build their applications as a [[universal binary]], which provides compatibility with both the Intel-based and PowerPC-based Macintosh lines.<ref>{{Cite web |date=February 22, 2007 |title=Adopting Universal Binaries on Mac OS X |url=https://developer.apple.com/macosx/adoptinguniversalbinaries.html |url-status=live |archive-url=https://web.archive.org/web/20081220184035/https://developer.apple.com/macosx/adoptinguniversalbinaries.html |archive-date=December 20, 2008 |access-date=December 15, 2008 |publisher=[[Apple Inc.|Apple]] |df=mdy-all}}</ref> First and third-party applications can be controlled programmatically using the [[AppleScript]] framework,<ref>{{Cite web |last=Productions |first=Nyhthawk |title=AppleScript: Graphic User Interface (GUI) Scripting |url=https://www.macosxautomation.com/applescript/uiscripting |url-status=live |archive-url=https://web.archive.org/web/20161121125017/https://www.macosxautomation.com/applescript/uiscripting |archive-date=November 21, 2016 |access-date=2017-01-03 |website=www.macosxautomation.com |df=mdy-all}}</ref> retained from the [[classic Mac OS]],<ref>{{Cite web |title=AppleScript Introduction |url=https://whitefiles.org/b1_s/1_free_guides/fg3mo/pgs/v01.htm |url-status=live |archive-url=https://web.archive.org/web/20160131030213/https://whitefiles.org/b1_s/1_free_guides/fg3mo/pgs/v01.htm |archive-date=January 31, 2016 |access-date=2017-01-03 |website=whitefiles.org |df=mdy-all}}</ref> or using the newer [[Automator (software)|Automator]] application that offers pre-written tasks that do not require programming knowledge.<ref>{{Cite web |title=The really simple guide to Automator in OS X on the Mac {{!}} RAW Mac |url=https://www.rawinfopages.com/mac/content/really-simple-guide-automator-os-x-mac |url-status=live |archive-url=https://web.archive.org/web/20170103170340/https://www.rawinfopages.com/mac/content/really-simple-guide-automator-os-x-mac |archive-date=January 3, 2017 |access-date=2017-01-03 |website=www.rawinfopages.com |df=mdy-all}}</ref>

=== Software compatibility ===
{{See also|List of Mac software}}

Apple offered two main [[Application programming interface|APIs]] to develop software natively for macOS: [[Cocoa (API)|Cocoa]] and [[Carbon (API)|Carbon]]. Cocoa was a descendant of APIs inherited from [[OpenStep|OPENSTEP]] with no ancestry from the [[classic Mac OS]], while Carbon was an adaptation of classic Mac OS APIs, allowing Mac software to be minimally rewritten to run natively on Mac OS X.<ref name="Rhapsody and Blues"/>

The Cocoa API was created as the result of a 1993 collaboration between [[NeXT]] Computer and [[Sun Microsystems]]. This heritage is highly visible for Cocoa developers, since the "NS" prefix is ubiquitous in the framework, standing variously for '''N'''eXT'''S'''TEP or '''N'''eXT/[[Sun Microsystems|'''S'''un]]. The official OPENSTEP API, published in September 1994, was the first to split the API between Foundation and ApplicationKit and the first to use the "NS" prefix.<ref name="nextstep_history">{{Cite web |title=Cocoa Fundamentals Guide: A Bit of History |url=https://developer.apple.com/legacy/library/documentation/Cocoa/Conceptual/CocoaFundamentals/WhatIsCocoa/WhatIsCocoa.html#//apple_ref/doc/uid/TP40002974-CH3-SW12 |access-date=January 18, 2018 |website=ADC Reference Library |publisher=[[Apple Developer Connection]] |archive-date=March 7, 2016 |archive-url=https://web.archive.org/web/20160307154056/https://developer.apple.com/legacy/library/documentation/Cocoa/Conceptual/CocoaFundamentals/WhatIsCocoa/WhatIsCocoa.html#//apple_ref/doc/uid/TP40002974-CH3-SW12 |url-status=live}}</ref> Traditionally, Cocoa programs have been mostly written in [[Objective-C]], with Java as an alternative. However, on July 11, 2005, Apple announced that "features added to Cocoa in Mac OS X versions later than 10.4 will not be added to the Cocoa-Java programming interface."<ref>{{Cite web |title=Introduction to Cocoa-Java Integration Guide |url=https://developer.apple.com/legacy/mac/library/#documentation/Cocoa/Conceptual/LanguageIntegration/LanguageIntegration.html |url-status=live |archive-url=https://web.archive.org/web/20090831202711/https://developer.apple.com/legacy/mac/library/#documentation/Cocoa/Conceptual/LanguageIntegration/LanguageIntegration.html |archive-date=August 31, 2009 |access-date=April 8, 2006 |website=ADC Reference Library |publisher=[[Apple Developer Connection]] |df=mdy-all}}</ref> macOS also used to support the [[Java Platform]] as a "preferred software package"—in practice this means that applications written in Java fit as neatly into the operating system as possible while still being [[cross-platform]] compatible, and that graphical user interfaces written in [[Swing (Java)|Swing]] look almost exactly like native Cocoa interfaces. Since 2014, Apple has promoted its new programming language [[Swift (programming language)|Swift]] as the preferred language for software development on Apple platforms.

Apple's original plan with macOS was to require all developers to rewrite their software into the Cocoa APIs. This caused much outcry among existing Mac developers, who threatened to abandon the platform rather than invest in a costly rewrite, and the idea was shelved.<ref name="Rhapsody and Blues"/><ref name="Photoshop, Lightroom, and Adobe's 64-bit roadmap"/> To permit a smooth transition from Mac OS 9 to Mac OS X, the [[Carbon (API)|Carbon]] [[Application Programming Interface]] (API) was created.<ref name="Rhapsody and Blues"/> Applications written with Carbon were initially able to run natively on both classic Mac OS and Mac OS X, although this ability was later dropped as Mac OS X developed. Carbon was not included in the first product sold as Mac OS X: the little-used original release of [[Mac OS X Server 1.0]], which also did not include the Aqua interface.<ref>{{Cite news |title=Looking back at OS X's origins |work=Macworld |url=https://www.macworld.com/article/1154036/osxorigins.html |access-date=September 25, 2020 |archive-date=January 3, 2012 |archive-url=https://web.archive.org/web/20120103080604/http://www.macworld.com/article/154036/2010/09/osxorigins.html |url-status=live}}</ref> Apple limited further development of Carbon from the release of Leopard onwards and announced that Carbon applications would not run at 64-bit.<ref name="Photoshop, Lightroom, and Adobe's 64-bit roadmap">{{Cite web |last=Nack |first=John |title=Photoshop, Lightroom, and Adobe's 64-bit roadmap |url=https://blogs.adobe.com/jnack/2008/04/photoshop_lightroom_and_adobes_64-bit_road.html |url-status=live |archive-url=https://web.archive.org/web/20150414030843/https://blogs.adobe.com/jnack/2008/04/photoshop_lightroom_and_adobes_64-bit_road.html |archive-date=April 14, 2015 |access-date=March 30, 2016 |publisher=[[Adobe Systems]] |df=mdy-all}}</ref><ref name="Rhapsody and Blues"/> A number of macOS applications continued to use Carbon for some time afterwards, especially ones with heritage dating back to the classic Mac OS and for which updates would be difficult, uneconomic or not necessary. This included [[Microsoft Office]] up to [[Microsoft Office 2016|Office 2016]], and Photoshop up to CS5.<ref name="Office 2016 preview 9to5 Mac">{{Cite web |last=Hall |first=Zac |date=March 5, 2015 |title=Back to the Mac: Microsoft releases redesigned Office for Mac 2016 Preview w/ Retina support, collaboration, more |url=https://9to5mac.com/2015/03/05/microsoft-office-mac-2016-preview |url-status=live |archive-url=https://web.archive.org/web/20171228000253/https://9to5mac.com/2015/03/05/microsoft-office-mac-2016-preview |archive-date=December 28, 2017 |access-date=27 December 2017 |website=9to5 Mac |df=mdy-all}}</ref><ref name="Photoshop, Lightroom, and Adobe's 64-bit roadmap"/> Early versions of macOS could also run some classic Mac OS applications through the [[Classic Environment]] with performance limitations; this feature was removed from 10.5 onwards and all Macs using Intel processors.

Because macOS is [[POSIX]] compliant, many software packages written for the other [[Unix-like]] systems including [[Linux]] can be recompiled to run on it, including many scientific and technical programs.<ref name="Mainzer">{{Cite web |last=Steele |first=Billy |title=NASA WISE Deputy Project Scientist Amy Mainzer |url=https://www.engadget.com/2013/05/24/engadget-questionnaire-nasa-amy-mainzer |url-status=live |archive-url=https://web.archive.org/web/20170625164201/https://www.engadget.com/2013/05/24/engadget-questionnaire-nasa-amy-mainzer |archive-date=June 25, 2017 |website=Engadget |date=May 24, 2013 |quote=As an astrophysicist, having the Unix core underlying the OS is key, since virtually all of our software is Unix-based in some sense |df=mdy-all}}</ref> Third-party projects such as [[Homebrew (package management software)|Homebrew]], [[Fink (software)|Fink]], [[MacPorts]] and [[pkgsrc]] provide pre-compiled or pre-formatted packages. Apple and others have provided versions of the [[X Window System]] graphical interface which can allow these applications to run with an approximation of the macOS look-and-feel.<ref>{{Cite web |date=October 28, 2003 |title=X11 for Mac OS X 1.0 |url=https://support.apple.com/downloads/X11_for_Mac_OS_X_1_0 |url-status=live |archive-url=https://web.archive.org/web/20081224160753/https://support.apple.com/downloads/X11_for_Mac_OS_X_1_0 |archive-date=December 24, 2008 |access-date=December 15, 2008 |publisher=[[Apple Inc.|Apple]] |df=mdy-all}}</ref><ref>{{Cite web |last=Ben Byer |date=October 27, 2007 |title=Re: X11 in Leopard: xterm on start-up |url=https://lists.apple.com/archives/x11-users/2007/Oct/msg00065.html |url-status=live |archive-url=https://web.archive.org/web/20080210000444/https://lists.apple.com/archives/X11-users/2007/Oct/msg00065.html |archive-date=February 10, 2008 |access-date=January 18, 2008 |website=Apple's x11-users mailing list |df=mdy-all}}</ref><ref>{{Cite web |last=Michael Larabel |date=May 28, 2011 |title=X.Org Server 1.10.2 Brings A Bunch Of Bug-Fixes |url=https://www.phoronix.com/scan.php?page=news_item&px=OTQ5OA |url-status=live |archive-url=https://web.archive.org/web/20110603150322/https://www.phoronix.com/scan.php?page=news_item&px=OTQ5OA |archive-date=June 3, 2011 |access-date=May 29, 2011 |publisher=phoronix |df=mdy-all}}</ref> The current Apple-endorsed method is the open-source [[XQuartz]] project; earlier versions could use the [[X11.app|X11]] application provided by Apple, or before that the [[XDarwin]] project.<ref>{{Cite web |last=Slivka |first=Eric |date=February 17, 2012 |title=Apple Removes X11 in OS X Mountain Lion, Shifts Support to Open Source XQuartz |url=https://www.macrumors.com/2012/02/17/apple-removes-x11-in-os-x-mountain-lion-shifts-support-to-open-source-xquartz |url-status=live |archive-url=https://web.archive.org/web/20120222214936/https://www.macrumors.com/2012/02/17/apple-removes-x11-in-os-x-mountain-lion-shifts-support-to-open-source-xquartz |archive-date=February 22, 2012 |access-date=February 23, 2012 |website=MacRumors |df=mdy-all}}</ref>

Applications can be distributed to Macs and installed by the user from any source and by any method such as downloading (with or without [[code signing]], available via an Apple developer account) or through the [[Mac App Store]], a marketplace of software maintained by Apple through a process requiring the company's approval. Apps installed through the Mac App Store run within a [[Sandbox (computer security)|sandbox]], restricting their ability to exchange information with other applications or modify the core operating system and its features. This has been cited as an advantage, by allowing users to install apps with confidence that they should not be able to damage their system, but also as a disadvantage due to blocking the Mac App Store's use for professional applications that require elevated privileges.<ref name="Not on the Mac App Store">{{Cite web |last=Counsell |first=Dan |date=November 16, 2015 |title=Not on the Mac App Store |url=https://dancounsell.typed.com/articles/not-on-the-mac-app-store |archive-url=https://web.archive.org/web/20151208082109/https://dancounsell.typed.com/articles/not-on-the-mac-app-store |archive-date=December 8, 2015}}</ref><ref name="Distributing Apps Outside the Mac App Store">{{Cite web |title=Distributing Apps Outside the Mac App Store |url=https://developer.apple.com/library/mac/documentation/IDEs/Conceptual/AppDistributionGuide/DistributingApplicationsOutside/DistributingApplicationsOutside.html |url-status=live |archive-url=https://web.archive.org/web/20151208143842/https://developer.apple.com/library/mac/documentation/IDEs/Conceptual/AppDistributionGuide/DistributingApplicationsOutside/DistributingApplicationsOutside.html |archive-date=December 8, 2015 |access-date=1 December 2015 |website=Apple Developer |publisher=Apple |df=mdy-all}}</ref> Applications without any code signature cannot be run by default except from a computer's administrator account.<ref name="How to open apps from an unidentified developer in OS X Mountain Lion">{{Cite web |last=Kazmucha |first=Allyson |date=October 4, 2019 |title=How to open apps from an unidentified developer in OS X Mountain Lion |url=https://www.imore.com/how-open-apps-anywhere-macos-catalina-and-mojave |access-date=September 25, 2020 |website=IMore |archive-date=December 31, 2021 |archive-url=https://web.archive.org/web/20211231130043/https://www.imore.com/how-open-apps-anywhere-macos-catalina-and-mojave |url-status=live}}</ref><ref name="About Gatekeeper">{{Cite web |title=About Gatekeeper |url=https://support.apple.com/en-us/HT202491 |url-status=live |archive-url=https://web.archive.org/web/20151204142544/https://support.apple.com/en-us/HT202491 |archive-date=December 4, 2015 |access-date=1 December 2015 |publisher=Apple |df=mdy-all}}</ref>

Apple produces macOS applications. Some are included with macOS and some sold separately. This includes [[iWork]], [[Final Cut Pro]], [[Logic Pro]], [[iLife]], and the database application [[FileMaker]]. Numerous other developers also offer [[List of Macintosh software|software for macOS]].

In 2018, Apple introduced an application layer, codenamed Marzipan, to [[Porting|port]] iOS apps to macOS.<ref name="Gurman Marzipan rumor">{{Cite news |last=Gurman |first=Masrk |date=December 20, 2017 |title=Apple Plans Combined iPhone, iPad & Mac Apps to Create One User Experience |work=Bloomberg.com |url=https://www.bloomberg.com/news/articles/2017-12-20/apple-is-said-to-have-plan-to-combine-iphone-ipad-and-mac-apps |access-date=2 February 2019 |archive-date=November 23, 2021 |archive-url=https://web.archive.org/web/20211123171922/https://www.bloomberg.com/news/articles/2017-12-20/apple-is-said-to-have-plan-to-combine-iphone-ipad-and-mac-apps |url-status=live}}</ref><ref name="Steinberger Marzipan">{{Cite web |last=Steinberger |first=Peter |title=Marzipan: Porting iOS Apps to the Mac |url=https://pspdfkit.com/blog/2018/porting-ios-apps-to-mac-marzipan-iosmac-uikit-appkit |access-date=2 February 2019 |publisher=PSPDFKit |archive-date=August 26, 2022 |archive-url=https://web.archive.org/web/20220826231543/https://pspdfkit.com/blog/2018/porting-ios-apps-to-mac-marzipan-iosmac-uikit-appkit/ |url-status=live}}</ref> macOS Mojave included ports of four first-party iOS apps including [[HomeKit|Home]] and [[Apple News|News]], and it was announced that the API would be available for third-party developers to use from 2019.<ref name="Verge future of the Mac comes from iOS">{{Cite web |last1=Gartenberg |first1=Chaim |last2=Bohn |first2=Dieter |date=June 7, 2018 |title=The future of the Mac comes from iOS apps |url=https://www.theverge.com/2018/6/7/17438450/apple-marzipan-mac-ios-apps-port-mojave-appkit-uikit-future-platform-software |access-date=29 January 2019 |website=The Verge |archive-date=November 11, 2021 |archive-url=https://web.archive.org/web/20211111003424/https://www.theverge.com/2018/6/7/17438450/apple-marzipan-mac-ios-apps-port-mojave-appkit-uikit-future-platform-software |url-status=live}}</ref><ref name="iMore Marzipan">{{Cite web |last=Ritchie |first=Rene |date=June 4, 2018 |title=Marzipan: What you need to know about iOS apps on the Mac |url=https://www.imore.com/marzipan |access-date=29 January 2019 |website=iMore |archive-date=August 18, 2021 |archive-url=https://web.archive.org/web/20210818144750/https://www.imore.com/marzipan |url-status=live}}</ref><ref name="Marzipan Benjamin Mayo">{{Cite web |last=Mayo |first=Benjamin |title=Marzipan |url=https://benjaminmayo.co.uk/marzipan |access-date=29 January 2019 |website=benjaminmayo.co.uk |date=September 25, 2018 |archive-date=April 14, 2019 |archive-url=https://web.archive.org/web/20190414093038/http://benjaminmayo.co.uk/marzipan |url-status=live}}</ref> With [[macOS Catalina]] in 2019, the application layer was made available to third-party developers as [[Mac Catalyst]].<ref>{{Cite web |title=Mac Catalyst |url=https://developer.apple.com/mac-catalyst/ |access-date=2022-10-06 |website=Apple Developer |language=en |archive-date=September 22, 2022 |archive-url=https://web.archive.org/web/20220922025050/https://developer.apple.com/mac-catalyst/ |url-status=live}}</ref>

=== Hardware compatibility ===
List of macOS versions, the supported systems on which they run, and their RAM requirements

{| class="wikitable sortable" style="text-align:center"

|-
! Operating system
! Release year(s)
! Supported systems<ref>{{webarchive |url=https://web.archive.org/web/*/apple.com/macos/how-to-upgrade/#hardware-requirements |title=macOS – Mac Hardware Requirements}}</ref>
! RAM requirement

|-
| [[Mac OS X 10.0|10.0]] – [[Mac OS X Jaguar|10.2]]
| 2001 – 2002
| G3, G4 and G5 [[iBook]] and [[PowerBook]], [[Power Macintosh|Power Mac]] and [[iMac]]<br /><small>(except [[PowerBook G3]] "Kanga")</small>
| data-sort-value=128 rowspan=2 | 128 MB

|-
| [[Mac OS X Panther|10.3]]
| 2003
| Macs with a [[New World ROM]]<ref name="TigerRequirements">{{Cite web |date=April 28, 2005 |title=Mac OS X: System Requirements |url=https://docs.info.apple.com/article.html?artnum=106163 |url-status=dead |archive-url=https://web.archive.org/web/20070809065541/https://docs.info.apple.com/article.html?artnum=106163 |archive-date=August 9, 2007 |access-date=December 20, 2006 |publisher=[[Apple Inc.|Apple]] |df=mdy-all}}</ref>

|-
| [[Mac OS X Tiger|10.4]]
| 2004
| Macs with built-in [[FireWire]] and either a [[New World ROM]] or Intel processor
| data-sort-value=256 | 256 MB

|-
| [[Mac OS X Leopard|10.5]]
| 2006
| Select G4, G5, and Intel Macs <small>(32-bit or 64-bit)</small> at 867&nbsp;MHz or faster<br />[[List of macOS components#Classic|Classic]] support dropped from 10.5 and later.
| data-sort-value=512 | 512 MB

|-
| [[Mac OS X Snow Leopard|10.6]]
| 2008
| Intel Macs <small>(32-bit or 64-bit)</small><ref name="LionReq" />
| data-sort-value=1024 | 1 GB

|-
| [[Mac OS X Lion|10.7]]
| 2010
| Intel Macs <small>(64-bit)</small><ref name="LionReq">{{Cite web |title=System requirements for OS X Lion and Mac OS X v10.6 |url=https://support.apple.com/en-au/HT202328 |url-status=live |archive-url=https://web.archive.org/web/20160923033514/https://support.apple.com/en-au/HT202328 |archive-date=September 23, 2016 |access-date=2016-09-22 |language=en-AU |df=mdy-all}}</ref><br />[[Rosetta (software)|Rosetta]] support dropped from 10.7 and later.
| data-sort-value=2048 rowspan=4 | 2 GB

|-
| [[OS X Mountain Lion|10.8]] – [[OS X El Capitan|10.11]]
| 2012 – 2015
| {{Plainlist |
* ''Laptops'': [[MacBook]] (Aluminum, Late 2008 or later), [[MacBook Air]] (Late 2008 or later), [[MacBook Pro]] (Mid 2007 or later)
* ''Desktops'':  [[Mac Mini]] (Early 2009 or later), [[iMac]] (Mid 2007 or later), [[Mac Pro]] (Early 2008 or later)
* ''Servers'': [[Xserve]] (Early 2009)
}}

|-
| [[macOS Sierra|10.12]] – [[macOS High Sierra|10.13]]
| 2016 – 2017
| {{Plainlist |
* ''Laptops'': [[MacBook]] (Late 2009 or later), [[MacBook Air]] (Late 2010 or later), [[MacBook Pro]] (Mid 2010 or later)
* ''Desktops'': [[Mac Mini]] (Mid 2010 or later), [[iMac]] (Late 2009 or later), [[iMac Pro]] (2017) (macOS 10.13), [[Mac Pro]] (Mid 2010 or later)
}}

|-
| [[macOS Mojave|10.14]]
| 2018
| {{Plainlist |
* ''Laptops'': [[MacBook]] (Early 2015 or later), [[MacBook Air]] (Mid 2012 or later), [[MacBook Pro]] (Mid 2012 or later)
* ''Desktops'': [[Mac Mini]] (Late 2012 or later), [[iMac]] (Late 2012 or later), [[iMac Pro]] (2017), [[Mac Pro]] (Mid 2010 or later<ref>{{Cite web|title=Install macOS 10.14 Mojave on Mac Pro (Mid 2010) and Mac Pro (Mid 2012)|url=https://support.apple.com/en-us/HT208898|access-date=March 3, 2021|website=Apple Support|archive-date=November 12, 2020|archive-url=https://web.archive.org/web/20201112022658/https://support.apple.com/en-us/HT208898|url-status=live}}</ref>)
}}

|-
| [[macOS Catalina|10.15]]
| 2019
| {{Plainlist |
* ''Laptops'': [[MacBook]] (Early 2015 or later), [[MacBook Air]] (Mid 2012 or later), [[MacBook Pro]] (Mid 2012 or later)
* ''Desktops'': [[Mac Mini]] (Late 2012 or later), [[iMac]] (Late 2012 or later), [[iMac Pro]] (2017), [[Mac Pro]] (Late 2013 or later)
}}
| rowspan="3" data-sort-value="4096" | 4 GB

|-
| [[macOS Big Sur|11]]
| 2020
| {{Plainlist |
* ''Laptops'': [[MacBook]] (Early 2015 or later), [[MacBook Air]] (Mid 2013 or later), [[MacBook Pro]] (Late 2013 or later)
* ''Desktops'': [[Mac Mini]] (Late 2014 or later), [[iMac]] (Mid 2014 or later), [[iMac Pro]] (2017), [[Mac Pro]] (Late 2013 or later)
}}

|-
| [[macOS Monterey|12]]
| 2021
| {{Plainlist |
* ''Laptops'': [[MacBook]] (Early 2016 or later), [[MacBook Air]] (Early 2015 or later), [[MacBook Pro]] (Early 2015 or later)
* ''Desktops'': [[Mac Mini]] (Late 2014 or later), [[iMac]] (Late 2015 or later), [[iMac Pro]] (2017), [[Mac Studio]] (2022), [[Mac Pro]] (Late 2013 or later)
}}

|-
| [[MacOS Ventura|13]]
| 2022
| {{Plainlist |
* ''Laptops'': [[MacBook]] (2017), [[MacBook Air]] (2018 or later), [[MacBook Pro]] (2017 or later)
* ''Desktops'': [[Mac Mini]] (2018 or later), [[iMac]] (2017 or later), [[iMac Pro]] (2017), [[Mac Studio]] (2022 or later), [[Mac Pro]] (2019 or later)
}}
| rowspan="3" data-sort-value="8192" | 8 GB

|-
|[[MacOS Sonoma|14]]
| 2023
|{{Plainlist|
* ''Laptops'': [[MacBook Air]] (2018 or later), [[MacBook Pro]] (2018 or later)
* ''Desktops'': [[Mac Mini]] (2018 or later), [[iMac]] (2019 or later), [[iMac Pro]] (2017), [[Mac Studio]] (2022 or later), [[Mac Pro]] (2019 or later)
}}

|-
|[[MacOS Sequoia|15]]
| 2024
|{{Plainlist|
* ''Laptops'': [[MacBook Air]] (2020 or later), [[MacBook Pro]] (2018 or later)
* ''Desktops'': [[Mac Mini]] (2018 or later), [[iMac]] (2019 or later), [[iMac Pro]] (2017), [[Mac Studio]] (2022 or later), [[Mac Pro]] (2019 or later)
}}
|}

Tools such as [[XPostFacto]] and patches applied to the installation media have been developed by third parties to enable installation of newer versions of macOS on systems not officially supported by Apple. This includes a number of pre-G3 Power Macintosh systems that can be made to run up to and including Mac OS X 10.2 Jaguar, all G3-based Macs which can run up to and including Tiger, and sub-867&nbsp;MHz G4 Macs can run Leopard by removing the restriction from the installation DVD or entering a command in the Mac's [[Open Firmware]] interface to tell the Leopard Installer that it has a clock rate of 867&nbsp;MHz or greater. Except for features requiring specific hardware such as graphics acceleration or DVD writing, the operating system offers the same functionality on all supported hardware.

As most Mac hardware components, or components similar to those, since the Intel transition are available for purchase,<ref>{{Cite web |title=iMac – Tech Specs – Apple |url=https://www.apple.com/imac/specs |url-status=live |archive-url=https://web.archive.org/web/20150728131342/https://www.apple.com/imac/specs |archive-date=July 28, 2015 |access-date=July 28, 2015 |publisher=Apple Inc. |df=mdy-all}}</ref> some technology-capable groups have developed software to install macOS on non-Apple computers. These are referred to as [[OSx86|Hackintoshes]], a [[portmanteau]] of the words "hack" and "Macintosh". This violates Apple's [[End-user license agreement|EULA]] (and is therefore unsupported by Apple technical support, warranties etc.), but communities that cater to personal users, who do not install for resale and profit, have generally been ignored by Apple.<ref>{{Cite web |title=Home page – footer |url=https://www.tonymacx86.com |url-status=live |archive-url=https://web.archive.org/web/20150728064306/https://www.tonymacx86.com |archive-date=July 28, 2015 |access-date=July 28, 2015 |website=tonymacx86.com |df=mdy-all}}</ref><ref>{{Cite web |last=K |first=M |title=Is installing Mavericks on Hackintosh legal? |url=https://apple.stackexchange.com/questions/107324/is-installing-mavericks-on-hackintosh-legal |url-status=live |archive-url=https://web.archive.org/web/20150823154640/https://apple.stackexchange.com/questions/107324/is-installing-mavericks-on-hackintosh-legal |archive-date=August 23, 2015 |access-date=July 28, 2015 |website=apple.stackexchange.com |df=mdy-all}}</ref><ref>{{Cite web |title=Choosing the right CPU for your hackintosh |url=https://www.macbreaker.com/2012/07/choosing-right-cpu-for-your-hackintosh.html |url-status=live |archive-url=https://web.archive.org/web/20150711181943/https://www.macbreaker.com/2012/07/choosing-right-cpu-for-your-hackintosh.html |archive-date=July 11, 2015 |access-date=July 28, 2015 |website=www.macbreaker.com |df=mdy-all}}</ref> These self-made computers allow more flexibility and customization of hardware, but at a cost of leaving the user more responsible for their own machine, such as on matter of data integrity or security.<ref>{{Cite web |last=Arment |first=Marco |title=Far Too Much Analysis Of The Alleged New Mac Pro Geekbench Score |url=https://www.marco.org/2013/06/20/new-mac-pro-geekbench |url-status=live |archive-url=https://web.archive.org/web/20150405214346/https://www.marco.org/2013/06/20/new-mac-pro-geekbench |archive-date=April 5, 2015 |access-date=14 August 2015 |website=Marco.org |df=mdy-all}}</ref> [[Psystar]], a business that attempted to profit from selling macOS on non-Apple certified hardware, was sued by Apple in 2008.<ref>{{Cite web |last=Taub |first=Eric |date=July 16, 2008 |title=Apple sues Psystar to block Macintosh clones |url=https://bits.blogs.nytimes.com/2008/07/16/apple-sues-psystar-to-block-macintosh-clone-sales/comment-page-2/?_r=0 |access-date=1 August 2015 |website=[[The New York Times]] |archive-date=October 20, 2021 |archive-url=https://web.archive.org/web/20211020004206/https://bits.blogs.nytimes.com/2008/07/16/apple-sues-psystar-to-block-macintosh-clone-sales/comment-page-2/?_r=0 |url-status=live }}</ref>

=== PowerPC–Intel transition ===
{{Main|Mac transition to Intel processors}}
[[File:Steve Jobs Presentation 1.jpg|thumb|Steve Jobs talks about the transition to Intel processors.]]
In April 2002, eWeek announced a rumor that Apple had a version of Mac OS X code-named [[Starvin' Marvin in Space|Marklar]], which ran on [[Intel x86]] processors. The idea behind Marklar was to keep Mac OS X running on an alternative platform should Apple become dissatisfied with the progress of the [[PowerPC]] platform.<ref>{{Cite web |last1=Rothenbourg |first1=Matthew |last2=dePlume, Nick |date=August 30, 2002 |title=Apple Keeps x86 Torch Lit with 'Marklar' |url=https://www.eweek.com/c/a/Apple/Apple-Keeps-x86-Torch-Lit-with-Marklar |access-date=June 8, 2013 |publisher=eWeek.com |archive-date=September 27, 2022 |archive-url=https://web.archive.org/web/20220927142110/https://www.eweek.com/apple/apple-keeps-x86-torch-lit-with-marklar/ |url-status=live }}</ref> These rumors subsided until late in May 2005, when various media outlets, such as ''[[The Wall Street Journal]]''<ref>{{Cite web |last1=Clark |first1=Don |last2=Wingfield |first2=Nick |date=May 23, 2005 |title=Apple Explores Use Of Chips From Intel For Macintosh Line |url=https://www.wsj.com/articles/SB111680203134440188 |url-status=live |archive-url=https://web.archive.org/web/20150115011437/https://www.wsj.com/articles/SB111680203134440188 |archive-date=January 15, 2015 |access-date=February 8, 2009 |website=[[The Wall Street Journal]] |publisher=[[Dow Jones & Company]] |df=mdy-all}}</ref> and [[CNET]],<ref>{{Cite web |last=Kanellos |first=Michael |date=May 24, 2005 |title=Apple to Intel: Some advantage, lots of risk |url=https://www.cnet.com/news/apple-to-intel-some-advantage-lots-of-risk |access-date=January 22, 2022 |website=[[CNET]] |publisher=[[CBS Interactive]] |archive-date=January 22, 2022 |archive-url=https://web.archive.org/web/20220122014428/https://www.cnet.com/news/apple-to-intel-some-advantage-lots-of-risk/ |url-status=live }}</ref> announced that Apple would unveil Marklar in the coming months.<ref name="I'll See You Intel">{{Cite web |last=Gruber |first=John |author-link=John Gruber |title=I'll See You Intel |url=https://daringfireball.net/2005/06/see_you_intel |url-status=live |archive-url=https://web.archive.org/web/20160313215847/https://daringfireball.net/2005/06/see_you_intel |archive-date=March 13, 2016 |access-date=31 March 2016 |website=Daring Fireball |df=mdy-all}}</ref><ref name="Intel-Apple Odds and Ends">{{Cite web |last=Gruber |first=John |title=Intel-Apple Odds and Ends |url=https://daringfireball.net/2005/06/intel_apple_odds_and_ends |url-status=live |archive-url=https://web.archive.org/web/20050608013302/https://daringfireball.net/2005/06/intel_apple_odds_and_ends |archive-date=June 8, 2005 |access-date=31 March 2016 |website=Daring Fireball |df=mdy-all}}</ref><ref name="Bombs Away">{{Cite web |last=Gruber |first=John |title=Bombs Away |url=https://daringfireball.net/2005/06/bombs_away |url-status=live |archive-url=https://web.archive.org/web/20160411170333/https://daringfireball.net/2005/06/bombs_away |archive-date=April 11, 2016 |access-date=31 March 2016 |website=Daring Fireball |df=mdy-all}}</ref>

On June 6, 2005, Steve Jobs announced in his keynote address at WWDC that Apple would be making the transition from PowerPC to [[Intel]] processors over the following two years, and that Mac OS X would support both platforms during the transition. Jobs also confirmed rumors that Apple had versions of Mac OS X running on Intel processors for most of its developmental life. Intel-based Macs would run a new recompiled version of OS X along with [[Rosetta (software)|Rosetta]], a [[binary translation]] layer which enables software compiled for PowerPC Mac OS X to run on Intel Mac OS X machines.<ref name="John Siracusa mourns the Power PC">{{Cite web |last=Siracusa |first=John |date=June 7, 2005 |title=Picking up the pieces: John Siracusa mourns the Power PC |url=https://arstechnica.com/apple/2005/06/mac-20050607 |url-status=live |archive-url=https://web.archive.org/web/20160329184041/https://arstechnica.com/apple/2005/06/mac-20050607 |archive-date=March 29, 2016 |access-date=31 March 2016 |website=[[Ars Technica]] |df=mdy-all}}</ref> The system was included with Mac OS X versions up to version 10.6.8.<ref name="AppleInsider: Mac OS X Lion drops Front Row, Java runtime, Rosetta">{{Cite web |last=AppleInsider Staff |date=February 26, 2011 |title=Mac OS X Lion drops Front Row, Java runtime, Rosetta |url=https://www.appleinsider.com/articles/11/02/26/mac_os_x_lion_drops_front_row_java_runtime_rosetta.html |url-status=live |archive-url=https://web.archive.org/web/20110301003419/https://www.appleinsider.com/articles/11/02/26/mac_os_x_lion_drops_front_row_java_runtime_rosetta.html |archive-date=March 1, 2011 |access-date=February 27, 2011 |website=[[AppleInsider]] |publisher=AppleInsider, Inc}}</ref> Apple dropped support for Classic mode on the new Intel Macs. Third party emulation software such as [[Mini vMac]], [[Basilisk II]] and [[SheepShaver]] provided support for some early versions of Mac OS. A new version of Xcode and the underlying command-line compilers supported building [[universal binary|universal binaries]] that would run on either architecture.<ref>{{Cite press release |title=Apple to Use Intel Microprocessors Beginning in 2006 |date=June 6, 2005 |publisher=[[Apple Inc.|Apple]] |url=https://www.apple.com/newsroom/2005/06/06Apple-to-Use-Intel-Microprocessors-Beginning-in-2006 |access-date=January 2, 2018 |url-status=live |archive-url=https://web.archive.org/web/20180130185804/https://www.apple.com/newsroom/2005/06/06Apple-to-Use-Intel-Microprocessors-Beginning-in-2006 |archive-date=January 30, 2018 |df=mdy-all}}</ref>

PowerPC-only software is supported with Apple's official [[binary translation]] software, [[Rosetta (software)|Rosetta]], though applications eventually had to be rewritten to run properly on the newer versions released for Intel processors. Apple initially encouraged developers to produce universal binaries with support for both PowerPC and Intel.<ref>{{Cite web |date=January 2006 |title=Adopting Universal Binaries |url=https://developer.apple.com/macosx/adoptinguniversalbinaries.html |url-status=live |archive-url=https://web.archive.org/web/20061017075217/https://developer.apple.com/macosx/adoptinguniversalbinaries.html |archive-date=October 17, 2006 |access-date=December 20, 2006 |publisher=[[Apple Inc.|Apple]] |df=mdy-all}}</ref> PowerPC binaries suffer a performance penalty when run on Intel Macs through Rosetta. Moreover, some PowerPC software, such as kernel extensions and System Preferences plugins, are not supported on Intel Macs at all. Plugins for Safari need to be compiled for the same platform as Safari, so when Safari is running on Intel, it requires plug-ins that have been compiled as Intel-only or universal binaries, so PowerPC-only plug-ins will not work.<ref>{{Cite web |last=Landau |first=Ted |date=May 2006 |title=OS X First Aid |url=https://www.macworld.com/article/50339/2006/04/firstaidintel.html |url-status=live |archive-url=https://web.archive.org/web/20090109080800/https://www.macworld.com/article/50339/2006/04/firstaidintel.html |archive-date=January 9, 2009 |access-date=February 8, 2009 |website=[[Macworld]] |publisher=[[International Data Group|IDG]] |df=mdy-all}}</ref> While Intel Macs can run PowerPC, Intel, and universal binaries, PowerPC Macs support only universal and PowerPC builds.

Support for the PowerPC platform was dropped following the transition. In 2009, Apple announced at WWDC that Mac OS X 10.6 Snow Leopard would drop support for PowerPC processors and be Intel-only.<ref>{{Cite web |last=Stevens |first=Tim |date=June 10, 2009 |title=Snow Leopard officially puts PowerPC Macs on endangered species list |url=https://www.engadget.com/2009/06/10/snow-leopard-officially-puts-powerpc-macs-on-endangered-species |url-status=live |archive-url=https://web.archive.org/web/20100323085015/https://www.engadget.com/2009/06/10/snow-leopard-officially-puts-powerpc-macs-on-endangered-species |archive-date=March 23, 2010 |access-date=June 15, 2009 |website=[[Engadget]] |publisher=[[AOL]] |df=mdy-all}}</ref> Rosetta continued to be offered as an optional download or installation choice in Snow Leopard before it was discontinued with Mac OS X 10.7 Lion.<ref name="MacRumors: Mac OS X Lion: Drops PowerPC Emulation, Adds QuickTime Pro Features, Much More">{{Cite web |last=Arnold Kim |date=February 27, 2011 |title=Mac OS X Lion: Drops PowerPC Emulation, Adds QuickTime Pro Features, Much More |url=https://www.macrumors.com/2011/02/27/mac-os-x-lion-drops-powerpc-emulation-adds-quicktime-pro-features-much-more |url-status=live |archive-url=https://web.archive.org/web/20110227205334/https://www.macrumors.com/2011/02/27/mac-os-x-lion-drops-powerpc-emulation-adds-quicktime-pro-features-much-more |archive-date=February 27, 2011 |access-date=February 27, 2011 |website=[[MacRumors]] |df=mdy-all}}</ref> In addition, new versions of Mac OS X first- and third-party software increasingly required Intel processors, including new versions of iLife, iWork, Aperture and Logic Pro.

=== Intel–Apple silicon transition ===
{{Main|Mac transition to Apple silicon}}
[[File:Apple M1.jpg|left|thumb|An illustration of Apple's M1 processor]]
Rumors of Apple shifting Macs from Intel to in-house ARM processors used by iOS devices began circulating as early as 2011,<ref name="SemiAccurate">{{Cite web |last=Demerjian |first=Charlie |date=May 5, 2011 |title=Apple dumps Intel from laptop lines |url=https://semiaccurate.com/2011/05/05/apple-dumps-intel-from-laptop-lines |access-date=June 25, 2020 |website=SemiAccurate |publisher=Stone Arch Networking Services, Inc. |archive-date=May 17, 2022 |archive-url=https://web.archive.org/web/20220517065123/https://semiaccurate.com/2011/05/05/apple-dumps-intel-from-laptop-lines/ |url-status=live }}</ref> and ebbed and flowed throughout the 2010s.<ref>{{Cite web |title=Apple Testing ARM Based Mac Prototypes with Large Magic Trackpad? |url=https://www.macrumors.com/2014/05/25/arm-mac-magic-trackpad |access-date=2020-06-22 |website=MacRumors |date=May 25, 2014 |language=en |archive-date=September 15, 2022 |archive-url=https://web.archive.org/web/20220915162849/https://www.macrumors.com/2014/05/25/arm-mac-magic-trackpad/ |url-status=live }}</ref> Rumors intensified in 2020, when numerous reports announced that the company would announce its shift to its custom processors at WWDC.<ref>{{Cite web |title=ARM Macs: Expected at WWDC 2020, What We Know |url=https://www.macrumors.com/guide/arm-macs |access-date=2020-06-22 |website=MacRumors |language=en |archive-date=June 25, 2020 |archive-url=https://web.archive.org/web/20200625004016/https://www.macrumors.com/guide/arm-macs/ |url-status=live }}</ref>

Apple officially announced its shift to [[Apple silicon|processors designed in-house]] on June 22, 2020, at WWDC 2020, with the transition planned to last for approximately two years.<ref>{{Cite press release |title=Apple announces Mac transition to Apple silicon |publisher=Apple Inc. |url=https://www.apple.com/newsroom/2020/06/apple-announces-mac-transition-to-apple-silicon |access-date=2020-06-22 |archive-date=June 22, 2020 |archive-url=https://web.archive.org/web/20200622185215/https://www.apple.com/newsroom/2020/06/apple-announces-mac-transition-to-apple-silicon |url-status=live }}</ref> The first release of macOS to support ARM was [[macOS Big Sur]]. Big Sur and later versions support [[Universal binary#Universal 2|Universal 2 binaries]], which are applications consisting of both Intel ([[x86-64]]) and Apple silicon ([[AArch64]]) binaries; when launched, only the appropriate binary is run. Additionally, Intel binaries can be run on Apple silicon-based Macs using the [[Rosetta 2]] [[binary translation]] software. The transition was completed at [[WWDC 2023]] with the announce of the Apple silicon [[Mac Pro]], ending the transition in 3 years, slightly behind schedule.

The change in processor architecture allows Macs with ARM processors to be able to run iOS and iPadOS apps natively.<ref name="Engadget1">{{Cite news |last=Lee |first=Nicole |date=June 22, 2020 |title=iOS apps will run natively on ARM-powered Macs |work=[[Engadget]] |url=https://www.engadget.com/ios-apps-arm-powered-macs-192046502.html |access-date=June 23, 2020 |archive-date=December 8, 2020 |archive-url=https://web.archive.org/web/20201208172634/https://www.engadget.com/ios-apps-arm-powered-macs-192046502.html |url-status=live }}</ref>