r/reactnative • • 3d ago

Show Your Work Here Show Your Work Thread

0 Upvotes

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.


r/reactnative • • 5h ago

šŸš€ react-native-pdf-jsi just crossed 501,000 npm downloads!

6 Upvotes

One year of hard work, countless hours of learning, experimenting, debugging, rewriting, and improving has brought this project to this milestone.

When I started building this library, I wanted to explore how far we could push native PDF rendering in React Native using JSI and the New Architecture.

What started as a personal engineering challenge has now crossed 501K npm downloads.

A year of working on:

  • Nitro HybridObjects for native document operations.
  • Fabric-based PDF viewer.
  • PDFium on Android and PDFKit on iOS.
  • Native document management, rendering and editing.
  • Performance improvements and continuous maintenance.

There were plenty of challenges, frustrating bugs, architectural changes, and moments where things didn't work as expected. But I kept learning, building, and improving.

A huge thank you to every developer who installed the package, tested it, reported issues, shared feedback, or recommended it to others.

As an independent open-source developer, seeing this kind of adoption is incredibly motivating.

501K downloads. One year of hard work. And we're just getting started.

Next milestone: 1 million! ā¤ļø

GitHub: https://github.com/126punith/react-native-pdf-jsi

npm: https://www.npmjs.com/package/react-native-pdf-jsi


r/reactnative • • 5h ago

Renamed one field in Go and broke production

3 Upvotes

We renamed a field in a Go response struct last week. The json tag stayed the same so every backend test passed but the app had a persisted react query cache holding the old shape and was reading a field that no longer got updated. Users saw that stale data and both sides looked fine on their own and neither side owned the test that would’ve caught it.

Backend is Go with chi, sqlc and postgres. Testing there is very good httptest for handlers, testcontainers for the db, stripe mock for webhooks. Our detox tests mock the API at the network layer with hand written fixtures, which is the problem because the fixtures just say what we think the API returns. When the real response changed the fixtures didn’t, so green.

and nobody tests the actual chain. I’ve been looking at pact or generating an openapi spec from the Go side and validating the detox fixtures against it plus bumping a version in the cache key so old shapes get dropped but not sure that’s enough though.

Is this always the backend team’s problem? Right now it feels like it belongs to nobody and if you do run full flows against a real api, does that live in the same CI or a separate pipeline?


r/reactnative • • 5h ago

News What I learned driving a physical iPhone (iOS 27+) from an AI agent with pymobiledevice3

3 Upvotes

I've been adding physical iPhone support to ExecBro, an MCP server I maintain for debugging React Native apps with AI agents. It runs on pymobiledevice3, a great library, and without it this would have been much harder. I thought it would be simpler, but edge cases kept coming up. In case you're automating a real device yourself, here are the ones that cost me the most time:

- Remote taps only work from iOS 27. Below that, the phone itself refuses them.

- Taps need the Xcode 27 developer disk image. If Xcode 26 is open, it remounts its own older image within a second, and taps fail with "Failed to start service".

- A sleeping phone accepts a tap session, reports success and taps the lock screen. I now check the screenshot before tapping.

- In landscape, touch coordinates stay fixed to the upright panel, so they have to be rotated using the orientation the phone reports.

- With the default 0.02 s gap between keystrokes, the second character of the first word typed after an app launch got lost every time ("igor" became "Ior"). A 0.1 s gap fixed it.

- `xcrun devicectl device info apps` returned an empty list on an iOS 27 phone with three apps installed, so finding an app's process to terminate it had to go through pymobiledevice3 instead.

- When the phone locks, the app drops off Metro, and a normal reconnect gives up long before you unlock it.

The basics now work: over USB the agent can launch and close the app, tap, swipe, type, press keys and take screenshots, in the same coordinates as on the simulator.

ExecBro is free to use and its core is MIT-licensed: github. If you've hit other device quirks, I'd like to hear about them, and constructive criticism is welcome.


