Skip to content
Pireon

← Blog

Angular Native: iOS and Android apps written in Angular

A just-published project lets you write mobile apps with Angular 22: components draw as real native views, with no WebView. It is in alpha and two days old.

On 27 September Angular Native appeared on GitHub, a project for writing iOS and Android apps with Angular. Two days later it cut its first two releases. It caught our eye because it targets exactly the version of Angular we work with.

What it is

It is not a WebView with a website inside. Angular Native uses Angular's Renderer2 to draw components as real native views — UIView on iOS and android.view.View on Android — on React Native's Fabric renderer, with Expo as the toolchain.

What you write is still Angular: templates, signals and services, as on the web.

What it brings

  • A real CSS engine, compiled at bundle time: selectors, the cascade, custom properties, @media, transitions and @keyframes.

  • Tailwind CSS v4, with ios:, android: and dark: variants.

  • Angular's Router on native stacks, tabs and headers, with deep links and the Android back button.

  • Signal Forms bound to native text fields and switches.

  • Device services as signals: screen, theme, keyboard, safe areas and accessibility settings.

  • Tests without a simulator, with Testing Library in Node against a fake native layer, and Maestro for end-to-end.

  • The same components on the web, inside an Angular app you already have.

What state it is in

Alpha, and worth taking literally. The first release, v0.1.0, went out on 29 September 2026, followed the same day by v0.1.1. The repository was created on 27 September and has around 120 stars. The licence is MIT.

It requires Angular 22 and Expo SDK 57. To try it:

npx create-expo-app@latest my-app --template @ng-native/template

Why it interests us

This part is our opinion, not the source's. We work with Angular 22 daily — this very site runs on it, and its contact form uses Signal Forms — so a route to mobile that does not force a change of language or mental model is appealing. That the components also render on the web opens the door to sharing pieces between an app and a back office.

That said: two days old and a v0.1.1 is no foundation for client work. We will look at it properly and, if it holds up, it goes on the radar. We will say how it went.

Sources