Capacitor vs NativeScript

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

Capacitor

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
NativeScript allows developers to build mobile apps for multiple platforms, including Android and iOS, using a single codebase.
Native APIs
NativeScript provides a bridge to all native APIs via JavaScript, without having to write anything in Swift or Kotlin. This means that developers can access native functionality such as camera, contacts, and file storage.

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.

Performance
NativeScript's performance is not as good as that of native apps due to the overhead introduced by the bridge between JavaScript and native APIs.
Emerging Community
Despite being around for a while, the NativeScript is not as popular as other frameworks, which means that there is not a lot of tutorials, and examples available to help developers apps.