Getting started
Compatibility and platforms
Choose the application environment and native modules your screen needs.
Which versions should I use?
Start from the official Angular Native template and follow Installation to add Neural Native. Neural Native and the framework have independent version numbers. The table identifies the documented application baseline; a newer upstream release needs its own compatibility check.
| Package or tool | Documented version | How to choose |
|---|---|---|
| Neural Native | 0.1.0-beta.1 · Beta | The current beta API may change before 1.0.0. |
| Angular Native | 0.18.2 | Keep components, fabric, device and icons on the same version. Use this version for testing too. |
| Angular | 22.2.2 | The Native package declares >=22.2.0 <23. This is the version used by these examples. |
| TypeScript | 6.0.3 | Match the compiler supported by your Angular version. |
| Node.js | 24.15.0 | This is the development runtime used for these examples. See Requirements for supported tooling. |
What does the native application run on?
The documented application uses Expo 57.0.27 and its React Native 0.86.3 runtime. Angular Native drives Fabric from Angular; you write Angular components, not React components. Keep the runtime chosen by the Expo template instead of independently changing its React Native version.
How Angular Native renders views ↗ · Official application setup ↗
iOS, Android and the documentation preview
| Environment | What to prepare | What to check on your screen |
|---|---|---|
| iOS | Use macOS and Xcode for local native builds, or an installed compatible app on your device. | Safe areas, the software keyboard, text scaling and VoiceOver. Adapt the layout to iPhone and iPad widths. |
| Android | Use an Android emulator or device and the SDK required by the application. | System back, the keyboard, text scaling and TalkBack. Include phone and tablet layouts. |
| Web preview | These documentation examples use @ng-native/web 0.18.2. | The device selector changes the frame. Check native gestures, keyboards and system surfaces in the installed application. |
Minimum operating-system versions belong to the selected Expo/native project configuration. Use its requirements when preparing a build. A phone frame in the documentation does not select an operating-system version.
Does a component need extra native modules?
| Capability | Application dependency | What to do |
|---|---|---|
| Safe areas | react-native-safe-area-context | Install it in your application and use SafeAreaProvider/SafeAreaView around screen content. Expo Go may already contain the native module. |
| SVG icons | react-native-svg 15.15.4 | It is a peer of Neural Native. Keep the documented version when reproducing this baseline. |
| Default file picker | expo-document-picker | The default Uploader picker uses this module. A custom NEU_FILE_PICKER can provide your own selection flow. |
npx expo install react-native-safe-area-context react-native-svg
# Add this when using the default Uploader picker
npx expo install expo-document-pickerExpo Go and a development build are different environments. If a native module is not included in Expo Go, create a development build containing it. Native dependency changes require rebuilding that application, not only restarting the JavaScript bundle.
Root theme and safe areas · Uploader and its picker contract
How do I update without mixing versions?
- Read the Neural Native changelog and choose a documented framework baseline.
- Update the @ng-native packages together. Keep Angular and its compiler compatible with each other.
- Check dependencies, run your tests, then check the installed iOS/Android application. Rebuild it if native modules changed.
npm ls @angular/core @angular/compiler @ng-native/components @ng-native/fabric @ng-native/device @ng-native/icons
npx expo install --checkIf npm reports an invalid peer or multiple framework versions, align the declarations and reinstall before continuing. Do not bypass the conflict with --force or --legacy-peer-deps.