Explaining the examples

The installation includes 1 simple example to give you ideas of possibilities.

examples/modal.ts

An example showing how to do some native ui blending to open a purely native platform modal on both platforms. This is exactly what nscap init scaffolds:

import { iosRootViewController } from '@nativescript/capacitor/bridge';

native.openNativeModalView = () => {
  if (native.isAndroid) {
    const activity = (<any>global).androidCapacitorActivity;
    const builder = new android.app.AlertDialog.Builder(activity);
    builder.setTitle('Hello from NativeScript 🚀');
    builder.setMessage('A fully native Android dialog, built from TypeScript.');
    builder.setPositiveButton('Close', null);
    builder.show();
    console.log('NSCAP_MODAL presented');
    return;
  }
  const vc = UIViewController.alloc().init();
  vc.view.backgroundColor = UIColor.systemIndigoColor;
  const label = UILabel.alloc().initWithFrame(
    CGRectMake(0, 80, UIScreen.mainScreen.bounds.size.width, 50),
  );
  label.text = 'Hello from NativeScript 🚀';
  label.textColor = UIColor.whiteColor;
  label.textAlignment = NSTextAlignment.Center;
  label.font = UIFont.boldSystemFontOfSize(28);
  vc.view.addSubview(label);
  iosRootViewController().presentViewControllerAnimatedCompletion(vc, true, () => {
    console.log('modal presented');
  });
};

Everything is a direct platform API call — UIViewController, UILabel, CGRectMake on iOS exactly as in the Apple Developer Docs; android.app.AlertDialog.Builder on Android exactly as in the Android Developer Docs. No subclassing, no bindings — and the iOS completion callback demonstrates callbacks marshalling naturally across the bridge.

Usage in your web codebase:

import { native } from '@nativescript/capacitor';

native.openNativeModalView(); // Open native modal

Declare it in src/native-custom.d.ts for full type support — see What is native-custom.d.ts?