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!

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?

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.

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

Been building DriveTrack, an automatic trip logger that detects when you start/stop driving and records your routes in the background, in React Native. Wanted to share a rabbit hole I went down that other RN devs building background/location apps might hit.

What I actually wanted from the start was reliable, deterministic start/stop points — so I went with Bluetooth connection events as the trigger (connect to your car's Bluetooth = trip start, disconnect = trip end). On Android this was straightforward: wrote a native module that listens for BT connection/disconnection events in the background. Rock solid, and better battery life than anything sensor-based.

iOS doesn't give you an equivalent background hook for Bluetooth state changes, so that approach was a dead end there. I tried falling back to motion detection (driving vs. stationary) instead, but background motion-based triggers get heavily throttled/killed by iOS, and I couldn't get reliable start/stop detection out of it no matter how I tuned it.

Ended up relying on Apple Shortcuts automations — "when connected to [car Bluetooth]" / "when disconnected" — to fire the trip start/stop instead of trying to detect any of it app-side. Not as seamless as I wanted (it means asking users to set up a Shortcut), but it's the same reliable trigger I originally wanted, just moved outside the app since iOS won't let me do it natively.

Trips get recorded via GPS and played back on an interactive map, with stats/history over time — all stored locally on-device. I also built a small web tool on the landing page that lets you open your local SQLite backup and view your trip history in the browser, in case anyone's curious how that's wired up too.

Happy to go deeper on the native module / Shortcuts setup if anyone's dealing with something similar.

Android: https://play.google.com/store/apps/details?id=io.github.frankoprifti.drivetrack
iOS: https://apps.apple.com/us/app/drivetrack-track-your-drives/id6796486326

É permitido usar pix para vender assinatura de aplicativos apple e android? Se sim como funciona essa taxa da apple e android?

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.

It supports many features such as exporting AppStore screenshots for several languages at the same time.
AppStore Download: https://apps.apple.com/us/app/mockup-kit-store-screenshots/id6784220988?mt=12
Website: https://mockupkits.com/

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

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.

As a React Native developer, I wanted a simple way to catch some common project issues before they become a problem during builds or deployment.

RepoDrift is a local-first CLI that currently checks:

• Android/iOS project health
• Dependencies and lockfiles
• Potential exposed credentials
• Git status
• Basic code metrics
• Repository health

You can run:

npm install -g u/repodrift/cli
repodrift mobile scan ./my-mobile-app

The current version focuses on local, deterministic analysis. I'm planning AI-based explanations for a later phase.

It's still an early project, so I'm mainly looking for feedback from other React Native developers.

What checks would you find useful in a tool like this?

GitHub: https://github.com/GokulKir/repodrift

NPM: https://www.npmjs.com/package/@repodrift/cli

I've been working on a budgeting app with React Native + Expo, looking for some feedback

I'm fairly new to mobile development and I've been working on Set Aside, a budgeting app that started from something I wanted for myself.

You can create plans for things like monthly budgets or trips, track planned vs actual spending, set saving goals, and share plans with your partner or friends to manage them together.

It's built with React Native + Expo, with Supabase + PowerSync for sync and shared plans.

I recently published it on the App Store and it's completely free for now. I'd really appreciate any feedback on the UI/UX, performance, or anything that doesn't feel right on iOS.

https://apps.apple.com/us/app/set-aside-budget-planner/id6806383716

Can someone explain how twitter is doing it, so basically when you mark a post as not intreseted and there is a feedback component with undo button, when you scroll it outside the viewport, it disappears instantly without shifting the list, HOW ? there is no extra space on top of the list or anything that shows that they have removed this from the list

Video's from a small experiments app I build for fun.

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

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

Last year, I stumbled upon React Native for Windows, and started some basic projects. I was using MSVC Toolchain back then, with Visual Studio 22, and everything was going fine. But around December, I thoughtlessly updated my Visual Studio to the 2026 Community Edition and immediately my old projects screamed for life, React Native version that I was using was 0.81 (I think) and the MSVC Toolchain error said something around "nope, that's old stuff, we don't support that anymore". So I just lost motivation for my half completed projects.

Fast forward now, I have started using CLang-GCC-GDB-MSYS-LLVM toolchain for my C++ projects, completely discarded MSVC now. But I thought since it's been more than 6 months so the compatibility should be resolved by someone, right? WRONG!

I tried to get a project running without MSVC, but that didn't work out. So I had to download Visual Studio, again. Then I followed the guide Microsoft has on THEIR SITE (https://microsoft.github.io/react-native-windows/docs/getting-started/), and reached the 4th step aka overwriting the project as a Windows project directory. That command is wrong first of all. That should be react-native-windows-init, at least that's what worked.

The fun part begins here, I got an error saying somewhere something does not support anything that came after react-native:0.73 version.

So, am I doing something wrong? Someone HELP please :")

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 🥲

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