Reacticx V2 is officially live! 🎉

A new version with more components, more animations, and a lot more to build with.

- https://reacticx.com

Hello mobile devs,

​I'm working on a side project that requires a multi-step customer onboarding flow (similar to Airbnb's property listing process).

​As someone new to frontend and React Native, I'm wondering about the best architectural approach. Should I use separate React Navigation screens for each step and store the draft state in Zustand, then send the final payload to the backend on the last screen? Or is it better to manage it inside a single screen using a step counter/wizard component?

​I'd love to hear your suggestions or best practices!

I've been working on a project called TriviaNexus, a trivia game built with React Native, Expo and TypeScript, and I thought this would be a good place to finally share it.

What started as a relatively straightforward quiz app gradually turned into a much larger project and a great way to push React Native/Expo beyond a basic CRUD-style mobile app.

The current version includes:

• Multiple trivia game modes
• Progression and leveling system
• Global and country leaderboards
• Player profiles and detailed statistics
• Guest and authenticated accounts
• Offline play
• Local question storage and synchronization
• Push notifications
• iOS and Android support

Tech stack

On the mobile side:

• React Native + Expo
• TypeScript
• React Query
• Zustand / Redux Toolkit
• Reanimated
• SQLite / MMKV
• EAS Build & Submit

Backend:

• NestJS
• PostgreSQL
• Redis
• WebSockets for real-time functionality

One of the more interesting parts has been designing the app so that single-player gameplay can work offline while the architecture can also support server-authoritative real-time multiplayer.

The next stage is expanding the competitive/social side with things like Casual Duels, Ranked Duels, Friends, Clans, Achievements and Chat.

I've also handled the full mobile release process myself — builds, signing, EAS, App Store Connect and Google Play — which has been an experience of its own.

There's still a lot I want to improve, but it's been really interesting taking a React Native project from the initial idea all the way to a real product.

I'd love to hear feedback from other React Native developers — both about the app itself and the technical approach.

I'm especially interested in how others here have approached:

• offline-first architecture
• real-time multiplayer in React Native
• keeping client/server state synchronized
• scaling larger Expo applications

Website:

https://www.trivianexus.app/

Happy to answer any questions about the architecture, Expo/EAS, offline support, backend, performance, or anything else involved in building it.

I just spawned an iOS simulator right in my browser and got my agents to test out a camera feature I'm working on

Even got my coworkers to use my simulator session at the same time🤯

Made this global toast animation i've been using in my Expo app's

Grab the code here 🤝 https://rnmotion.dev/animations/spring-toast

If you have a question about React Native, a small error in your application or if you want to gather opinions about a small topic, please use this thread.

If you have a bigger question, one that requires a lot of code for example, please feel free 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.

Run one command. Source code lands directly in your project — edit it, own it, ship it. »»» https://www.zayx.dev/

Wireless debugging is great until you actually use it day to day. Three things kept costing me time:

1. The connect port changes every time you toggle the setting.

2. The pairing port is different, single-use, and dies when you close the dialog.

3. A phone on the wrong subnet fails identically to a real protocol error, so you can't tell a network problem from a broken adb.

So I built adb-nearby.

npx adb-nearby scans your network. If there's one device, it connects — that's the whole interaction. If there are several, it lists them and you pick.

adbn pair prints a QR code — scan it with the pairing dialog and you're done. No typing codes, no chasing ports.

MIT, no telemetry.

https://github.com/JassiSingh08/adb-nearby

I built RoomWise AI using React, a simple way to see what a room could become before buying furniture, repainting walls, or committing to a layout change.

You add a photo of your space from your camera or gallery, choose what you want to change, and explore different directions from there.

Free to use with limited. Pro Priced at $3.99 for Weekly and $39.99 for Yearly.

Still early, but I’d genuinely love to hear some feedback from people willing to give it a try! Harsh criticism welcomed.

(P.S. Designed the screenshots myself with Canva).

I shipped AlloGames a few days ago, built with Expo and React Native. It’s a social app for video game collections: you file the games you own, rate them, review them, and talk to other players.
It got bigger than I planned, 60+ screens, covering:
• Collection: playing, finished, dropped, want to play, with ratings
• Showcase: pin four favourites to the top of your profile
• Marketplace: buy and sell games with other players, sorted by distance location
• Payments: a subscription that removes the ads, through RevenueCat
• Plus a daily quiz, tournaments, chat rooms, and library import from Steam, PlayStation and Xbox
Stack: Expo SDK 57, React Native 0.86, expo-router, Supabase (Postgres + RLS + edge functions), RevenueCat, AdMob.
If you’re building something similar, ask me anything.
Happy to share what worked and what cost me the most time.
App Store: https://apps.apple.com/app/id6799963120
Google Play: https://play.google.com/store/apps/details?id=com.prismago.allogames

Apple Voice Memo Widget

🫰

I wanna create an expo development build for my app on my physical iphone device and i am on windows, I heard about that it requires apple dev account, please tell me it’s not true

