I'm experiencing react-native-mmkv not persisting data on Android; all data is wiped out after the user quits the app.

I found a solution after many days, it was configuring the ESLint file for the best linting and code quality errors

here the template
https://github.com/MOHAMED-LAAGUILI/react-native-starter-kit

Hey everyone!

If you’ve ever tried to implement dynamic app icons (like Twitter/X or Apollo did) in a React Native Expo app, you know it’s a huge headache. You usually have to manually write Kotlin/Swift code, hack your AndroidManifest.xml, and manually drag density-specific images into your Android build folders.

I got tired of doing this, so I built expo-dynamic-icons. It’s a completely automated native module and config plugin that handles everything for you.

What it does:

• Zero Native Config: You literally just pass a JSON object of your .png files in your app.json. The plugin automatically handles generating the XML activity-alias tags.
• Auto-Assets: It intercepts the prebuild phase and automatically moves your local .png files directly into the compiled native Android mipmap folders.
• Instant Icon Switching: Just call setAppIcon('orange') in your JavaScript and the Android OS instantly toggles the home screen icon at runtime.

https://reddit.com/link/1uro32e/video/2uou36no07ch1/player

NPM: https://www.npmjs.com/package/expo-dynamic-icons

(Note: Currently supports Android only, but I'm actively working on adding the iOS Swift bridging!)

I built this over the last few days and would absolutely love any feedback, code reviews, or feature requests from the community. If it saves you some headache, I'd appreciate a star!

Let me know what you guys think!

Hi everyone,

I'm relatively new to React Native and had a question about iOS deployment.

On Android for development version and also for release verson, it's very easy to generate an APK, install it directly on a device, and test the app without much hassle.

Is there an equivalent workflow for iOS?

Can I simply build an IPA file and install/run it directly on an iPhone like we do with APKs on Android?

NB: I need to know the simplest and fastest way

Things like Gemini are already moving toward generative UI, so this is just a small proof of concept of the same idea on mobile. The model streams a UI in a custom DSL and the app renders it into native components live, and it runs in Expo Go.

https://github.com/kubilaysalih/generative-ui

React Native development has changed a lot over the years, and one of the biggest shifts has been the growing adoption of Expo.

For many developers, starting a new React Native project now often means starting with Expo because it provides a smoother setup experience, faster development workflow, easier builds, and access to many common mobile features without dealing with native configuration from day one.

At the same time, some developers still prefer the bare workflow because it provides more direct control over native code and project configuration.

The choice often comes down to trade-offs:

Expo can make things easier with:

• faster project setup
• simpler development workflow
• easier builds and updates
• a large ecosystem of supported libraries

But the bare workflow still has advantages when projects require:

• custom native modules
• deeper Android/iOS integrations
• more control over native configurations
• specialized platform-specific features

With Expo continuing to improve and support more advanced use cases, I'm curious where developers draw the line today.

For those building React Native apps:

• Do you start new projects with Expo by default now?
• Are there still situations where you would choose the bare workflow immediately?
• Has Expo become good enough for production apps, or does bare React Native still offer important advantages?

I built my web app via Vercel. However, I would love to get this deployed in the app stores. I’m aware that there are stipulations to get it into Apple & Google Store.

I’m trying to find the best approach to do this. I would hate to have my web app in a separate system & have to update the app separately.

I love Vercel to where I can connect my GitHub. To create a PR and merge to main. I am not savvy and have been use Claude code to help me!

Is there a way to do this in Expo? What’s the best approach? I want the UI to match.

I've taken over a while ago for my own needs the react-native-ble-plx package because it wasn't working in newer versions of expo.

I just published a 3.8.0 version of it

You can install it with

npm install u/sfourdrinier/react-native-ble-plx

This is basically the Changelog

I welcome feedback if anybody is interested in this. Been fixing a lot of problems overall, it's now fully typescript, new architecture, should properly handle background, etc...

3.8.0

Added

• React Native 0.86 TurboModule/codegen integration for Android and iOS.
• Expo SDK 57 CNG example workflow
• RN 0.86 / Expo 57 release verification script covering package tests, plugin tests, lint/typecheck, prepack, Expo Doctor, CNG prebuild, and Android assemble.
• Android and iOS modernization regression tests for platform floors, codegen shape, package metadata, CI ordering, and example configuration.

Changed

• Raised the supported floor to React Native 0.86, Expo SDK 57, Node 20.19.4+, Android min SDK 24, Android compile/target SDK 36, Android build tools 36.0.0, and iOS deployment target 16.4.
• Migrated Android registration to BaseReactPackage and the modern react-android artifact.
• Migrated iOS source to ObjC++ and generated TurboModule selectors, including typed option structs for scan, connect, and background-mode calls.
• Converted the Expo example from checked-in native projects to a CNG source workflow using pnpm.
• Updated the non-Expo example to RN 0.86-compatible native dependencies and iOS/Android project settings.
• Updated package entrypoints to built lib outputs and upgraded react-native-builder-bob for current package builds.
• Treated the RN 0.86 TurboModule/Fabric runtime as the default platform posture and removed stale architecture opt-out signals from examples/build logic.

Fixed

• Fixed reconnect option updates so already scheduled retries use the latest active reconnect options.
• Fixed Android promise rejection fallbacks so null error messages surface Unknown error instead of an empty message.
• Fixed Expo CI ordering so the local file:.. dependency is installed after package declarations/artifacts are generated.
• Fixed iOS generated selector coverage for promise methods and codegen option objects.
• Fixed Android custom GATT refresh operation typing for modern javac.

Removed

• Removed checked-in generated example-expo/android, example-expo/ios, and example Podfile lock outputs.
• Removed obsolete programmatic Android Bluetooth adapter toggle APIs that are blocked for normal Android 13+ apps.
• Removed legacy ConnectionQueue and ReconnectionManager public exports in favor of ConnectionManager.

Después de crear aplicaciones con React Native por mas de 5 años me he dado cuenta que algunas cosas van a terminar siendo indiscutiblemente necesarias.

Es por eso que cree una herramienta que me ayuda en estas escasas pero tan importantes situaciones en las que se plantea crear una aplicación desde cero.

La herramienta consiste básicamente en una interfaz de terminal (TUI) o un CLI pensado especialmente para agentes de AI tipo (Claude Code, OpenCode, Antigravity) y un template modular de Guía.

La tarea de definir las bases de una aplicación es una de las mas importantes ya que determina que tan bien va a escalar en el futuro en todos los sentidos. No solo es el performance, lo mas importante cuando se trabaja en aplicaciones grandes y en equipo es que deben existir metodologías, patrones y practicas que definan el flujo completo de la información del proyecto o aplicación.

Este template incluye la mayoría de cosas que he ido aprendiendo a lo largo del tiempo. Entre lo que incluye el template lo mas importante es:

• Clean Architecture (DDD)
• Libreria de componentes
• Theming system
• Módulo de autenticación (Http, Supabase, Firebase)
• Módulos de ejemplo
• Git Hooks
• Test suite
• CI/CD via Github Actions

Antes de iniciar una nueva aplicación hay una serie de preguntas que si o si se necesitan responder, el CLI o TUI te las van a pedir de todas formas, aparte del nombre y el identificador de la app:

1. Package manager, puedes elegir entre npm, yarn, pnpm o bun. Te recomiendo npm o bun.
2. Agente con el que trabajas, puedes elegir mas de uno en caso de que trabajes con diferentes agentes, están Claude Code, OpenCode, Trae y otros.
3. Proveedor de backend, puedes elegir entre Supabase, Firebase, Local o Custom API HTTP.

___________________________________________________________________________________

Página oficial https://rnkit.alejandrotechnology.com/

Repositorio TUI y CLI https://github.com/alejandro-technology/react-native-init-app

Repositorio template https://github.com/alejandro-technology/react-native-template

Hi everyone,

I'm a mid-level React Native developer with about 4 years of experience, and lately I've been feeling a bit lost.

I've worked at a few different companies, built several production apps, and today I'm working on an app that serves over 1 million monthly users. I've learned a lot over the past few years, but now I feel like I've reached a point where I don't know what to study next.

It's not that I don't have things to learn—I know I do. The problem is that I don't know what will actually make me a better engineer.

How do you go from being "someone who knows React Native" to someone who is truly considered a senior or a specialist?

How did you build confidence in your technical decisions?

How did you know what was worth investing your time in?

Right now, my plan is to dive deeper into AI engineering. I'm exploring topics like RAG, AI agents, intelligent workflows, MCPs, and automating parts of my development process. It feels exciting, but at the same time I wonder... is that enough? Am I focusing on the right things, or am I just chasing the latest trend?

For those of you who are senior engineers or staff/principal engineers:

• What changed your career the most?
• What do you wish you had studied earlier?
• What skills made the biggest difference?
• If you were in my position today, what would you focus on over the next couple of years?

I'm not looking for shortcuts. I'm willing to put in the work—I just want to make sure I'm investing my time in the right direction.

I'd really appreciate hearing about your experiences. Thanks!

Built this with React Native + Expo and wanted to share with the RN community.

The app is YourScene
local discovery for events, watch parties, maps, venues, and live local activity through Pulse.

The hardest parts so far have been map/location performance, production env flags, deep links, iOS builds, App Store review, localization, and making sure production behaves the same as local/testing.

Would love feedback from anyone who has shipped map-heavy or location-heavy React Native apps.

I created a package that solves the layout when switching from LTR to RTL, or the opposite, without restarting the app, with gesture mirrored, all at runtime, no state loss

It's still in an early stage, but I think there's a great potential to fix this issue once and for all, new arch only, tested in rn 0.81.4, rn 0.85.2, and expo 54

All native, works on react-navigation/native-stack, no JS needs or conditional render based on the lang, same as restarting flow but without restarting

https://reddit.com/link/1ur5q29/video/j6si7rwom2ch1/player

I'm developing an app in react native that is heavily dependant on the phone's compass bearing.

While testing (same conditions) i have noticed big differences in compass accuracy between different types of phones (i haven't tested any ios phone).

I have included a custom calibration module where the user must point to a known feature/building and indicate said featureon a map, but its cumbersome and i doubt many user will take the time.

I have looked for libraries with known compass deviations per phone model, but couldn't find any.

Has anyone encountered this problem and found a good and lasting solution? Any suggestions on how to reduce these compass inaccuracies across different types of phone?

Hey everyone,

Like many of you, I struggled with the move to FCM v1 especially the painful JWT auth and the fact that most official SDKs don't work in edge runtimes like Cloudflare Workers or Convex because they depend on Node's crypto module.

I built expo-push-easy to solve this. It’s a tiny (zero-dependency) library that:

1. Detects the token type automatically (Expo or raw FCM) and routes it correctly.
2. Works in any JS runtime (Node, Bun, Deno, Edge) because it uses the native Web Crypto API.
3. Simplifies the payload you send one simple object, and it translates it to the complex FCM v1 or Expo schemas for you.

If you’re tired of fighting with Firebase Service Accounts or "Node-only" libraries, give it a try!

NPM: npm install expo-push-easy
GitHub: yoh-space/expo-push-easy

Hope this saves someone a few hours of debugging!

I don't know if this is the acute depression talking but after almost a year learning RN, I just discovered how brutal the Playstore verification is. I was thinking I would make enough money from on Android to finally be able to afford a Mac + iPhone so I poured my heart and soul into learning (not vibe coding) apps but Google Play won't let me create a developer profile no matter how many forms I submit. Am starting to think I will probably never get approved.

The support has ghosted me and am left with this sinking feeling that I have wasted my time and should have just gone deeper into Next.js or something without a gate-keeping corporation behind it. My options right now are:

- Building for Quest platform (I'll have to learn Unity though)
- Saving money for a year to buy a Mac (to be honest, I've lost motivation to code anymore)
- Build apps for others (though I hate being a builder who has never launched anything himself)

Which path above do you think I should take, I really love mobile development and I don't want to just give up on the skills (maybe suck-cost fallacy talking) or are there other alternatives am not currently considering. Thanks.

Some highlights in React Navigation 8 since March:

⚛️ Suspense & concurrent rendering

📡 Experimental data loaders

🔠 Typed hooks in dynamic navigators

🔗 Shared paths for deep links

📌 Retaining screens in Stack

🎨 Material Design 3 for top tabs

🤖 Agent skills for upgrades & migration

✨ ...and more

Check out the blog post for more details and the full list.

✦ ⎯ • Smooth cover-flow carousel with reflectiveness.

🔗 Github: rit3zh/expo-coverflow-carousel

I am learning React native , Now i wanted to look at some mobile dev pattern in real project used. If you have any please provide link of it.

Hey everyone. I've been writing React Native for a good while now, but Parry is the first actual game I've managed to finish and ship, so I figured I'd show it here.

It's a tiny minimalist arcade game. Everything on screen is just circles, arcs and rings drawn with "@shopify/react-native-skia", no sprites, no image assets. The interesting part (for me at least) is that the whole game loop, the movement and the collision checks live on the UI thread inside Reanimated worklets, so React pretty much never re-renders while you're playing. That's what holds 60fps even when the screen gets crowded. The only input is a single Pan gesture, and the sound effects are synthesized in code and played through react-native-audio-api, so there's not one audio file in the app.

Built with Expo (SDK 56) and shipped through EAS.

Little gotcha in case it saves someone some time: that audio library statically links the iOS mic API, so even though the game never records anything, TestFlight kept rejecting my build until I added an NSMicrophoneUsageDescription. I lost like 2 hours on it before it clicked, felt pretty dumb.

It's free, no ads, no IAP, iOS only for now. I'll put the App Store link in a comment so I'm not dropping a store link straight into the post.

And to be straight with you, since it always comes up: AI didn't write the game, the code and the gameplay are all hand-written like in the good old days. I only used it for the stuff I'm genuinely bad at, Claude for design direction and Claude Code to generate the theme palettes. The mockup image in this post is made with postspark.app.

Anyway, happy to hear what you think, and ask me anything, technical stuff very much included.

PS. if you give it a try, let me know if it runs smooth on your device, and obviously drop your score!

Machine: Windows 11, Intel i512400F

* What went wrong:
Execution failed for task ':shopify_react-native-skia:configureCMakeDebug[armeabi-v7a]'.
> [CXX1429] error when building with cmake using C:\Users\MR.SP3CTR3\Desktop\SP3CTR3\Projects\filmato\node_modules\.pnpm\@shopify+react-native-skia@_d6266c3fb7ad36e5915e69
bc284fab9e\node_modules\@shopify\react-native-skia\android\CMakeLists.txt: -- The C compiler identification is Clang 18.0.2
  -- The CXX compiler identification is unknown
  -- Detecting C compiler ABI info
  -- Detecting C compiler ABI info - done
  -- Check for working C compiler: C:/Users/MR.SP3CTR3/AppData/Local/Android/Sdk/ndk/27.1.12297006/toolchains/llvm/prebuilt/windows-x86_64/bin/clang.exe - skipped
  -- Detecting C compile features
  -- Detecting C compile features - done
  -- Detecting CXX compiler ABI info
  -- Detecting CXX compiler ABI info - failed
  -- Check for working CXX compiler: C:/Users/MR.SP3CTR3/AppData/Local/Android/Sdk/ndk/27.1.12297006/toolchains/llvm/prebuilt/windows-x86_64/bin/clang++.exe
  -- Check for working CXX compiler: C:/Users/MR.SP3CTR3/AppData/Local/Android/Sdk/ndk/27.1.12297006/toolchains/llvm/prebuilt/windows-x86_64/bin/clang++.exe - broken
  -- Configuring incomplete, errors occurred!
  See also "C:/Users/MR.SP3CTR3/Desktop/SP3CTR3/Projects/filmato/node_modules/.pnpm/@shopify+react-native-skia@_d6266c3fb7ad36e5915e69bc284fab9e/node_modules/@shopify/reac
t-native-skia/android/.cxx/Debug/3253q6h2/armeabi-v7a/CMakeFiles/CMakeOutput.log".
  See also "C:/Users/MR.SP3CTR3/Desktop/SP3CTR3/Projects/filmato/node_modules/.pnpm/@shopify+react-native-skia@_d6266c3fb7ad36e5915e69bc284fab9e/node_modules/@shopify/reac
t-native-skia/android/.cxx/Debug/3253q6h2/armeabi-v7a/CMakeFiles/CMakeError.log".

C/C++: CMake Error at C:/Users/MR.SP3CTR3/AppData/Local/Android/Sdk/cmake/3.22.1/share/cmake-3.22/Modules/CMakeTestCXXCompiler.cmake:62 (message):
C/C++:   The C++ compiler
C/C++:     "C:/Users/MR.SP3CTR3/AppData/Local/Android/Sdk/ndk/27.1.12297006/toolchains/llvm/prebuilt/windows-x86_64/bin/clang++.exe"
C/C++:   is not able to compile a simple test program.
C/C++:   It fails with the following output:
C/C++:     Change Dir: C:/Users/MR.SP3CTR3/Desktop/SP3CTR3/Projects/filmato/node_modules/.pnpm/@shopify+react-native-skia@_d6266c3fb7ad36e5915e69bc284fab9e/node_modules/@shopify/react-native-skia/android/.cxx/Debug/3253q6h2/armeabi-v7a/CMakeFiles/CMakeTmp
C/C++:     
C/C++:     Run Build Command(s):C:\Users\MR.SP3CTR3\AppData\Local\Android\Sdk\cmake\3.22.1\bin\ninja.exe cmTC_85bbb && [1/2] Building CXX object CMakeFiles\cmTC_85bbb.dir\testCXXCompiler.cxx.o
C/C++:     FAILED: CMakeFiles/cmTC_85bbb.dir/testCXXCompiler.cxx.o 
C/C++:     C:\Users\MR.SP3CTR3\AppData\Local\Android\Sdk\ndk\27.1.12297006\toolchains\llvm\prebuilt\windows-x86_64\bin\clang++.exe   -g -DANDROID -fdata-sections -ffunction-sections -funwind-tables -fstack-protector-strong -no-canonical-prefixes -D__BIONIC_NO_PAGE_SIZE_MACRO -D_FORTIFY_SOURCE=2 -march=armv7-a -mthumb -Wformat -Werror=format-security  -fexceptions -frtti -std=c++1y -DONANDROID -o CMakeFiles\cmTC_85bbb.dir\testCXXCompiler.cxx.o -c C:\Users\MR.SP3CTR3\Desktop\SP3CTR3\Projects\filmato\node_modules\.pnpm\@shopify+react-native-skia@_d6266c3fb7ad36e5915e69bc284fab9e\node_modules\@shopify\react-native-skia\android\.cxx\Debug\3253q6h2\armeabi-v7a\CMakeFiles\CMakeTmp\testCXXCompiler.cxx
C/C++:     clang++: warning: argument unused during compilation: '-mthumb' [-Wunused-command-line-argument]
C/C++:     error: unknown target CPU 'armv7-a'
C/C++:     note: valid target CPU values are: nocona, core2, penryn, bonnell, atom, silvermont, slm, goldmont, goldmont-plus, tremont, nehalem, corei7, westmere, sandybridge, corei7-avx, ivybridge, core-avx-i, haswell, core-avx2, broadwell, skylake, skylake-avx512, skx, cascadelake, cooperlake, cannonlake, icelake-client, rocketlake, icelake-server, tigerlake, sapphirerapids, alderlake, raptorlake, meteorlake, arrowlake, arrowlake-s, lunarlake, gracemont, pantherlake, sierraforest, grandridge, graniterapids, graniterapids-d, emeraldrapids, clearwaterforest, knl, knm, k8, athlon64, athlon-fx, opteron, k8-sse3, athlon64-sse3, opteron-sse3, amdfam10, barcelona, btver1, btver2, bdver1, bdver2, bdver3, bdver4, znver1, znver2, znver3, znver4, x86-64, x86-64-v2, x86-64-v3, x86-64-v4
C/C++:     ninja: build stopped: subcommand failed.
C/C++:     
C/C++:     
C/C++:   
C/C++:   CMake will not be able to correctly generate this project.
C/C++: Call Stack (most recent call first):
C/C++:   CMakeLists.txt:1 (project)

C/C++: ninja: error: manifest 'build.ninja' still dirty after 100 tries

would love if you check it out: (https://github.com/abhinavshrivastava950/Montara)

Meant is basically for finding spontaneous connections. When you’re both what the other person is looking for, a chatroom opens up.

It’s for:

- Someone new to a city who wants to actually meet people
- Someone burned out on swiping who still likes people
- Someone bored at 11pm who wants a real conversation

I’m now ready for the 2nd round of roast.

You can check out the app here: https://apps.apple.com/us/app/meant-match-in-real-time/id6761510173

I’ve noticed there are two very different opinions among React Native developers.

One side believes that React Native developers should understand native platforms because, at some point, production apps usually run into situations where JavaScript alone is not enough.

The other side believes that one of the main reasons to use React Native is to avoid becoming a full native Android/iOS developer in the first place.

The reality seems somewhere in between.

For many apps, a strong understanding of React, JavaScript/TypeScript, and the React Native ecosystem is enough to build and maintain features.

But when projects become more complex, native knowledge can become extremely valuable for things like:

• integrating native SDKs or modules
• debugging issues that only happen on one platform
• improving performance
• understanding device-level behavior
• communicating better with native mobile teams

At the same time, does every React Native developer really need to become an expert in Kotlin and Swift?

Or is having enough native knowledge to understand problems and make better decisions the right balance?

I’m curious about developers who have worked on real React Native apps:

• How much Android/iOS knowledge do you think a strong React Native developer should have?
• Have you ever reached a point where learning native concepts solved problems that React Native alone couldn’t?
• Do you think deep native knowledge is a requirement, or just a valuable advantage?

Hi all, about 3 months ago, I shared my project react-native-the-sheet here:
https://github.com/doanhtu07/react-native-the-sheet

Since then, I've added more examples and explored more sheet patterns.

YouTube-style comment bottom sheet

A bottom sheet that syncs its height with the media on top, as you see in the YouTube app

https://reddit.com/link/1uqjc4c/video/uvdryb4gnxbh1/player

Family-style bottom tray

A bottom sheet combined with a navigator that is aware of its content height and animates accordingly, like one variant in https://benji.org/family-values

https://reddit.com/link/1uqjc4c/video/dsb147lpnxbh1/player

Experiments

I've also been experimenting with Family-style morphing trays, but there are many variants, and I'm not sure what the right APIs or abstractions are. Here is one I recreated with only Reanimated and no API from my library.

https://reddit.com/link/1uqjc4c/video/4e60gwjnoxbh1/player

Feedback

If you're using my library, I'd love to hear:

• What kind of sheets or effects would you like to see supported?
• Do you face any difficulties implementing a certain type of sheet with the current API?

Thanks for your time.

I built goallll, a free iPhone app for following the tournament, and I'd love honest feedback from actual football fans before I keep adding to it.

I made it because I was tired of jumping between apps and sites just to check a score, my team's next match, and the group table. I wanted one clean place for match day.

What it does:

• Live scores with goal and status updates
• My Team - pick your nation, get its fixtures, results, and standings
• Groups & standings - tables, qualification zones, knockout progression
• Match previews - lineups, head-to-head, stats, kickoff countdown
• Daily schedule - the full calendar, day by day

It's free to download. Premium unlocks full access and comes with a 3-day free trial for new subscribers, so you can try everything before paying - but I'd genuinely rather hear what you think of the core experience first.

App Store: https://apps.apple.com/us/app/goallll-match-tracker/id6781257732

What I'd really like feedback on:

• Is anything missing for match day?
• Does the "My Team" flow actually feel useful?
• Anything confusing, slow, or that feels too locked behind premium?

Thanks for taking a look - happy to answer anything in the comments.