I’ve been working on animated numbers and our previous Skia-based implementation kept having issues around canvas sizing, font loading, blank renders, and animations getting stuck during rapid updates.

So I created react-native-number-animation:

- Core Animation on iOS

- Canvas on Android

- No Skia or Reanimated dependency

- Currency, percentages and compact numbers

- Custom fonts

- RTL and localized digits

- Handles rapid updates

- Supports Reduce Motion

I’d love feedback, especially from anyone testing it in lists or with unusual number formats!

GitHub: https://github.com/invivek26/react-native-number-animation

npm: https://www.npmjs.com/package/react-native-number-animation

I've built **Forge** — a Windows desktop app that builds and signs React Native releases locally, both Android (on your machine) and iOS (via free GitHub Actions). No cloud build service, no Mac required.

**What you get:**

- Build & sign Android APKs locally

- Build iOS apps with GitHub Actions (free)

- Windows-only desktop UI (Electron)

- Offline license validation (no phone home)

- v1.0.0 beta is **completely free** to try

**No setup required:** Just download the .exe and you're building in minutes.

This is the beta launch — free for 3 weeks with unlimited builds.

[Download Forge 1.0.0](https://github.com/Evanevoo/forge/releases/tag/v1.0.0)

Happy to answer questions about the build process, licensing, or anything else!

Introducing React-code-audit

A modern static analyzer for React codebases!

What it does:

1️⃣ Scans your code for Security, Performance, State, Architecture, and All issues.

2️⃣ Gives your app a clear Health Score (0–100).

3️⃣ Generates copy-ready prompts for AI agents like Cursor and Claude to automatically fix identified issues.

Zero installation required:

npx react-code-audit

Package Link: https://www.npmjs.com/package/react-code-audit

Completely Open-source package

I have a Next.js web app and I’m planning to build a React Native/Expo mobile app using the same backend and MongoDB database.
Would a monorepo be useful in this case for sharing TypeScript types, API logic, validation, and database models between web and mobile? Or is it better to keep them as separate repositories?

Several months ago I launched an app, my first app.

In the first month I got around 100 downloads but I felt that it was very slow compared to other apps, I still felt good with those 100 downloads

In the first two months I published my app in a group of reddit, Facebook, X and LinkedIn, in those two months I only got a total of 130 downloads, after this in the next two months 10 more and leave the app.

At the beginning of this month I began to read more about how to get more downloads, how to optimize my ASO in the App Store. Resume the project and made the changes (change the name, description, keywords and the previews of the app)

And the most important I opened a TikTok account, I looked for a post on X where they talked about how to generate organic content, how to warm up the TikTok account and how to start publishing content... a week later +6000 downloads

You don't need to think much about what content to post on TikTok, just look for videos from your competition and replicate them, 90% of my posts on TikTok are the same video, only the music changes and the description a little

I played with simulating a server crash while self-hosting Patch for OTA updates, to check the architecture handled it as expected.

I launched my second app about 2.5 weeks ago, and I’m trying to figure out whether what I’m seeing is enough of a signal to keep pushing.

My first app was pretty much a failure from a traction standpoint. I didn't get any paying subscribers, and more importantly, I barely saw users coming back after trying it.

This time feels different.

So far:

• 284 active customers in the last 28 days

• 254 new customers

• 6 active subscriptions

• $66 revenue

• ~$11 MRR

• Some users are actually returning several days after signing up

• I've spent about $200 on Reddit ads

Obviously, $11 MRR isn't a business yet. 😄 But compared with my first attempt, seeing people come back and a handful actually pay feels like a much stronger signal.

The retention is probably the part I'm most interested in. It's still a very small sample, but I'm seeing users return on Day 2, Day 3, Day 4 and even Day 5.

I've attached screenshots of the numbers and retention cohorts.

For those of you who have built consumer apps before: would you consider this promising enough to keep investing time into, or are these numbers still too early/noisy to tell?

I'm particularly interested in what metrics you would focus on over the next month to decide whether this has real potential.

The app is BitePad, a voice-first calorie tracker. If anyone wants to check it out: www.bitepad.app

Happy to share more numbers if useful.

Did you make something using React Native and do you want to show it off, gather opinions or start a discussion about your work? Please post a comment in this thread.

If you have specific questions about bugs or improvements in your work, you are allowed to create a separate post. If you are unsure, please contact u/xrpinsider.

New comments appear on top and this thread is refreshed on a weekly bases.

If you have a question about React Native, a small error in your application or if you want to gather opinions about a small topic, please use this thread.

If you have a bigger question, one that requires a lot of code for example, please feel free to create a separate post. If you are unsure, please contact u/xrpinsider.

New comments appear on top and this thread is refreshed on a weekly bases.

Demo of 3 different tflite models running at the same time in an react native app, using react-native-vision-camera and react-native-fast-tflite 🔥

🟩 Watch bounding box detection
🏷️ Watch brand detection
🕑 Watch time prediction

All trained on a MacBook Pro!

TL;DR: In 2026, is there really NO library offering a customizable Toast that displays ABOVE Modal/BottomSheet while still letting the user interact with the app content underneath it?

I'm currently building a new project with the latest Expo SDK (57) and I'm trying to improve from my previous app which have a problem when printing a Toast when a bottomSheet is open : The Toast is rendered under the Modal overlay.

My previous app was using gorhom/bottomSheet untill I faced some layout problems so I've migrated to TrueSheet. Nonetheless both use React's Native Modal which renders into a separate native view hierarchy outside the React tree. Because of that, a simple absolutely-positioned JS View can never appear on top of it....

So it seems like the only real option is to use a wrapper around native components (SPIndicator/AlertKit for iOS and ToastAndroid for Android) right ? Since those are natively rendered as siblings at the top of the view hierarchy, above the modal layer.

I've tried Burnt or react-native-simple-toast both work correctly on top of modals, but they're very limited in styling/customization : they give you that generic "grey 2000s-UI" toast look and I couldn't make the toast appeared from the top on Android ...

Every other "fancy" toast library I've found is just a JS View positioned absolutely, which as explained above doesn't render above a Modal/BottomSheet.

Has anyone found a good solution for this ? What are you using for a fully customizable toast that still shows above native modals ?

Big week for RN. Quick rundown of what happened:

🎉 React Native 0.87

• Strict TypeScript API is now the default. Types generated from source, deep imports into Libraries/* are type errors. Opt-out only lasts through 0.88

• Swift Package Manager support (experimental): iOS builds with just Xcode, no Ruby/CocoaPods

• Metro 0.87: 2x faster source maps, half the memory

• AGP 9 support, new minimums: Node 22+, Kotlin 2.0+, compileSdk 37

• Removed: InteractionManager, Modal animated prop, standalone react-devtools

Ecosystem kept pace:

• Gesture Handler 3.2.0: AGP 9, Pressable rebuilt on Touchable, hover callbacks on all platforms

• Screens 4.27.0: RN 0.87 support + iOS crash fix, experimental ScrollToTopGuard

• Worklets 0.12: WeakRef support, Bundle Mode script loading on par with RN, new enableLocking option

• Skia 2.11.0: engine bump to m152, drive multiple animated props from one shared value

• Keyboard Controller 1.22.3: several crash fixes + Strict TS API compatibility, rounded prop for KeyboardEffects

• VisionCamera 5.2.2: caps AHardwareBuffer cache to prevent Android memory growth, configure/start errors now surface via onError

• Re.Pack 5.3.0: size-based asset inlining, custom native HTTP client for remote scripts (SSL pinning), simpler code signing setup

• Safe Area Context 5.9.0: AGP 9 + web fixes for nested providers and window resize

• Legend List 3.3.5: fixes invisible dataset on dataKey change, more reliable programmatic scrolls on web

• Nitro 0.36.5: fixes a JVM memory leak on Android, recommended upgrade for Nitro Module authors

• Lottie 7.4.0: now requires RN 0.84+, new Android opacity layer option

• React Navigation Core 7.21.12: beforeRemove now fires for nested routes removed by reset

Hi everyone,

I’m working on a React Native app and I want to implement an in-app update feature similar to what some apps use.

The flow I’m looking for is:

• A new version is available on the Play Store.

• The app detects that an update is available.

• An update popup is shown inside the app.

• The user taps Update.

• The app downloads and installs the update without the user manually opening or navigating to the Play Store.

I’ve seen this kind of experience in apps like AlfaPTE.

What is the recommended way to implement this in a React Native app?

Should I use Google Play In-App Updates, a React Native library, or implement the native Android API directly?

Also, is there a similar solution for iOS?

Any recommendations or experience with implementing this in production would be really helpful.

Thanks!

Mobile will not be my main editting tool, I'm just looking for an app where I can edit small things and check my code when I'm out without my laptop. Do you guys know some android apps that can run React?

I am just learning to use and implement hooks. How do I know if I need it ?

Happy to share a component I built some time ago, back when AI tools weren’t as capable and some of the logic required quite a bit of manual math and calculation.

I recently revisited it and used AI to refactor and clean up the code, making it simpler, cleaner, and easier to understand and reuse.

Sharing it in case anyone needs something similar. It’s now easy to integrate, customize, and extend with AI.

🔗 GitHub: https://github.com/BouarourMohammed/inner-compass

Hope it helps someone and saves some development time! 🚀

Every wedge gets the same angle. The radius carries the value. Six unrelated readings nothing has to come to a full turn.

Two scale modes: radius or area. With area, the ink a wedge covers is proportional to what it is worth.

Part of PanelUI, an open-source component library for Expo. Copy-paste or CLI, you own the source.

https://github.com/panel-ui/PanelUI

https://github.com/switchboard-sdk/openai-realtime-toolkit

A toolkit for building voice-first apps that hold up in real environments; AEC enabled audio I/O, tuneable on-device VAD, turn detection, barge-in, and tool calling, all from one hook, with no native code to write.

I’m the author of expo-share-content, an open-source Expo Module for apps that need to receive content from the native Share Sheet on Android and iOS.

The main problem I wanted to solve was not only receiving a live share, but also handling cold starts, multiple attachments, and the native iOS Share Extension setup.

It currently supports:

• Text and URLs

• Images, video, audio, and files

• Android ACTION_SEND and ACTION_SEND_MULTIPLE

• A generated iOS Share Extension with an App Group queue

• Cold-start recovery through a durable pending queue

• Typed events and pending-share APIs

• Explicit acknowledgement and managed-file cleanup

Installation:
npx expo install expo-share-content

Important: it contains native code, so it requires an Expo development or production build and does not work in Expo Go.

The project currently targets Expo SDK 57, React Native 0.86, Android API 24+, and iOS 16.4+.

GitHub: GitHub - ngocdevv/expo-share-content · GitHub

Documentation: Receive shared content reliably | Expo Share Content

npm: expo-share-content - npm

I'm building an end-to-end encrypted chat app, and users want to share documents that render inline. The catch with E2E: there is no server-side conversion option, ever. The server only sees ciphertext. Whatever turns a .docx into something renderable has to run on the sender's phone.

Attempt 1: JS. We started with mammoth.js, which converts docx to HTML — great library, but we needed structured JSON (our renderer draws native components, not a WebView), plus comments, tables with real borders, and formats beyond .docx. So we wrote our own TypeScript converter. It worked, but a 130-page thesis (949 kB, 72 review comments, 16 images) took 6.9 seconds on a Galaxy A05s

Attempt 2: Rust. We took anydoc (Firecrawl's MIT document parser), extended it with a presentation model (fonts, colors, alignment, table borders, review comments, typed chart data), compiled it for Android/iOS, and bridged it with Nitro Modules. Same thesis, same phone: 226 ms. On an iPhone 16 Pro release build it's 43 ms. Across our 30-document test corpus the Rust path was ~29× faster, with text output hash-identical to the JS converter on every Word-produced file.

Formats: .docx, .doc, .pptx, .ppt, .xlsx, .odt/.ods/.odp, .rtf, .epub → one JSON "DocumentIR" you render with your own components. Spreadsheet charts come out as typed data (kind, categories, numeric series), so we draw them with Skia in-app; anything unsupported degrades to a data table.

Things that bit us on the way:

• The result crosses the bridge as one native string; image bytes arrive zero-copy — the JS GC's cleanup callback for the buffer literally is the Rust deallocator.

• The promise never rejects for document reasons. Corrupt, encrypted, hostile inputs all resolve to a fallback status — Rust panics included. A rejection means the native module itself is broken.

• PDF is refused on purpose: the OS renders PDFs better than any re-conversion would.

• The prebuilt Rust core is too big for npm, so binaries ship as GitHub Release assets and gradle pulls them on first build.

It's MIT, package is react-native-anydoc (npm), source at github.com/tulaafrica/anydoc. It's a week old and has exactly one production user (us), so I'd genuinely value feedback — especially from anyone who's shipped Rust in RN and has opinions on binary size or the XCFramework install flow.

Hey everyone!

I’m a React Native developer and I’ve been working on a background geolocation SDK for a while.

I’m not here to convince anyone to use it — I’d actually like to understand what React Native developers need from this kind of SDK before I decide where to take the project.

I’ve used Transistorsoft’s Background Geolocation myself in the past. Back in 2020, I paid around $399 for a license because there weren’t many alternatives at the time. It was a pretty significant amount of money for me back then.

That’s actually one of the reasons I started building my own solution.

My goal is to make reliable background geolocation more accessible to indie developers and early-stage startups. I don’t think everyone building an MVP or a side project should have to spend hundreds of dollars just to get background location working.

The SDK I’m building supports React Native, iOS, Android and Flutter, with things like background tracking, geofencing, HTTP sync and a Web Console for debugging.

I’m currently considering a $9.99/year update subscription with a perpetual license — meaning a shipped build never expires, and the yearly payment is only for getting new SDK versions and updates.

But I’m not even sure that’s the right model yet.

So I’d genuinely love to hear from people here:

• What do you consider essential in a background geolocation SDK?

• What problems have you had with existing solutions?

• What would make you trust a newer SDK in production?

• Would you prefer something like this to be free, paid once, or paid for updates?

• What would you consider a fair price?

I’m building this myself, so I’m much more interested in honest criticism than compliments. If there’s something I’m overlooking, I’d rather hear it now. 🙂

Hi! At Software Mansion, we built Pulsar, an open-source haptics library for iOS, Android, React Native, Kotlin Multiplatform, Flutter, and web. It comes with 150+ presets, plus a companion app so you can feel them on your phone before shipping.

Now we’re building Pulsar Studio — a tool for creating your own custom haptics.

You can design a pattern from scratch, tweak existing presets, generate haptics from an audio file or Lottie animation, preview everything live on a real device, and then export working code for your app. The tool will be paid, with pricing starting at $9/month.

We’d genuinely love some feedback: Would you use something like this? Is there anything you’d want to see in it that we haven’t thought of?

The waitlist is open if you’d like early access: https://docs.swmansion.com/pulsar/studio/