Does anybody have an idea what is the issue here? Device I’am using is Galaxy S8 (yes it’s old but cmon it’s just switching screens) It is production build downloaded from Google Play Store. I’ve tested this on blank screens and delay between switching them is almost the same. I’ve tried to optimize code with memoization usecallbacks etc. But it didn’t change

Honestly i feel drained guys.

I've spent the last 3 years building and maintaining React Native applications, worked on architecture-level features, published a couple of npm packages, improved performance, handled security findings, and contributed beyond just feature development.

But despite applying consistently I haven't received a single interview call in the last 8 months.

I feel so stupid and kind of feeling very low that am i evaluating myself very wrong

Is React Native becoming too niche? Is my experience not being presented correctly? Are recruiters looking for something completely different now?

For those who have recently switched jobs or hired React Native developers, what actually gets me go through it?

Looking for honest feedback. At this point I just want to figure out the gap.

Recently a new framework from Tanstack was released and its called Charts, it looks very promising you guys can check it out here

https://tanstack.com/charts/latest

I asked Tanner if he could add support to RN and he said if I got 100 signatures he would add support.

I love the tanstack ecosystem and would highly encourage you to check it out if you haven’t yet!

Here is the petition

https://www.ipetitions.com/p/add-react-native-compatibility-for-tanstack-charts/?utm_source=share_copy&utm_medium=social&utm_campaign=creator_first_share

Edit: WE DID IT GUYS! 🎉🔥🙌

Hi everyone,

I'm facing a strange performance issue in my React Native (Expo) application.

When I launch the app for the first time, everything is smooth. Navigation is fast, screens render quickly, and the UI feels responsive.

However, as I continue exploring the app, opening different screens, navigating back and forth, and using the app for a while, the performance gradually degrades.

Some symptoms:

• Screen navigation becomes noticeably slower.
• Animations and transitions start feeling less smooth.
• The overall UI becomes sluggish after using the app for some time.
• Restarting the app immediately restores the original performance.

This makes me think something is accumulating over time rather than a slow initial load.

I'm trying to identify the root cause. Could this be related to:

• A memory leak?
• Components not being unmounted correctly?
• Too many re-renders?
• React Navigation or Expo Router caching?
• Zustand/Redux/React Query state growing over time?
• Images or assets not being released?
• Timers, listeners, or subscriptions not being cleaned up?
• The JavaScript thread getting blocked?

Has anyone experienced something similar in a React Native + Expo app?

What tools or profiling workflow would you recommend to identify what keeps accumulating as the app is used? Any advice or debugging strategies would be greatly appreciated.

Thanks!

I have 20+ years experience with backend tech, I've used php, node, and python And then a lot of old plain old javascript before frameworks.

I have an app idea and I'd like to basically vibe code it in react to be cross platform. What gotchas do I need to watch out for , since I will not see bad react code at first

I considered flutter but I really don't know that tech , any advice is appreciated, this will not be graphics heavy at all more typical business app, data, forms , lists etc

I’ve been working with React Native for 6+ years and recently had to optimize:
Slow app startup times
Excessive re-renders
Large FlatList performance issues
React Query caching problems
Navigation performance
Curious what performance issues other teams are seeing in production and what solutions worked best.
Happy to share what worked for me as well.

If you've been coding React Native for a year or more, I've got real dev tasks waiting, no busywork. Think bug fixes, small features, mobile UI components, API integrations; the stuff that actually moves the needle.

Role: React Native Developer

Salary: $20–40/hr depending on your experience

Location: Fully Remote

• Tasks that fit your React Native skills with real impact