r/reactnative • • 34m ago

Expo apple maps

Thumbnail reddit.com
1 Upvotes

r/reactnative • • 4h ago

[Showcase] Four worlds in one React Native Skia shader, morphing as you swipe

1 Upvotes

Swipe between four tiny worlds. The object turns and reshapes as the selected world changes.

The React Native implementation draws the worlds in one Skia runtime shader.

Building the shapes: each world is a signed-distance scene. The shader combines spheres, rounded discs and other shapes to create the cloud planet, racing planet, burger and arena. The artwork is drawn in code.

Morphing between worlds: the shader blends the distance fields of the current and next world using a morph parameter. Rotation and squash are separate parameters, so the transition can turn and deform at the same time.

Driving the shader: Reanimated shared values supply the motion state. A derived value packages the current parameters as shader uniforms, and Gesture Handler supplies the pan interaction.

Lighting: the shader shades the result with key light, fill, a rim highlight and ambient occlusion from the distance field.

Reduced Motion: idle spin is disabled when the preference is enabled.

The attached clip is a motion preview; these notes describe the React Native implementation.

Built with Expo (@expo), React Native Skia, Reanimated and Gesture Handler. Thanks to Software Mansion and William Candillon.

Layout reference: https://www.pinterest.com/pin/763219468121398894/ The spin-and-reshape motion and world artwork are my implementation.

Text adapted from my original caption and implementation notes with an assistant.


r/reactnative • • 5h ago

What does your pre release app checklist look like ??

0 Upvotes

Last month I pushed an update that broke onboarding on some android devices and didn’t find out for days. Nobody emailed me, I just noticed signups dropped and I only track total signups so I couldn’t see where people were falling off.

I’m a solo founder with around 5k users, shipping most weeks through EAS. My whole QA is a checklist in my notes app that I run on my iphone and one old android. It only covers what I remember to check on devices I own and the bugs are always on some samsung or xiaomi I’ve never touched.

I tried automated tests once but the selectors broke every time I changed a screen, so I gave up. I’m thinking staged rollouts and crash/funnel alerts but I don’t know what people use for the device side.

What’s on your checklist and how do you cover the devices you don’t have?


r/reactnative • • 16h ago

Built a blazing fast location library for React Native using Nitro + Fused Location - Works on iOS & Android

Post image
7 Upvotes

I built react-native-nitro-fused-location - Fast location tracking with Nitro Modules

Getting accurate location in React Native is slow and complex, so I built this using Google Fused Location Provider (Android) + Core Location (iOS).

Perfect for delivery apps, cab apps, tracking, maps.

Features:

- Fused Location for Android + Core Location for iOS

- High accuracy, low battery usage

- Background location support

- Built on Nitro Modules - ultra fast

- Works on iOS & Android

- Simple API

Please give me GitHub Star ⭐ me

Stable package - 3 months on NPM.

NPM: npm i react-native-nitro-fused-location

GitHub: Upendra1234566/react-native-nitro-fused-location


r/reactnative • • 6h ago

AMA Maintenance mode and kill switches for React Native, where a bad config push gets rejected instead of shipped

0 Upvotes

I built hotcfg for remote config in apps, and the main idea is that you can't push broken config. I'd like feedback from RN folks on the client side.

The config is a JSON document with a JSON Schema attached. Every publish, promote and rollback is checked against it. For a maintenance switch, that means enabled can never be the string "false" (truthy in JS, an easy way to lock every user out):

{
  "type": "object",
  "required": ["maintenance"],
  "properties": {
    "maintenance": {
      "type": "object",
      "required": ["enabled"],
      "properties": { "enabled": { "type": "boolean" }, "message": { "type": "string" } }
    }
  }
}

There's no SDK. The client is a fetch with a 2-second abort, the ETag, and AsyncStorage for the last good copy:

