Angular Native renders Angular components as real iOS and Android views over React Native's Fabric renderer, with 350 stars in five days

An Angular team that wanted to ship a mobile app has had to leave Angular at the door for most of a decade. A new project called Angular Native, published to GitHub on 27 September 2026 and now at 350 stars, takes that choice away: it renders Angular components as real native iOS and Android views, through React Native's Fabric renderer, with React never in the render path.

The entry point is a template on Expo: npx create-expo-app@latest my-app --template @ng-native/template. The project README states that developers write "standalone components, signals, Signal Forms and @angular/router routes as you would for the web", then build, hot reload and ship with Expo. The elements are imported like any other Angular component (Pressable, SafeAreaView, Text). Stylesheets compile to native styles at build time.

What it ships

The feature list in the README names eight pieces. Native rendering happens through an incremental renderer that commits only what changed to Fabric, with native text, images, scroll views, virtual and section lists, text inputs, switches, modals and gestures. Component stylesheets, CSS variables, media queries, dark mode, transitions and @keyframes are supported, alongside a Tailwind preset with ios: and android: variants.

Navigation is @angular/router over native stacks, tabs, headers, modals and sheets, with guards, resolvers, lazy routes and deep links. Forms are Signal Forms bound to native controls. Expo's modules (camera, location, notifications, secure storage, file system, SQLite, biometrics, maps, haptics) are injectable as Angular services. The Testing Library runs components in Node against a fake Fabric so tests do not need a simulator. The same component tree can also render to the DOM through @ng-native/web.

Where it fits in a workspace

The repository ships twelve packages for different parts of the stack. @ng-native/platform carries the Angular renderer and an HttpClient for React Native. @ng-native/schematics gives an Angular CLI workspace ng add @ng-native/schematics and ng generate, and @ng-native/nx is the matching generator for Nx workspaces. @ng-native/fabric is the framework-agnostic retained tree and commit engine underneath the renderer.

The examples the project ships are complete apps: a bank wallet, a habit tracker, a music player, a run tracker with maps and a notes app. They are the shortest path to seeing the renderer, the router, the forms, the Tailwind preset and the Expo modules in one place.

Status and the constraints

Angular Native is at the alpha stage, with the maintainers saying APIs may change between 0.x releases. The README links a known limitations page that lists every gap with its workaround, which is the file to read before scoping a port. The platform requirements are Angular 22, Expo SDK 57 and React Native 0.86 with the New Architecture, on Node 22.18 or later, which rules out older React Native projects that have not migrated.

The project is independent and MIT licensed. The README states it is not affiliated with or endorsed by Google, the Angular team or Expo, and that Angular is a trademark of Google LLC. For an Angular team weighing a mobile build, the choice this project opens is a port of existing component code and router config, instead of a rewrite in a different framework.

Source

• Primary source: ng-native/ng-native on GitHub
• Related: ng-native.com getting started guide
• Related: Known limitations