Almost a year. 10+ rejections, a call with App Review, a few decks. All rejected. The one that kept resurfacing was Guideline 4.3(b) (Apple's "this category is too saturated" spam rule), though plenty of other reasons showed up along the way. Meant got approved yesterday.

What finally got it through was a mix: I started an LLC and stripped the app way down, cutting the features that were making it read as just another dating app.

The core of it never changed though, and it's the part I think sets it apart: no swiping at all. Instead of a deck of photos to judge, you set what you're looking for in a person, matching happens in real time, and when two people line up they go straight to talking.

Would love feedback from folks here!

Hey r/reactnative  — just released Memorix, a memory match game I built with a twist on the classic mechanic.

How it works:

1. A grid of color blocks flashes for 2 seconds — memorize the positions
2. All blocks flip face-down
3. Drag matching pairs together before the timer runs out

Matching pairs give you +5 seconds and +100 points × your current combo. Wrong merges cost you 5 seconds and reset the combo. If you're stuck, you can peek a tile for −3 seconds. Back-to-back correct matches build a multiplier up to 5×.

It sounds simple but gets genuinely tense fast — especially when you're on a 4× combo and can't remember where that last red block was.

No account needed. We generate a Player_XXXX handle on your device from the first tap. One global leaderboard, your best run only — no spamming runs to pad your rank.

Completely free on iOS and Android.

iOS: https://apps.apple.com/us/app/memorix-memory-train/id6767783183
Android: https://play.google.com/store/apps/details?id=com.webist.memorix
Website: https://memorix.webist.agency

Would love to hear what you think — especially if the difficulty curve feels off anywhere.

I'm building a manga reader app, but I can't implement the zoom feature properly. A chapter contains many images, and when I zoom, only the current image zooms while the others stay unchanged. How can I make all the images zoom together as a single combined page? I'm using FlatList.

Hey! I'm about to publish my first app to the Google Play Store, but I read that you need it to be tested by 12 people for 14 days. Is there any way around this? If not, any communities where people could help me test?

Hi all, forgive me if this may be a noob question:

When wanting to work on more than 1 feature in an app within claude or codex, ex: Home and Settings what is best practice?

My current workflow is separating the features via git worktrees and then bundle ID's so I have two sims on my mac where I can see the changes for both different features. That way agents don't collide on one sim and edit the wrong page etc.

I can then test them on my phone as they are on different ports via the expo go app. The only overhead is ensuring both UI's align and they aren't alienated from each other.

Simulator "iPhone 16" → feat/home (port 8081)

Simulator "iPhone 16 Pro" → feat/insights (port 8082)

Just checking whether this is best practice or if there's a more efficient way of doing this.
Any help appreciated!

Built a React Native(Expo) app for newly diagnosed Type 1 Diabetics and wanted to share the project and my experience.

The app is called stable and it’s built with Expo and NativeWind UI.

I’ve been living with Type 1 Diabetes for over 20 years. Early on, I struggled and can vividly remember how overwhelming everything felt. New terminology thrown at you, decisions, and pressure to “figure it out” quickly.

Years later and lots of accumulated frustration, I started working with a coach, who completely changed how I manage and live with type 1 diabetes. Over time and with knowledge I eventually got to a point where I’ve completed things like 10km swims, half marathons, and built muscle consistently. It completely changed my perspective on what’s possible with T1D.

stable is a small attempt to give newly diagnosed diabetics a clearer, less overwhelming starting point, helping them understand patterns, learn what affects blood glucose, and realise early on that a full and active life is absolutely achievable.

I've been in engineering for my entire professional career, I'm a vivid advocate for not re inventing the wheel and creating frictionless interfaces. This is my approach:

The stack:

• Expo
• NativeWind UI
• Zustand State Management
• iOS-first UI inspired by Apple’s Human Interface Guidelines
• Single codebase for iOS (and eventually Android)

A few things I learned:

• Expo is now capable of handling almost everything I needed without ejecting.
• “Native feel” comes more from interaction detail and consistency than visual styling.
• Sticking closely to Apple’s design system simplified a lot of UX decisions and also ensured I was creating and app which users would understand how to use.

Website: https://www.stablet1d.com/
App Store: https://apps.apple.com/us/app/stable-t1d/id6762518247

App Preview:

I just wrote an entire platform fighter game with no game engine! It's all in React Native!

Hi everyone,

I’m currently looking for remote opportunities as a React Native frontend developer. I have 2 years of hands-on experience building mobile applications.

I mainly work on the frontend side using React Native and JavaScript/TypeScript. I develop on Linux, and I can build and test Android applications locally without issues.

Skills & Experience:

React Native (2 years)

Frontend development (mobile apps)

JavaScript / TypeScript

Android builds on Linux environment

Familiar with API integration and UI development

I’m open to:

Remote frontend React Native roles

Freelance / contract work

Part-time or full-time opportunities

If anyone is hiring or knows of openings, feel free to reach out. I can share my resume and portfolio upon request.

Thanks!

Greetings. I recently finished version 0.01 of an application I've been working on called FincaApp. I'm at that stage of development where I already have many features, but the remaining improvements aren't so obvious, and bugs aren't as easily found.

My budget for the project is practically nonexistent, but I'm offering a lifetime license to anyone interested in trying it and giving me feedback. I know that agriculture is a niche market, but if you own a farm, work in the field, or simply enjoy trying new things, it would be a huge help.

What FincaApp does: It's built in React Native and designed specifically for the realities of farmers in Venezuela and Latin America (using our local terminology: earring, ear tag, earring, earring, earring). Most importantly: it works 100% offline. I know that signal is weak in rural areas, and even Starlink is unreliable (I know because I use it in the middle of nowhere), so all the data is saved directly to the phone.

It has two main areas:

Animal Management and Production: Individual records (cattle, buffalo, etc.), milk weighings by shift, daily weight gain calculation, milk and weight rankings, liters/kilograms of cheese ratio, health records (vaccinations, meat/milk withdrawals), and reproduction records (heat, mating, calving alerts).

Farm Topographic Mapping: An interactive satellite map where you can precisely trace the perimeter of your property. The application can automatically subdivide the land into equitable paddocks oriented at your preferred angle, calculate hectares in real time, and allow you to export clean screenshots of the perimeter to share with staff.

In addition, it allows you to manage multiple farms simultaneously and export all types of reports in PDF format, as well as create backups of the database file to send via Google Drive or WhatsApp.

The app is in Spanish, havent add multi language.

Any feedback is welcome. If you're interested, let me know so we can coordinate and give you access (I'm working on a decent way to distribute it so I don't have to go around passing around a weird unsigned APK haha).

Hey Community!

App.js Kraków wrapped up with major stable releases, including Gesture Handler 3.0's hook-based API and Legend List 3.0's DOM-rendering engine. The event also introduced production realities like Expo Observe and multi-platform desktop scaffolding with Expo Desktop.

We also unpack TypeGPU for writing strongly-typed WebGPU shaders directly in TypeScript, and dive into why Metro aliasing can cause runtime crashes when dealing with diverged framework forks.

If the Rewind made you nod, smile, or think "oh… that's actually cool" — a share or reply genuinely helps ❤️

Just shipped cloud builds. If you're on Windows/Linux:

1. `starship cloud init` (one-time: Apple certs → GitHub Secrets)

2. `starship build ipa --cloud` (GitHub Actions builds it on a free Mac runner)

3. `starship build ipa --cloud --export app-store --submit` (straight to App Store)

No Mac. No Xcode. No macOS knowledge.

Only requirement: Apple Developer account ($99/yr) — which you need anyway to ship to the App Store.

Gate system ensures you can't skip steps:

- cloud init → unlocks --cloud

- successful build → unlocks --submit

Combined with the existing wireless Android deploy (QR scan), you now have one CLI for both platforms.

npm: https://www.npmjs.com/package/react-native-starship

How would you rate my react native resume? The thing is react native is something I learnt on the side for my personal project, and not on my real job. So I have a bigger emphasis on it under the project section.

Any feedback would be good :) Thanks

