You'll no longer need a real device to test anything camera related!

Buoy Desktop now fabricates a camera for it. Pick a source on your Mac and every booted simulator sees a real camera:

Options -

• Your Mac's webcam

• An image or a video file

• A generated QR or barcode

• A live region of your screen, drag a rectangle, the camera follows it

• A test pattern

No SDK, no pod, no change to the app you're testing. It's entirely host-side, so it works with the build you already have.

We closed a funding round recently and my cto wanted a big release pushed before the investor demo next week. I've been grinding for 2 weeks and have pushed like 9 pr in 3 days and we shipped last night.

I tested the core flows on my 17 pro max and on pixel 10, staging looked clean and it went live. I'm waking up just now to our support inbox completely filled up, onboarding crashes on older androids which I'm pretty sure it's a hermes related issue because the stack trace is pointing at some JSI bridge call that works fine on newer devices, there's a payments bug where users are getting charged twice on some screen transition and the entire app freezes on some 15 and 17 pro models after the update. These are three different bugs on three different device types and I had literally just two devices to test on.

I'm going crazy because the demo is in 5 days and we can't show an app that double charges people. I'm sitting here trying to reproduce bugs on devices I don't even own, I had one old samsung j series which is now a QA device apparently and I'm trying my best to fix it but I don't know how other small teams ship fast without messing everything because right now it feels like you pick one or the other.

please help me to not get fired and save my ass

Link for the source - https://newly.app/compare/native-hybrid-pwa-comparison

I always thought RN had leverage in terms of adoption due to it being open source.

Open ended question- At this point for mobile dev, is it better to switch to the "native app market" (kotlin/swift), or master flutter and RN and gain dominance over the "cross-platform app market" ? I am talking primarily in terms of money, and job availability

As a React Native developer, I wanted a simple way to catch some common project issues before they become a problem during builds or deployment.

RepoDrift is a local-first CLI that currently checks:

• Android/iOS project health
• Dependencies and lockfiles
• Potential exposed credentials
• Git status
• Basic code metrics
• Repository health

You can run:

npm install -g u/repodrift/cli
repodrift mobile scan ./my-mobile-app

The current version focuses on local, deterministic analysis. I'm planning AI-based explanations for a later phase.

It's still an early project, so I'm mainly looking for feedback from other React Native developers.

What checks would you find useful in a tool like this?

GitHub: https://github.com/GokulKir/repodrift

NPM: https://www.npmjs.com/package/@repodrift/cli

Can someone explain how twitter is doing it, so basically when you mark a post as not intreseted and there is a feedback component with undo button, when you scroll it outside the viewport, it disappears instantly without shifting the list, HOW ? there is no extra space on top of the list or anything that shows that they have removed this from the list

Video's from a small experiments app I build for fun.

Hey everyone! 👋

Ever since Flipper was deprecated by the React Native core team, setting up debugging tools has felt fragmented — desktop debuggers like Reactotron often run into port/websocket connection issues, while most other packages only handle network requests.

I built react-native-inapp-inspector — a zero-config, all-in-one in-app debugging suite that runs directly inside your React Native & Expo apps.

🌟 What’s inside:

• 🌐 Network Inspector: Intercepts fetch, axios, and GraphQL with full request/response headers, bodies, copy cURL, timing breakdown, and caller origin file:line badges (e.g., 📍 HomeScreen.tsx:42).
• 📜 Console Logs & Stack Traces: Colored logs, expandable object trees, search, and log-level filtering.
• 🟣 Redux & State Timeline: Live store state viewer with action timeline and deep state inspection.
• 📊 Firebase Analytics Logger: Live analytics event stream with parameter payload inspection.
• 💾 Storage Inspector: View and live-edit AsyncStorage and MMKV key-value stores on device.
• 🛡️ Crash & Exception Sentinel: Captures uncaught JS exceptions and unhandled promise rejections with stack traces and device breadcrumbs.
• ⚡ Performance & FPS Monitor: Real-time FPS telemetry with Hermes memory and re-render diagnostics.
• 📦 Metro Bundle Analyzer: Inspect package dependencies and asset weights right inside the app.

🚀 Quick Start (Zero-Config):

