RU

Angular Native: Rendering Angular Apps as Real Native iOS and Android Views

Published: 2026-09-29 · Author: AI Release · @ai_release1
Angular Native: Rendering Angular Apps as Real Native iOS and Android Views

⚡ The Gist in 5 Seconds - What it is: Angular Native (ng-native) renders Angular components as real native iOS and Android views using React Native's Fabric renderer, with React playing no part in the rendering. - Where to get it: the project is published on GitHub, installed via create-expo-app with the @ng-native/template template, and run through Expo Go or a simulator. - Limitation: the project is in alpha status, the API may change between 0.x releases, and there is a list of known limitations. ### 🔍 What Was Discovered The Angular Native project has been published on GitHub. It renders Angular components directly on the Fabric renderer — so that a <view> element becomes a UIView on iOS and android.view.View on Android. React is not involved in the rendering process. Developers use Angular approaches familiar from the web: standalone components, signals, Signal Forms, and routing via @angular/router. The app runs on Expo: the command npx create-expo-app@latest my-app --template @ng-native/template creates a project, then you start it with npx expo start and scan the QR code in Expo Go, or press i/a to launch the simulator. According to the README, the project provides a set of packages: @ng-native/platform — a renderer and HttpClient for React Native; @ng-native/components — elements (views, text, images, lists, inputs, etc.); @ng-native/router — native stack and tabs on top of @angular/router; @ng-native/expo — Expo modules as Angular services; @ng-native/tailwind — a Tailwind preset with ios: and android: variants; @ng-native/testing — a Testing Library that runs in Node against a fake Fabric. Requirements: Angular 22, Expo SDK 57, and React Native 0.86 with the New Architecture, plus Node 22.18 or newer. The project includes full example apps: a bank, a habit tracker, a music player, a running tracker with maps, notes, and an Analog file-based routing showcase. ### 💡 Why It Matters Angular teams can now build mobile interfaces with Angular, without using a WebView and without switching to React. All elements are compiled to native styles at build time, while CSS and Tailwind are supported with platform-specific variants. This opens the way to bringing existing Angular skills into mobile development with native rendering, and the integration of Expo modules as Angular services makes it easier to access the camera, geolocation, notifications, and other device capabilities. For those already invested in Angular who want native apps, this is a potential alternative to hybrid approaches. ### 🧩 Context Angular Native is an independent open-source project, not affiliated with Google, the Angular team, or Expo. It works with Expo SDK 57 and a React Native 0.86 base on the New Architecture, using the Fabric renderer — the layer responsible for drawing native views in React Native. The project is in alpha status, so the API may change. The authors have published a list of known limitations and workarounds. The license is MIT. Contributions are welcome; the list of contributors includes erKam, Chau Tran, Stavros Thalassinos, and others.

🔗 Read on github.com

🤖 AI summary
angularreact-nativefabricexponative-rendering
📖
Read the guide on this topic
Read →
← PreviousOpenAI announces ChatGPT office suite: Space, Pages, and slidesNext →AppTime publishes Android game calendar for May 2026

Source: github.com · post in Telegram