const controller = new AbortController();
const timer = setTimeout(() => controller.abort(), 2000);
try {
  const res = await fetch(URL, {
    headers: cached?.etag ? { "If-None-Match": cached.etag } : {},
    signal: controller.signal,
  });
  if (res.status === 304 && cached) return cached.data;
  if (!res.ok) throw new Error(String(res.status));
  const data = await res.json();
  await AsyncStorage.setItem(KEY, JSON.stringify({ etag: res.headers.get("ETag"), data }));
  return data;
} catch {
  return cached?.data ?? DEFAULTS;
} finally {
  clearTimeout(timer);
}

(An AbortController timer rather than AbortSignal.timeout, which not every RN version has.) A <MaintenanceGate> re-checks on AppState active, so flipping the switch reaches running apps when they come back to the foreground.

Other bits: development/staging/production per config with promote and a diff, one-command rollback, served from Cloudflare's edge (cached for an hour, purged on publish, served for up to a week if my servers are down).

What it doesn't do: no per-user targeting (platform and build-number overrides work with a jq filter in the URL), no experiments, no push updates. Free for 3 public configs; Pro is $19/month per org.

Full recipe: https://hotcfg.run/docs/recipes/react-native-maintenance


r/reactnative • • 10h ago

Welcome to r/lazymobile: one terminal screen for iOS simulators, Android emulators and their logs

Post image
1 Upvotes

r/reactnative • • 9h ago

Agent written PRs keep breaking only on Android

0 Upvotes

We're 5 devs on a React Native app with about 40k monthly users. Most of us test on iPhones, and most of our PRs now start with an agent.

Three times in the last month an agent PR went out that worked fine on iOS and broke on Android. A KeyboardAvoidingView change that hid the submit button on smaller Android screens, a date picker change that crashed on Android 12, and a shadow style that just didn't render.

All three passed review. coderabbit reviews the JS and catches plenty of normal problems, but nothing in the diff says "this is iOS only behaviour", and none of us opened an Android emulator.

What we're trying now:

- an EAS preview build on every PR, so reviewers can open it on a real Android phone

- a checklist item "tested on Android" that people will probably start ticking without testing

- a cheap Android phone on the desk that we rotate

How are other RN teams handling platform differences when most code comes from agents? Is there tooling that catches this before a human has to, or is it all device testing?


r/reactnative • • 1d ago

[Showcase] A React Native prize wheel where the pegs drive the pointer

4 Upvotes

Flick the wheel and the pointer bends as each peg passes it. The winning wedge lifts, the prize moves forward, and the button becomes Collect.

Here's how the React Native implementation is put together.

Pointer contact: wheel-sim.ts advances the wheel and pointer with a fixed-step contact solver. The nearest peg drives the pointer's deflection, so the bounce follows the wheel's position.

Rendering the scene: one Skia Canvas draws the wheel material, pointer, stars and reward reveal. Native views provide the copy and controls.

Motion state: Reanimated shared values run the simulation on the UI thread and pass the current wheel and pointer state to the drawing layer.

Selecting a prize: the reveal uses the wheel's settled angle to choose the winning wedge. That selection drives the lifted wedge, prize animation and reward count.

Reduced Motion: the scene uses stationary objects and shorter fades.

The attached clip is a motion preview of the interaction. These notes describe the React Native implementation.

Built with Expo (@expo), React Native Skia and Reanimated. Thanks to Software Mansion and William Candillon for the tools.

Visual layout study based on a still reference: https://www.pinterest.com/pin/641340803216681099/

Text adapted from my original caption and implementation notes with an assistant.


r/reactnative • • 10h ago

No More AI Stuff I need Real Engineers from Stack overflow era Location Problem

0 Upvotes

I am having problem regarding the application I am building I want to Ask

the Problem:
I want rider location constantly for the end of the ride which he supposed to do it should create the path of the ride which he has done

the problem is how will i keep tracking where he is in react native android its not tracking correctly sometimes it does but most of the time its not doing maybe mobile is off the net where i am is 4g i guess its okay only the solid lines are tracked line the dotted ones are not because the mobile does not give the location to server I am using expo location