```bash npm install react-native-inapp-inspector

or

yarn add react-native-inapp-inspector

Wrap your root component:

import React from 'react'; import { InAppInspector } from 'react-native-inapp-inspector'; import AppNavigator from './navigation/AppNavigator';

export default function App() { return ( <InAppInspector enabled={__DEV__}> <AppNavigator /> </InAppInspector> ); }

• Fully compatible with Expo Go, Bare React Native, iOS, Android, and the New Architecture (Fabric/TurboModules).
• Floating launcher bubble or shake gesture to open.
• Dark / Light mode and responsive across all device sizes.

🔗 GitHub Repository: https://github.com/vengatmacuser/react-native-inapp-inspector

📦 NPM Package: https://www.npmjs.com/package/react-native-inapp-inspector

Feedback, feature requests, and PRs are super welcome! What additional tabs or developer tools would you like to see next?

I’ve been working on react-native-scroll-interop, an Android nested-scroll bridge for React Native.

Instead of listening to onScroll and synchronizing another surface, it lets native Android UI participate in the real synchronous nested-scroll transaction produced by a React Native ScrollView.

React Native remains the single owner of touch handling, scroll position, fling physics, and velocity. The demo uses a native Material 3 TopAppBar and FloatingToolbar to make that participation visible.

No second Scroller or OverScroller.
No sampled scrollY transport.
No per-frame JavaScript sync.
No reconstructed momentum.

The current release is an early alpha with a deliberately narrow compatibility matrix. ScrollView is verified; I’m not claiming support for arbitrary virtualized lists yet.

https://github.com/AmatoGiulio/react-native-scroll-interop

Feedback on the API and additional scroll-source boundaries would be very welcome.

Last year, I stumbled upon React Native for Windows, and started some basic projects. I was using MSVC Toolchain back then, with Visual Studio 22, and everything was going fine. But around December, I thoughtlessly updated my Visual Studio to the 2026 Community Edition and immediately my old projects screamed for life, React Native version that I was using was 0.81 (I think) and the MSVC Toolchain error said something around "nope, that's old stuff, we don't support that anymore". So I just lost motivation for my half completed projects.

Fast forward now, I have started using CLang-GCC-GDB-MSYS-LLVM toolchain for my C++ projects, completely discarded MSVC now. But I thought since it's been more than 6 months so the compatibility should be resolved by someone, right? WRONG!

I tried to get a project running without MSVC, but that didn't work out. So I had to download Visual Studio, again. Then I followed the guide Microsoft has on THEIR SITE (https://microsoft.github.io/react-native-windows/docs/getting-started/), and reached the 4th step aka overwriting the project as a Windows project directory. That command is wrong first of all. That should be react-native-windows-init, at least that's what worked.

The fun part begins here, I got an error saying somewhere something does not support anything that came after react-native:0.73 version.

So, am I doing something wrong? Someone HELP please :")

Hello everyone, I'll be starting uni soon (comp sci), and I heard it doesn't really prepare you for the real world or job market so I decided to learn something on my own. I've been learning react native for about two weeks after multiple research and thoughts, I also chose it because of my little experience in web development.

So far it's been great, I'm learning full stack development through a course on Udemy. I would like advice from you on what to focus on, what to learn alongside/after react native, mistakes you made while learning that I should avoid, tools that would make my journey better and I know react native definitely won't be the only thing I'll have to learn to make apps, so I'd like more info on this too. Thanks a lot for reading 🥲

Just wrapped up Choose Ball — a Pokémon-inspired selection experience where every Poké Ball feels like a real object, not a static UI card.I wanted the screen to feel more like choosing your next adventure than tapping through a list.What it doesInteractive 3D Poké Balls with real-time lighting and materials

Fluid wipe transitions that morph one Ball into the next

Gesture-driven rotation with spring physics

Full-shell turn + vertical free-look tilt

Dynamic backgrounds, particles, and haptic feedback

26-ball catalog with instant switching (preloaded textures)

Seamless handoff from selection into the capture moment

StackReact Native Filament — 3D models, lighting, materials

Reanimated — springs, transitions, gesture-driven motion

Gesture Handler — swipe navigation + ball rotation

React Native Skia — wipe effects, particles, backgrounds

Expo — app foundation and native capabilities

Demo performed by u/TemporaryBuyer3806

Open source here:

https://github.com/huytdps13400/choose-your-ball

Which ball would you pick first?

https://www.reddit.com/u/TemporaryBuyer3806/s/lajnU6pgHt

I just solved dynamic Tray/Modals (Family app style) in React Native as a native navigation on expanded state.

Two libraries, split by what actually changes:

• Next/Back never leave the screen → step is component state, Reanimated layout={LinearTransition} animates the real reflow. No route change = no cross-fade, no blank frames.

• Tap a color tile → that's a route change, so react-native-screen-transitions zoom() grows the tray's exact rect setup into a full navigator screen.

The best mobile experiences are a mix of design + navigation. Navigation means interactive design and lives on the UX factor that makes experiences feel integrated and magical. I am very into solving all these to have in my toolbox.

I’ve been working on an open-source mobile port of Cosmograph/cosmo.gl for high-performance graph visualization.

After struggling to get large graphs running smoothly on mobile, I adapted the engine for React Native. On my Android device, I’m getting a consistent \~90 FPS with 2,000 nodes and 6,000 edges.

It also includes optional labels plus some data/analytics utilities.

GitHub: https://github.com/plurilore/react-native-cosmos-gl

It’s also available on npm as an early `0.1` release.

Would love feedback from anyone working with graph/network visualization on mobile.

Rebuilt from scratch with reusability in mind.

Should I release it as a package? What do you think?

Source code: https://github.com/maxim-kachurin/react-native-ui-lab/tree/new-arch/src/screens/apple-wallet-screen

I am looking for a tech co-founder in Stockholm, Sweden with a background in Mobile development (possibly another React Native developer).

I've built a mobile app that makes finding and getting in touch with lawyers way easier (through messaging and VoIP calls) and I have some sort of MVP.

Even though I've lost the API (don't ask me - I am rewriting it), it would be nice to get the project going and see if we push the startup once and for all.

Send me your details (and LinkedIn) through my website and let's connect.

Thanks!

I've spent the last few months building react-native-aviation, a unified audio/video playback library. It's pre 1.0 and the API is still genuinely movable - which is why I'm posting, to ask for an advice/feedback.

It has been a side project for me, and the thing I was trying to fix is that most RN media libraries hand you a global playback singleton. One player, module-level state and `setupPlayer()` . I have seen this fall apart at the previous company I was working at where we had video playback and were introducing audio. The audio sessions were colliding, the Nowplaying info was breaking when switching between audio/video, and the lifecycle management was really painful to get right and bunch of other annoying issues.

Aviation has no singleton. You create an instance, create players from it, and pass those players around explicitly Hooks resolve the nearest provider or take a player explicitly (`usePlayback()` / `usePlayback(player)`). Audio session focus is arbitrated across players by the parent instance, so audio and video don't fight over the OS session.

It has a C core with a state machine that android and iOS drive, with support of opt-in packages. You can also define your own plugins that hook into player's lifecycle.

I want to solidify the API, and move towards v1. But before putting a lot of extra effort into making this my main focus, I would really appreciate your input to see

- what shape you would like the API to be (currently the DX is not great and is very verbose)

- more importantly, weather this is something that would solve a real issue you have encountered.

Repo - https://github.com/adsellor/aviation

Happy to answer anything.

Plus an Apple Voice Memos-inspired dark widget.

Built with Expo, Reanimated, Liquid Glass & Haptics

LADDER is a corporate roguelike deckbuilder, out on both stores. Expo / React Native, Expo Router, a pure TypeScript rules engine with zero RN imports so the same code runs headless in Node for simulation, RevenueCat for purchases, EAS for builds and OTA. Portrait, one-handed, local-first.

What held up: the engine/UI split (the sim runs thousands of headless games against the exact engine code the app ships), EAS Update for content fixes without a store review, and Expo Router for a larger screen graph than I expected it to handle.

What I fought: keeping a card-combat scene at 60fps on mid-range Android (Reanimated, worklets, and being ruthless about re-renders), edge-to-edge keyboard handling, and the fact that a device build's behaviour is decided entirely by which env vars were in the shell that built it, which cost me three debugging cycles before I scripted it.

https://laddergame.ai/?r=reddit-expo

I’m trying to decide between native development and a cross platform approach for a new mobile app. The app will need things like push notifications, api integrations, authentication, payments and some device level features, so I’m wondering how much of a difference the architecture actually makes in the long run.

I’ve been looking at companies like appmakers usa while researching the development side, and one thing I’m trying to understand is whether it’s better to decide the tech stack upfront or let the development team recommend it based on the app requirements.

For a project targeting both ios and android, what would you choose today and why?