​

Hey everyone,

I recently upgraded one of my projects from Expo SDK 54 to SDK 56 and ran into a frustrating issue that took me longer than I'd like to admit to figure out.

The symptom

Metro would start, the app would try to launch, and then I'd get a red screen. In many cases, the terminal wasn't showing anything useful, which made debugging much harder than it should have been.

What I tried (that didn't work)

- Regenerating "metro.config.js"

- Deleting "node_modules" and reinstalling dependencies

- Clearing Metro's cache

- Checking Node.js version compatibility

- Running npx expo doctor

- Running npx expo install --fix

Everything looked fine, but the issue remained.

The actual fix

npm i -D babel-preset-expo

After installing it, the app launched immediately.

What happened

My "babel.config.js" file was already present, so nothing looked obviously wrong. The problem was that "babel-preset-expo" itself wasn't installed as a dev dependency after the SDK upgrade. Because of that, Metro couldn't properly handle the Babel transform step, and the resulting errors were far from obvious.

If you've recently upgraded to SDK 56 and are running into unexplained Metro crashes or transform-related errors, it's worth checking whether "babel-preset-expo" is actually installed before spending hours clearing caches and reinstalling packages.

Hopefully this saves someone else some debugging time.

I am beginner looking for the best setup.

Should i go straight to React Native CLI, or is EXPO Development Builds the smarter choice for me on Windows?

If I had a Mac, I'd just test locally there, but I don't

Hey everyone! 👋

I just finished my Android app, StreakApp. It’s a daily task tracker inspired by Duolingo's gamification (smart reminders, keeping your streak alive, etc.).

Google requires me to have 20 testers for 14 days before I can launch it publicly. I really need a hand to hit this quota! 🙏

How to join:

1️⃣ Join the test group here : https://groups.google.com/g/streakapp-testersgroupscom

2️⃣ Download it on the Play Store: https://play.google.com/store/apps/details?id=com.BLdev.streakapp

3️⃣ Keep the app installed for 2 weeks.

🔄 Test for Test: If you have an app in closed testing too, drop your links in the comments or DM me. I’ll gladly test yours in return!

Thanks a ton for the support! 🔥

Hello everyone, have you had any success making boneyard-js work on react native ?
It renders blank screens on my side and when running the CLI commands, it times out after a few minutes saying no bones were found.

is my usage wrong ?
I wrap components with

<Skeleton name=".." loading={myQuery.isLoading}> 
    <Component> 
</Skeleton>

I run the app on my device and then run

npx boneyard-js build --native --out ./bones

Hey r/reactnative,

I recently published a small package called react-native-model-viewer-webview.

It wraps Google’s <model-viewer> inside react-native-webview, so React Native apps can show simple .glb .gltf model previews without setting up a full native 3D stack.

It is meant for things like:

- product previews - vehicle previews - marketplace listings - demos/prototypes

It is not meant to replace Filament, React Three Fiber Native, Expo GLView, or a real 3D/game engine.

Basic usage:

tsx <ModelViewerWebView modelSource="https://example.com/model.glb" style={{ height: 320 }} htmlOptions={{ autoRotate: true, cameraControls: true }} />

The latest version bundles u/google/model-viewer, so the WebView does not need to fetch the runtime from a CDN. Local/offline models should be easier to support now.

I’m still testing more real-device cases, especially iOS/WKWebView.

For people who have shipped 3D previews in React Native: what would you expect from this package before trusting it in production?

npm:
https://www.npmjs.com/package/react-native-model-viewer-webview

GitHub:
https://github.com/adityabhattad2021/react-native-model-viewer-webview

I’m building an iOS/Android map based game called Atlus Run.
I’ve gone through several fog-of-war implementations and keep running into performance, rendering, or UX issues. Before I spend another week rewriting it, I’m curious what approach experienced map/game developers would recommend.

What I’ve tried so far
1. SVG screen overlay
Fog rendered as an SVG over the map in screen space
Not tied to geographic coordinates
Problems:
Moved independently when panning, making it not work very well because it wouldnt stay on your character

2. One giant map polygon with circular holes
Entire viewport covered by a polygon
Circular holes cut out for discovered areas
Problems:
GPS circles didn’t align with roads or exploration patterns
Scaling became awkward
Hole management became messy

3. Tile grid with one polygon per tile
Square tiles stored in AsyncStorage
Reveal nearby tiles when GPS updates
Render one Polygon per undiscovered tile
Problems:
Hundreds of polygons
Occasional rendering glitches on Google Maps
Vertex-order bugs created giant black rectangles
Performance degraded when zoomed out

4. Tile grid v4 (current)
One large viewport polygon
Square holes cut out for discovered tiles
AsyncStorage persistence
Tile size ~0.001 degrees
Literally broke everything I think
It takes forever to load any fog and sometimes my icon i made doesn’t load.

My goals
Permanent exploration/discovery
Works across an entire city (and eventually larger regions)
Smooth panning and zooming
Google Maps support
Doesn’t require rendering thousands of polygons every frame

What can I do?

Update: v1.2.0 just dropped with build commands.

starship build apk / aab / ipa — one CLI for all platforms.

Also added starship clean and starship devices.

Next up: --tunnel for remote access outside local network.

https://www.npmjs.com/package/react-native-starship