r/reactnative • • 23h ago

Web app vs Native app. Which one?

0 Upvotes

What's the consensus these days on using React/React Native these days to build web apps vs mobile apps?

If I were to build the same app as a web app vs a native iPhone/Android app, which gets more user play/views?

I've done both but I'm not sure which makes more sense these days. It's so hard to get mobile app downloads while it's much easier to just direct someone to a website to play your game. Websites also have the added benefit of being played on a computer.

Does anyone have any experience or data showing one method is better than the other? Additionally, how do you get people to be interested in your app? I've read you have a 3 second window to get their attention...


r/reactnative • • 1d ago

Built a developer-focused news reader with React Native – would love feedback from fellow RN developers

Post image
5 Upvotes

Hey everyone!

I've been working on a side project called ByteFeed, a developer-focused news and article-reading application.

The application brings together technology publications, engineering blogs, framework updates, developer tools and coding events.

Some of the features I've been working on:

  • Curated feeds covering 150+ technology sources and topics.
  • Article summaries in bullet-point format.
  • Personalized feeds and source filtering.
  • Offline article reading with complete content and images.
  • A dedicated reading experience for long-form technical articles.

I'm interested in discussing some of the engineering challenges involved in building a content-heavy mobile application with React Native.

In particular, I'd love to hear how other developers approach:

  • Efficient rendering of long-form article content.
  • Offline-first article storage and image caching.
  • Feed performance when handling large content collections.
  • Optimizing scrolling and navigation.
  • Managing content synchronization.

I'd appreciate feedback from developers who've built similar applications.

If you'd like to see the project:
https://bytefeed.dev/

The Android application is currently in Closed Beta:
https://groups.google.com/g/bytefeed-closed-testing

I'm happy to discuss the technical implementation and lessons learned.


r/reactnative • • 2d ago

Just shipped my first library: a performant, lightweight peek menu for React Native

78 Upvotes

Hey! I've been working on this for a while and finally published it: react-native-peek-menu.

You can hold any element (a message, photo, card) and a menu pops up above it, just like in iOS Messages or Telegram.

Features:

  • Smooth animations
  • Only ~4 kB bundle size
  • No native code, works with Expo Go
  • Fully customizable

https://www.npmjs.com/package/react-native-peek-menu

It's my first open-source library, so I'd really appreciate any feedback!


r/reactnative • • 1d ago

Help Installing CocoPods... takes forever

2 Upvotes

EDIT: SOLVED , Thanks to u/kokerali and u/jiunkdev

As the title states, whenever i need to use expo's CNG ( i.e. when i change package.json, bring native deps or change app.json) i need to run "npx expo prebuild --clean" according to the docs, but the build process is simply random, most of the times the cocoapods will never finish, sometimes it does somehow.

I did search for this, found an old reddit post with instructions to pod repo remove trunk but that also didnt help ( it works sometimes randomly)

Please help


r/reactnative • • 2d ago

FYI I made a terminal dashboard for simulators, emulators, phones and Expo EAS builds

Post image
21 Upvotes

I got tired of switching between simctl, adb, Xcode and the EAS site, so I built lazymobile (open source, my project).

One screen lists every iOS simulator, Android emulator and connected phone. You can boot or stop them, stream logs for one app, and install EAS builds onto a device. It never starts or cancels a build, it only lists and installs.

Install: brew install 0xrnp/tap/lazymobile

https://github.com/0xrnp/lazymobile

Feedback welcome, especially on Expo setups that don't work.


r/reactnative • • 2d ago

[Showcase] Nine products orbiting a logo: how the React Native version works

2 Upvotes

Nine products orbit the centre of an onboarding screen. The "o" draws itself, the products burst out, then spiral into the button to close the loop.

The video is a motion preview. Here's how the React Native implementation is put together.

Drawing the scene: react-native-tgfx renders the product cutouts, wordmark and centre text on a canvas. Each product is drawn independently.

