NativeScript

When to Use

• You need 100% native performance and API access but want to share logic in JS/TS.
• You want to use Angular or Vue architecture for mobile.
• You need to access a new native API (e.g., latest iOS SDK) immediately without waiting for a plugin wrapper.

Quick Start

npm install -g nativescript
ns create my-app
# Choose flavor: Angular, Vue, React, Svelte, or TypeScript
cd my-app
ns run android

// Accessing Native APIs directly (Android)
const time = new android.text.format.Time();
time.setToNow();
console.log(time.format("%d.%m.%Y"));

Core Concepts

Runtime Marshalling

• new android.widget.Button(context)

  creates a real Android Button.

• UILabel.alloc().init()

  creates a real iOS Label.

Layouts

• StackLayout

  ,

  GridLayout

  ,

  FlexboxLayout

  .

Plugins

Best Practices

• Use TypeScript strictly. Direct native access without types is error-prone.
• Offload heavy CPU tasks to Worker Threads (JS runs on the main UI thread).
• Use

  Webpack

  optimizations provided by the CLI.

• Don't block the main thread.
• Don't assume CSS works exactly like the web (it's a subset/mapping).

Troubleshooting

Marshalling Error

Out of Memory

image-cache-it

Build Failed

ns clean

platforms/

node_modules/

References

• NativeScript Docs
• NativeScript Plugins