Hi!I&#x27;ve been frustrated with the fact that the beautiful NumberFlow library for web (link) is not available on React Native - a platform that I think is much more animation native than the web is. And there are no alternatives of the same quality available. So I reimplemented it myself, basically from the ground up.Introducing Number Flow React Native.I am aiming for this to be the best number animation library for React Native.- Beautiful animation easing directly inspired by web NumberFlow
- Supporting both Native and Skia versions
- Full i18n support for locales, things like compact or scientific notations, etc.
- TimeFlow component for timers and counters
- Custom digit bounding for things like binary
- Supporting 37 different numeral systems such as Arabic, Thai, and many others
- A dedicated, shared worklet mode for as much FPS as possible perfect for sliders or gestures for example
- Built on top of React Native Reanimated v3+
- Also supports web via Expo WebPlease check out the docs: <a href="https:&#x2F;&#x2F;number-flow-react-native.awingender.com&#x2F;docs" rel="nofollow">https:&#x2F;&#x2F;number-flow-react-native.awingender.com&#x2F;docs</a>
And star it on GitHub if you like it: <a href="https:&#x2F;&#x2F;github.com&#x2F;Rednegniw&#x2F;number-flow-react-native" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;Rednegniw&#x2F;number-flow-react-native</a>Let me know what you think!

Show HN: I created a beautiful number animation library for React Native

Composer 2 scores highest in React Native evals with 96%

Malicious NPM Packages Found in React Native – 130K+ Monthly Downloads Hit

Show HN: On-device element inspector for React Native

We built browser-metro, a Metro-like bundler that runs entirely in a Web Worker. It supports full HMR with React Refresh, Expo Router with file-based routing, and on-demand npm package resolution via an ESM server. API routes run in-browser through fetch interception — no server or service worker needed.
Unlike Expo Snack (server-side bundling) or CodeSandbox, everything here happens client-side. Currently web-preview only; native device preview is on the roadmap.Open source (MIT): <a href="https:&#x2F;&#x2F;github.com&#x2F;RapidNative&#x2F;reactnative-run" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;RapidNative&#x2F;reactnative-run</a>

Show HN: ReactNative.run – Browser Metro bundler that runs React Native

Understanding React Native's new architecture

Every AI app builder on the market right now generates cross-platform code. Bolt, Lovable, Rork, they all output React Native or Expo under the hood, or worse, web apps wrapped in a native shell. And I get why. React has more documentation, more training data for LLMs, and it&#x27;s easier to build a platform around, one codebase, two platforms, faster time to market.But the apps are bad.I tried building a polished app with one of these tools and the moment I needed a premium, native-feeling design, I hit a wall. Everything looked like AI slop. Animations were janky. Platform conventions were ignored. Try getting one of these approved on the App Store without weeks of cleanup. Apple doesn&#x27;t love Expo wrappers, and users can feel the difference whether they can articulate it or not.So when I started building Nativeline, I made what most people told me was the wrong bet: generate real SwiftUI for iPhone, iPad, and Mac. No React Native. No web views. Actual native Swift that opens in Xcode and builds.This was significantly harder. Here&#x27;s why.The biggest challenge is that LLMs are trained on the entire history of Swift, including five years of deprecated APIs, old UIKit patterns, and SwiftUI code from when it was half-baked. Getting the model to generate modern, clean SwiftUI without reaching for GeometryReader for every layout problem or calling APIs that haven&#x27;t existed since iOS 15 was a serious effort. It&#x27;s not just about generating code that runs. It&#x27;s about generating code that builds without errors, follows current conventions, and reads like something a good Swift developer would actually write.Then there&#x27;s keeping up with Apple. When Liquid Glass dropped, every existing LLM was useless for generating UI that used the new framework. If you&#x27;re generating React Native, you don&#x27;t really care, you&#x27;re abstracted away from platform changes. But if you&#x27;re generating native Swift, staying current with Apple&#x27;s frameworks isn&#x27;t optional. It&#x27;s the whole point.What we got right: The output is real SwiftUI that you own. Full Xcode project on your machine. One user described a Mac app idea, iterated on it over about 6 days, and is now selling it on the Mac App Store. He didn&#x27;t write Swift before that. The code was clean enough to ship and maintain.What we&#x27;re still working on: Complex backend integrations are hard. Database connections, Supabase, CloudKit, anything with real data persistence, still produce more errors than we&#x27;d like. We&#x27;re working on building deeper internal documentation for the AI specifically around database patterns, potentially our own managed backend, so the model has reliable patterns to follow instead of hallucinating schema configurations.I think the industry defaulted to React Native because it was the easier path for the builder of the tool, not because it was better for the user of the apps. The hard bet is generating native code. But the output difference is obvious the moment you use the app.Nativeline is free to try: https:&#x2F;&#x2F;nativeline.aiHappy to answer questions about the technical approach, the tradeoffs, or anything else.

