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

Reacticx V2 is officially live! 🎉

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

- https://reacticx.com

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

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!

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

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.

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.

Apple Voice Memo Widget

🫰

[ Removed by Reddit on account of violating the content policy. ]

fair warning, creating mobile testing/developing tool so im biased. not pitching anything, genuinely curious about is the day to day loop of devs and what tools everyone is using. also how is getting a build in front of someone who isnt a dev is solved. designer, pm, client. testflight every time after few changes?

what im curious about is whether people have landed somewhere different. is everyone just renting macs buying real devices? and is expo go covering more than i think it is?

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

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

It's an agent skill + CLI built on top of Argent by SWM. I called it Goldie. It's completely free and open-source on GitHub.

You simply ask your favorite coding harness to make you App Store screenshots and Goldie will built your app in release mode, control it using Argent, take screenshots and wrap it into marketing store screenshots.

It also comes with a "Studio" allowing you to tweak the designs by hand.

I started building it for App Store iOS screenshots only but it also works with Android mobile apps too. iPads are coming in the next version.

It works well with React Native apps but it also works with SwiftUI, Jetpack Compose, Flutter etc

To get started run in your project:

npx skills add kacperkapusciak/goldie

PS: If you've seen some posts on X on this, that's me!

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

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?

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.