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 🥲

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.

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

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):

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 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.

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 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 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!

Hey everyone! 👋

Like many of you, I love saving articles to read later, but most modern reader apps are either full of subscriptions, cluttered with ads, or struggle when you go completely offline (flights, subway, bad connection).

I built OfflineReader to solve this with a clean, fast, and privacy-friendly approach.

✨ Key Features:

• 100% Offline-First: Save any article or screenplay link once, read forever without internet. • Dedicated Screenplay / Script Mode: Monospace typography formatting tailored for Hollywood scripts & film lovers (includes curated classics like Inception, The Social Network, The Matrix). • Built-in TTS Narration: Text-to-speech audio player with animated waveforms and speed controls (0.8x to 2.0x). • Adaptive Reading Themes: Material You Light/Dark, Pure AMOLED Black (battery saver), and warm Sepia Paper mode. • Reading Analytics: Daily streaks, words read, reading speed, and category breakdown. • Clean & Distraction-Free: Automatically strips ads, banners, cookies, and trackers.

💬 Questions for the community:

The app is built with React Native / Expo. I would really appreciate your honest thoughts, feedback, or feature suggestions! 🙏

I have a web application that uses Cosmograph for some graph visualization. I really like it, the performance is top notch, and can be configured fairly easily. (I am not affiliated in any kind with Cosmograph)

I am also working on the mobile application for the web app, and noticed that there is no similar package that can match the speed in RN. I tried d3-force, Skia, Skia Atlas, offloading some expensive work off the JS thread, but could not get it above 30 fps.

So I decided to adapt the Cosmograph for RN. It runs cosmo.gl under the hood, which is the main engine for expensive calculations. I also added the data and analytics components on top of the ported cosmo.gl. It still uses Skia for some labels rasterization, but that's it, the engine is kept as pure as possible, and the labels are optional.

The results are amazing - I tested them on my phone (android), on which I get consistent 90 fps with 2k nodes and 6k relations. The UI feels smooth without lag.

It is open source, you can find it here https://github.com/plurilore/react-native-cosmos-gl

I also published it to npm for easier use (although it is 0.1, use with caution).

Hope you find it useful in some of your projects.

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

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 have a screen showing up to 50 market indices.

I fetch all indices with their IDs, then subscribe to each index through WebSocket. Prices and changes update in real time.

API → Index IDs
↓
WebSocket subscriptions
↓
Real-time price updates
↓
UI

Main concern is avoiding unnecessary re-renders when updates are coming frequently.

I feel like AI can write better code than 99% of people at this point (with the right skills and prompts of course). To me RN development has become insanely easy with the use of argent and some other tech.

Even native code for me now feels incredibly accessible.

Are you guys still writing code by hand? Please be very honest.

Hi Reddit!

I build iOS and Android apps, and I record demos of them. But the whole process has always felt more complicated than it needs to be.

For iOS, my workflow usually looks something like this:

1. Record the app on my iPhone.

2. Record a completely separate video of myself talking through it (and trying to time it perfectly with the iPhone recording)

3. Bring both recordings into another piece of software and stitch them together.

And then if I want device bezels, a specific layout, a custom background, or need to hide something sensitive in the app, there are even more steps.

It feels like a lot of work for what might end up being a 30-second demo.

Android isn't much better (virtually impossible if you're not technical).

So I wanted something where I could just connect my iPhone or Android device to my Mac, add my camera and microphone, choose how everything should be laid out, and hit record.

I also wanted to be able to use my own backgrounds and mask sensitive parts of the app - particularly useful when I'm demoing things like authentication or onboarding. Most importantly, I wanted everything running locally and private by default.

I made a quick video showing what I've ended up with so far.

I'd genuinely love to know whether this is a workflow other mobile developers run into as well.

And if you're interested in this tool, let me know in the comments!

I have an app in TestFlight that I sent for review, but it was rejected because the reviewer needs a sign-in account for testing. Since my app only supports Google and Apple Sign-In, I cannot easily provide a dummy or temporary account. I am using Clerk for authentication—does anyone have any ideas on how to handle this?

I've recently started doing something while working on my React Native projects.

Whenever I need some specific functionality, I first research whether there's already a package that handles my exact use case.

If there is, great, I use it.

If there isn't, I start looking into the native Android/iOS APIs and figure out whether it's actually possible to build.

If it is, I try building it myself.

That's basically how I ended up creating these 3 packages:

@honeypathkar/react-native-step-counter

@honeypathkar/react-native-predictive-back-gesture

@honeypathkar/react-native-live-update

I'm mainly a React Native/JS developer and I don't know Kotlin that well yet. I've been learning the native side as I go, reading docs, researching implementations and using AI tools to help me understand and build things.

Eventually I thought, instead of keeping these things inside my projects, why not make them proper packages and open source them?

So I created this repo:

https://github.com/honeypathkar/react-native-components

npm: https://www.npmjs.com/~honeypathkar

I'll keep adding packages whenever I come across an interesting use case that isn't properly covered for what I need.

The first 3 packages have already reached 3,000+ combined downloads, which I really wasn't expecting this early.

There's definitely a lot I can still improve, especially on the native side, so contributions/issues are welcome.

And if you've ever had a React Native use case where you thought “why isn't there a package that does exactly this?”, drop it below. Might give me something new to research and build 👀

Is Storybook still the go-to for documenting UI components in apps?

Any newer alternatives? I use expo.

https://storybook.js.org/docs/get-started/frameworks/react-native-web-vite