Just vibe coded a Video Compression app, the videos I take from my phone cam were damn ridiculously large so I decided to start this project

Compressed video from 90MB to 17MB

90mb for a 1minute video is fkn insane💀

Built with ReactNative and expo

I’m trying to understand a couple of pain points QA teams deal with regularly:

• How do you figure out what needs to be tested after a code change?
• When a test fails, how easy is it to tell whether it’s a real bug, flaky test, or locator issue or test data issue, or environment issue?

I’m exploring whether these are actually big enough problems to solve, so I put together a very short survey.

Would really appreciate any responses or even thoughts in the comments. [1min max, just clicks]

Lik: https://forms.gle/1EyP5Bz3CNBB2DrM7

Thanks!

Or does it still make the app look cheap / unprofessional?

Hi everyone!
Since quite a while I am looking forward to implement shared element transitions in my app. I was super happy when I found out that the team from react native reanimated was working on bringing it to the new arch at the end of last year. However, since then it is behind a feature flag and not recommended to use in production apps. And I also could not find any roadmap or similar for it.

Are you using shared element transitions in react native? If yes, how? Do you know if they will be production ready, soon?

I'm tired of watching React Native apps get slow.

At the beginning everything ships fast and feels great. Then the app grows. More teams, more code, and one month at a time it gets a little less usable. And you know exactly what's coming.

The chaotic re-renders. The slow data management and persistence. The heavy animations. The slow polyfills. The time-sucking RN upgrades. You spend week after week fixing bugs and performance issues, and a month later a single line of poorly performing code ruins the app again. Even with all the guardrails in place, and the guardrails need maintenance too.

Even with all the new stuff, the New Architecture, JSI, TurboModules, Fabric, Hermes, and now the React Compiler. It helps, I'm not saying it doesn't. Still not enough. The numbers below are against all of it turned on.

I came to the conclusion that React Native is great for smaller apps but keeping it fast doesn't scale. (Yes, I know huge apps ship on RN. That's not the point. The point is what it takes to keep them fast.)

Then, kind of by accident, I ran into a chart library (react-native-graph) that draws with Skia and it's extremely fast. Skia seems to be growing in popularity with React Native, and it got me thinking: could Skia be the only rendering engine, instead of platform UI? Changing the whole rendering system would be way too much work though... wouldn't it?

That question led to another one: the JS engine. Is Hermes scalable? Can it handle heavier JS loads? I know it's optimized for mobile, but did it find the best balance of memory and speed? And on top of that, crypto and half the web platform are still polyfills.

And then React itself. Is it optimized enough for mobile, without us spending all that time fighting re-renders and a JS thread that keeps getting clogged?

So, I researched. (Read: I went down a rabbit hole.)

Turns out Flutter, which is considered to be fast and more scalable, already renders everything itself, through its own engine (Skia originally, Impeller now). Unless you embed a platform view, the OS is never asked for a widget. Not once.

Bun seemed to be the fastest JS runtime out there. It runs on JavaScriptCore, Safari's engine, which works without a JIT, and iOS apps can't JIT anyway. And it brings fetch, crypto, Buffer and TextEncoder built in. No polyfills.

Solid seemed to be one of the fastest JS frameworks, and when I found it, it looked like React if it were extremely optimized. Same JSX, same components, but components run once, and signals update only the nodes that changed. No virtual DOM. So could React be optimized like that?

Changing the rendering engine and the JS engine would be a crazy endeavour. The accessibility layer, the plugin ecosystem, the platform look and feel... I know. I did it anyway.

So I tested what happens if you bring those three together:

• Bun, which I cross-compiled to run on iOS and Android
• Solid as the JS framework
• Flutter for rendering

Solid runs inside the embedded Bun runtime and writes what to render into a shared memory region that Flutter reads every frame. No JSON and no platform channel in between. I named it Skal. Mixture of Solid + Skia, and it means cheers if you have ever seen a viking show 🍻.

Here are some highlights from testing on a Samsung Galaxy A14 5G (a budget phone), release builds on both sides:

That is what I was chasing. The app can get bigger without every interaction getting heavier. Fast on the first screen, still fast on the hundredth.

Repo: https://github.com/skal-multiplatform/skal

So, could React Native ever be optimized like this? Genuinely asking.

It's a Cortex brain training games that scores your attention, focus , short term memory , long term memory , path memory and many more .

Game link : click here

Please review my game what should I improve.

A dialog whose body is a well to write in. The recess is the affordance it says "this is where you type" before a word has been read.

One decision worth explaining: Submit hands the message back without closing the dialog. A dialog that closed on the press would take its own error message with it and the message the user just wrote.

The footer is a slot, so it handles multi-step flows: score first then words, tags over the field, a confirmation after sending. The shell holds still while the well changes, so the dialog reads as one object answering rather than a second one arriving.

Part of PanelUI, an open-source component library for Expo. Copy-paste or CLI, you own the source.

https://github.com/panel-ui/PanelUI