Apple Native vs NativeScript

How does Apple Native compare to NativeScript?
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
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.

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

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.