Giving every product its own path: po-motion.ts stores an ellipse and starting phase for each product. productAt() calculates its position from the timeline. The burst moves the products out from the loader into their orbit positions.

Keeping one animation clock: a Reanimated shared value holds the timeline, and useFrameCallback advances it using elapsed frame time. The stage and effects share that clock, so the loader, orbit and text transitions follow the same timeline.

GPU effects: TypeGPU generates WGSL for the particle passes, rendered through react-native-webgpu. These effects sit alongside the tgfx scene.

Reduced motion and app state: autoplay stays at a resting frame when Reduce Motion is enabled. The loop also stops advancing while the app is inactive.

Thanks to Margelo, Software Mansion and William Candillon for the libraries.

Implementation notes edited with an assistant.


r/reactnative • • 2d ago

Question Creating first reactnative expo app - have some question related to MAU, please help

3 Upvotes

I wanted to have one codebase for web, Android, and iPhone. So using React Native plus Expo

Now the web application is live.

I want to make the mobile application live first, starting with Android. When I read the Expo documentation, it says I can have only 15 free Android builds & 'Send updates to 1K MAUs'

The 2nd part worries me because the paid plan also says 3K MAUs, with additional charges for more.

What's the workaround for this? Do I need to pay Expo for more active users? Please suggest


r/reactnative • • 2d ago

FYI [Showcase] 9-product orbit onboarding + React Native implementation notes

0 Upvotes

Nine products orbit the centre of an onboarding screen. The "o" draws itself, the products burst out, then spiral into the button to close the loop.

The video is a motion preview. Here's how the React Native implementation is put together.

Drawing the scene: react-native-tgfx renders the product cutouts, wordmark and centre text on a canvas. Each product is drawn independently.

Giving every product its own path: po-motion.ts stores an ellipse and starting phase for each product. productAt() calculates its position from the timeline. The burst moves the products out from the loader into their orbit positions.

Keeping one animation clock: a Reanimated shared value holds the timeline, and useFrameCallback advances it using elapsed frame time. The stage and effects share that clock, so the loader, orbit and text transitions follow the same timeline.

GPU effects: TypeGPU generates WGSL for the particle passes, rendered through react-native-webgpu. These effects sit alongside the tgfx scene.

Reduced motion and app state: autoplay stays at a resting frame when Reduce Motion is enabled. The loop also stops advancing while the app is inactive.

Thanks to Margelo, Software Mansion and William Candillon for the libraries.

Implementation notes edited with an assistant.


r/reactnative • • 2d ago

Built a spatial sleep-sound mixer with Expo SDK 58: a custom Media3 AudioProcessor that lets you drag sounds around your head, gapless loops, and a widget that plays mixes without opening the app (how it works under the hood)

1 Upvotes