Every AI app builder outputs React Native. I chose real Swift instead

React Native App Development Cost in the US (2026) + a One-Page Budget Checklist

C++ for JavaScript developers: the 5 concepts you need for React Native JSI

Show HN: The fastest OLAP engine for React Native

React Native 0.84

React-Auth: Google Sign-In for React Native and Expo and Web

VoltRN CLI for React Native/Expo Scaffolding, Generators

React Native Is Not Dead – Nor Is It Deprecated

Mindwtr – Open-source, local-first GTD app (Tauri and React Native)

Jetpack Compose now available for React Native apps

Show HN: React Native formatting in Node, powered by real Clang-format binaries

Introducing React Native View Recorder!The ultimate library to record any native View in your app and export it as a video or an image. No server required, MIT Licensed.- Record or snapshot any arbitrary View in React Native, whole app dashboard or only part of it
- Supports recording Skia Canvas
- You have frame-by-frame control over the video you&#x27;re recording
- Add your audio file or mix in the audio frame by frame
- Fully native, no FFmpeg binaries
- Control FPS, bitrate
- Support for H.264, HEVC, and transparencyStar it on GitHub: <a href="https:&#x2F;&#x2F;github.com&#x2F;Rednegniw&#x2F;react-native-view-recorder" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;Rednegniw&#x2F;react-native-view-recorder</a>Check out the docs: <a href="https:&#x2F;&#x2F;react-native-view-recorder.awingender.com&#x2F;" rel="nofollow">https:&#x2F;&#x2F;react-native-view-recorder.awingender.com&#x2F;</a>

Show HN: A library to turn any React Native View into a video or an image

I&#x27;m open-sourcing Send to X4, an iOS&#x2F;Android app that turns shared links into clean EPUBs entirely on-device, then transfers them to an Xteink X4 over local Wi-Fi — no accounts, no cloud.Repo (MIT): <a href="https:&#x2F;&#x2F;github.com&#x2F;Xatpy&#x2F;send-to-x4-mobile-app" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;Xatpy&#x2F;send-to-x4-mobile-app</a>
Product page + screenshots: <a href="https:&#x2F;&#x2F;chapiware.com&#x2F;send-to-x4" rel="nofollow">https:&#x2F;&#x2F;chapiware.com&#x2F;send-to-x4</a>WHY I BUILT IT
The X4 is a focused e-ink device, but getting long-form content onto it from a phone almost always involves a cloud step somewhere. I wanted a pipeline where the phone handles extraction and packaging entirely, and the device only ever receives finished files over LAN. Turns out doing this well on-device is more interesting than I expected.INTERESTING TECHNICAL BIT
- Reader mode extraction: Mozilla Readability + linkedom (a fast DOM implementation) to keep extraction lightweight inside RN.
- Client-side rendered pages: for sites where &quot;fetch HTML and parse&quot; fails, I use a headless WebView render → DOM capture → extract pipeline. This is the most fragile part of the stack and where I&#x27;d most value outside eyes.
- EPUB generation: downloads inline images locally, normalizes formats (transcoding problem types to JPEG for e-ink compatibility), then builds a compliant EPUB.
- Local transfer: pushes the resulting EPUB &#x2F; .xtc &#x2F; .bmp to the device via its local API (stock + CrossPoint firmware supported).STACK
React Native &#x2F; Expo (Hermes + new architecture).WHAT I&#x27;M LOOKING FOR
- Feedback on the on-device extraction architecture — JS thread vs native, the WebView approach, perf pitfalls
- Ideas for making extraction less whack-a-mole (site adapters, heuristics, test corpus)
- PRs for niche sites &#x2F; edge cases are very welcome

Show HN: On-device article extraction and ePub generation in a React Native app

Shadcn/UI and unistyles 3 (React Native) = shadniwind

# This is a Expo Framework

Expo is a framework and a platform for universal React Applications. 
It is a set of tools and services built around React Native and native platforms that help you develop, build, deploy,
and quickly iterate on iOS, Android, and web Apps from the same JavaScript/TypeScript codebase.

# Requirements

- Node.js LTS release or greater
- Git
- Watchman for macOS users

# Recommended Tools

- VSCode Editor
- Yarn
- Windows users: PowerShell or Bash via WS

# Installing Expo CLI

```bash
 # install the command line tools
 npm install --global expo-cli
```

## Getting Started 

Create a new app:
At this point we should have Expo CLI installed on our development machine and the Expo Go App on an iOS or Android physical device or emulator.
If not, go back to the Installation guide before proceeding.

# Initializing the project

```bash
# Create a project named my-app.
# Select the "blank" templata when promped
expo init my-app

# Navigate to the project directory
cd my-app
```

First, run the development server:

```bash
expo start
# or
npm start
```

... More content comming soon ...

ReactNative News

News From: hn.algolia.com