Apple Native vs Capacitor

How does Apple Native compare to Capacitor?
See the pros and cons of each framework, target platforms and more.

Apple Native

Official SDK
Native apps are built using the official Apple development tools, which provide access to the latest features and functionality of the Apple ecosystem.
Performance
Native Apple apps perform better than hybrid apps as they have direct access to device hardware and the underlying operating system.
User Experience
Native Apple apps offer a consistent user experience that users are familiar with.
Ecosystem
Developers can build apps for other all Apple products like Apple Watch, Apple TV, Mac, iPad and iPhone.
Large Community
Apple has a very large and active developer community, which means there is plenty of documentation, tutorials, and examples available to help developers build apps for Apple.

Cross-platform
Capacitor allows developers to build mobile apps for multiple platforms, including Android and iOS, using a single codebase.
Native APIs
Capacitor provides a bridge between the web technologies and the native APIs of the operating systems. This means that developers can access native functionality such as camera, contacts, and file storage.
Web Technologies
Developers can use web technologies like HTML, CSS, and JavaScript to build mobile apps with Capacitor, which they may already be familiar with. This can make development faster and more comfortable.
Plugins
Capacitor has a plugin system that allows developers to extend the functionality of their apps. There are many plugins available to help developers build apps faster.

Cross-platform
Developers have to build separate apps using a different framework to target other platforms like Android and Windows.

Performance
Apps built with Capacitor may not perform as well as those built natively due to the overhead introduced by the webview.
Emerging Community
Capacitor is a relatively new framework, which means that there is not a lot of tutorials, and examples available to help developers apps.