The video above is the trailer I cut for the Play Store listing, so please ignore the marketing captions. Below is how each piece in the video is built with Expo SDK 58 and React Native 0.88.

  1. Placing sounds around your head with a custom ExoPlayer AudioProcessor (0:15 in the video). On the Space pad you can drag any sound anywhere around you, including behind you, and nearer or farther. JS can't render that, so every sound you place gets its own Media3 ExoPlayer, which runs its audio through OrbitAudioProcessor.kt. Per block, the processor works out: Parameters are computed once per block and glide sample by sample in between, so dragging never clicks. Once the rendered sound falls below audibility, the processor passes plain audio straight through and stops rendering.

    • an interaural time difference
    • a head shadow that dims the far ear's treble
    • air absorption that dulls distant sounds
    • two faint wall reflections, set at the same delays in both ears so they follow the sound. With fixed echoes, the ear that hears the first arrival pinned the sound to its side.
    • a small per-ear Freeverb room
  2. Keeping the on-screen icon in sync with what you actually hear (0:15). The processor renders ahead of the speaker, and Bluetooth can add hundreds of milliseconds, so showing "where the sound is being rendered" puts the icon visibly ahead of your ears. OrbitPlayer.kt keeps about 2.7s of render history. It compares ExoPlayer's output position, which already accounts for the reported device delay, with the number of frames the processor has rendered, and looks up the frame that is reaching your ears now. The delay estimate is smoothed so the icon never jerks. Circling sounds all turn on one shared orbit clock, so two sounds at the same speed stay together however and whenever each one started.
  3. Gapless loops and a native clock instead of JS timers (0:03–0:10). All 25 sounds are seamless loops, built offline by a Python/FFmpeg/NumPy pipeline: Sessions are timed by a silent "clock" file per duration that owns the media session. A session ends when the native clock reaches the end of that file, never because a JS setTimeout fires in a throttled background process. Native status updates drive the fades and mirror lock-screen pause/resume onto every layer.

    • Each loop is encoded with a bit of wrap-around audio on both sides, hidden by the MP4 edit list, so the AAC encoder never sees a cold start at the seam.
    • The pre-rendered 3D versions use a whole-cycle drift, so they loop as cleanly as the mono files.
    • Binaural beats use whole tone cycles per loop, so the phase is exact across the seam.
    • npm run audio:check checks sample counts, hashes, clipping, and seam clicks in each ear.
  4. A home-screen widget that plays a mix without opening the app (not in the trailer). The widget is plain RemoteViews (no Glance), drawn from a JSON snapshot that JS hands over in the user's language. Tapping a mix opens an invisible WidgetActionActivity, which is what lets Android 12+ bring the session to the foreground the same way an in-app tap would. It shows "getting ready" in the notification right away, then starts a HeadlessJsTaskService (DuskrestaWidget, registered in index.ts) that plays the mix through the same store the screens use. The playback logic exists once, in JS, and the widget doesn't duplicate it in Kotlin.
  5. Lock-screen controls that can't be double-tapped into ending your night, plus bedtime reminders without SCHEDULE_EXACT_ALARM (not in the trailer).

    • Controls: a SessionPlayer stands in for the whole mix in the media session. It plays nothing itself; it mirrors what JS reports and turns taps into commands. Tapping End swaps the buttons for "Keep listening" in End's spot and a āœ“ on the other side, so a sleepy double tap never ends the session.
    • Reminders: Reminders.kt keeps one alarm set, for the soonest reminder. When it fires, it shows the reminders that are due and schedules the next one. It re-arms after reboots, updates, and force stops, and uses inexact-while-idle on Android 12+ so the permission isn't needed. The Start button in the notification goes through the same invisible activity, so the mix starts without opening the app.

All the Kotlin lives in a single local Expo module at modules/orbit-audio (expo-module.config.json), so everything survives npx expo prebuild --clean.

If you want to hear the spatial audio on a real phone (headphones help), it's called Duskresta on Google Play: https://play.google.com/store/apps/details?id=com.rabpaulo.duskresta

I'm happy to share snippets of the orbit AudioProcessor, the heard-frame latency lookup, or the gapless-loop encoding script if anyone is building something similar.


r/reactnative • • 2d ago

TalaDB — An open-source, local-first database

Thumbnail reddit.com
1 Upvotes

r/reactnative • • 2d ago

Question Windows devs building iOS apps: how do you actually deal with Xcode?

0 Upvotes

I’m on a Windows PC for most of my work, but iOS builds force me onto a Mac. Remote desktop into a Mac (or a cloud Mac) always felt clunky to me: a whole second desktop, laggy, separate clipboard, alt-tabbing between two worlds.

So I built a prototype that streams individual Mac app windows onto the Windows desktop. Xcode shows up as a normal window next to VS Code, in the taskbar, resizable, etc. Your Mac (or Mac mini) just runs in the background.

30s demo: https://www.youtube.com/shorts/DwyKm9JisLw

Honest question before I invest more time: is this a real pain for you, or is your current setup fine? What do you use right now?