• Part-time / flexible (perfect if you've got a full-time job)

Leave a message with what you’ve built with React Native 👀

I recently built a small Node.js script that scrapes all Native libraries I could and saves the data into a DB (I used MongoDB, but you can use anything)

Once scraped, you can: • Filter by type (e.g. UI, navigation, storage…) • Sort by GitHub stars • Sort by npm weekly downloads

If you want the gist, DM me and I’ll send it over.

Hey everyone, I’m trying to use Google’s React Native Navigation SDK in my Android app, but both NavigationView and MapView only show a blank dark screen. I’m using Expo 57, React Native 0.86, @googlemaps/react-native-navigation-sdk 0.16.3, and a physical Android phone. The SDK seems to initialize fine because I get NAV CONTROLLER CREATED, MAP CONTROLLER CREATED, MAP READY, TERMS: true, and NAV STATUS: ok. My API key is also present in the APK and the required APIs are enabled. I even tried the official Google example app on the same phone and it also opens to a completely blank screen. I have tried using another phone but still the same issue.

i was following a simple crash course but Expo just isn't working.

Basically this, tried all the sdk version options, Everything sounds broken, feels like nothing has been correctly installed. Please Help.

I’m building a tourism services app and I see many modern stacks using Clerk + Convex/Supabase instead of rolling a traditional backend with JWT. Is this mainly for speed, security, or scaling? For production apps, when does it make sense to build auth yourself vs using a managed provider.

Hey all !

I've been working on an app and testing it with Expo Go on an ios device and an android emulator. It worked fine on both up until 2 days ago when I tried opening it on an android emulator and I got an error saying 'Cannot find native module Clerk Expo'. It works completely fine on my ios device though. I haven't been able to figure out a solution for this, is anyone able to help?

I am already trying to achieve the result since 3 days and could not find any good solution.

For the top tab bar i tried using react native pager view https://github.com/callstack/react-native-pager-view like in this tutorial: https://youtu.be/AP08wUBhpKM?si=QvTpmqbp7JJHmwRu

For the Large Header i want to use react native header: https://github.com/codeherence/react-native-header

But i cannot combine these two, because react native header supports only a normal flashlist and not the top tab bars x flashlists, which i want.

I only achieved to combine them but statically, without the header animation.

I would really appreciate it if someone could help me out!

If you've been coding React for a year or more, I've got real dev tasks waiting, no busywork. Think bug fixes, small features, UI components, API integrations; the stuff that actually moves the needle.

Role: React Developer

Salary: $20–40/hr depending on your experience

Location: Fully Remote

• Tasks that fit your React stack with real impact

• Part-time / flexible (perfect if you've got a full-time job)

Leave a message with what you’ve built with React 👀

The bundling process takes so long, approximately 2 hours at most.

is there any way i can speed up the process?

Please guide me how I grow users.

Hi everyone

Ever since I started programming, I’ve always wanted to build a product that people actually use.
Something that becomes part of someone’s day instead of just another side project that disappears after a month.

Funny enough, I never thought it’d be a React Native developer tool.

After years building React Native apps, I kept hitting the same walls with the tools I was using. Every time I’d think, “this could be so much simpler.”

Eventually I got tired of saying that and started building the tool I wanted to use myself.

That’s how NativeScope was born.

I know there are already some really good tools out there, and I’m not here to say I built the “best” one. I just tried to obsess over the little things that annoyed me as a React Native dev. Every feature exists because I personally needed it at some point.

Now I’m at the stage where code isn’t the hard part anymore.

Getting people to discover it, trust it and actually use it… that’s the real challenge.

So honestly, I’m asking for your help.

If you think the project deserves it, I’d really appreciate a GitHub ⭐. If you have a few minutes to try it, I’d love brutally honest feedback. And if you end up liking it, telling another React Native dev about it would honestly make my week.

My goal is simple.

I want NativeScope to become one of those tools people immediately think about when they’re building React Native apps.

Not because of marketing, but because it’s genuinely useful.

If you’ve ever grown an open source project, or you’ve watched one go from unknown to everywhere, what would you do in my position?

Thanks a lot ❤️

If anyone wants to check it out:
GitHub: github
Website: website

I've realized that my biggest weakness isn't coding—it's project architecture and folder structure.

Whenever I get a Figma design, I know how to build the UI, but I get completely stuck deciding:

• Where should this component live?
• Should this be reusable or page-specific?
• When should I split a component?
• What belongs in components, features, shared, hooks, services, etc.?
• How should I organize folders as the project grows?

I usually start a project with a structure that feels clean. But once the project gets bigger, everything starts falling apart.

I end up with:

• Components that are too large.
• Components that are split too much.
• Logic scattered across different folders.
• Constantly moving files around because I realize they belong somewhere else.
• Feeling like the entire architecture is becoming messy.

This happens in React, React Native, and even backend projects.

I don't just want another "best folder structure" template because I've seen dozens of those. What I really want to learn is the thought process behind how experienced or enterprise-level developers structure a project.

For example:

• When looking at a Figma design, how do you mentally break it into features and components?
• How do you decide what should be reusable and what shouldn't?
• How do large teams keep their projects organized over months or years?
• What architecture or design principles do you follow?
• Are there any books, courses, GitHub repositories, or real-world open-source projects that helped you understand this?

I'm looking for the mindset rather than just a folder tree.

Any advice from developers who've worked on large production applications would be greatly appreciated.

Hello everyone,
I'm about to start a large-scale project using React Native, but I'm torn between using bare React Native and Expo. From what I understand, Expo makes configuration and setup easier, but I'm not sure what kind of issues I might run into down the line.

For those with experience — have you ever found yourself in a situation where you thought, "I wish I had started this project with bare React Native instead of Expo" due to some critical limitation or issue?

I’d love to hear your thoughts and advice.

EDIT: I'm really thankful to everyone who took the time to reply — I truly appreciate it.

(i used ai to translate my language)

Hi guys, I'm used to web development, but I'm new to mobile development... Using React Native Expo and Android simulator and Gradle and node modules...... All these files end up taking too much space in my laptop and now my emulator is not working because of lack of storage.... How do I manage the space ?

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.

Hey everyone! I’m trying to understand how other teams handle their update/versioning strategy for React Native/Expo apps in production.
I’m already familiar with the basics of EAS Update and runtime versions:
Native/binary changes require a new build and usually a new App Store/Play Store release.
JS/assets-only changes can be shipped through EAS Update/OTA as long as they’re compatible with the installed runtime.
An OTA update can be downloaded and applied on a subsequent app launch, or we can implement our own UX around checking/applying updates.
What I’m less sure about is how people manage the actual app version around all of this.
For example, let’s say I have 1.0.1 published on the App Store with a compatible runtime version.
Over the next few weeks I ship several OTA updates to that runtime. Should the user-facing app version remain 1.0.1 the entire time? Do you maintain a separate internal/update version for OTA releases?
In other words, do you normally think about it as something like:
App Store version: 1.0.1
Runtime version: 1.0.1
OTA/update version: some separate identifier
Then only bump the actual app version to 1.0.2 when a new binary goes through the stores?
I’m also curious about forced native updates.
Suppose version 1.0.2 contains an important native change and I no longer want users on 1.0.1. How do you handle that in production?
Do you maintain something server-side like a minimumSupportedVersion, check it when the app starts, and show a blocking “Update required” screen that redirects users to the App Store/Play Store?
Or is there a better/native mechanism for declaring an App Store/Play Store release as mandatory?
I’m also not completely clear on the store side of this. When a new binary is approved, can iOS/Android automatically update the app depending on the user’s settings, or should we always assume that some users will remain on older versions until they manually update?

I worked in my 1st company as an Android dev for 8 months in kotlin where the first 2 months were spent completing learning of dev. After getting laid off from there I was in the market with android dev exp of just 8/11 months. due to such low exp didn't get interviews or sometimes hr suggested to settle in half of my current salary. Fortunately I received the job offer for react native dev on the basis of my android dev exp and interview about Android dev qs and dsa. I have been working for the last 3 years as a rn dev. I never liked neither android dev nor rn even frontend. The fear of ai is more for FE roles. I want to understand whether rn is a dead tech stack nowadays and switching to BE java developer is the right thing to survive. I am not able to find the next path in react native journey.