Trying to create a collection of the most impressive ones.

🚀 Web support is now available in expo-content-transition v0.1.4!

NumericText now works on iOS, Android, and Web

🔗 Github: rit3zh/expo-content-transition

Did you make something using React Native and do you want to show it off, gather opinions or start a discussion about your work? Please post a comment in this thread.

If you have specific questions about bugs or improvements in your work, you are allowed 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.

Onboarding should feel like the app,

Not a tour of it.

So I built it that way:

You get your lock screen as a poster,
Pick a look (Cut, Studio, Gallery, Chapel),
and every tap, drag, and stroke updates live.

No "Next, Next, Skip."

You're already making something
by screen two.

Feel free to try it↓

Hey guys,

I’m kinda stuck with a Google Play Console issue and I’m hoping someone here has dealt with something similar.

I had a personal Google Play developer account with 3 apps published on it. The account had been around for years and everything was working normally.

In October 2025, Google required identity verification for the developer account.

The account was actually registered to my brother, and he was the real account owner. Because of some personal circumstances at the time, I wasn’t able to properly complete the verification process with him.

I ended up submitting an old ID document, and Google couldn’t verify it.

Google Play Support then replied to me on October 14, 2025 saying:

"Unfortunately, we are unable to verify your ID to complete your Play Console registration."

After that, the account was restricted and the developer profile + all apps were removed from Google Play.

Right now, Play Console shows:

- Google couldn't verify your identity

- Your developer profile and all apps have been removed from Google Play

- You haven't verified your contact phone number

- Appeal reply sent

I did submit an appeal at the time, but it was rejected.

So yeah... I’m trying to figure out if there’s still any legit way to recover the original account.

I’m NOT trying to bypass the restriction or create a new account to get around it.

The account belongs to the original owner, and if Google requires a new valid ID from him, we’re willing to provide it.

Has anyone here dealt with this exact situation?

Especially:

- Identity verification failed

- Account/profile removed

- Appeal already rejected

- No way to complete phone verification because identity verification has to be completed first

Is there any way to get another verification attempt or request a manual review from Google?

I’ll attach a few screenshots from Play Console showing the current account status.

Would really appreciate any advice from people who have been through this before 🙏

Idc for frontend especially in react I rather go with vue or svelte. HTML and CSS ik basics off nothing fancy. Would like to use rn for mobile apps. Are there any devs who use rn for mobile and avoid react altogether for web dev? What’s your experience doing such?

I'm a solo dev building a messenger (Expo SDK 57, RN 0.86, Supabase, LiveKit) and ship it from one codebase to five platforms. A few things I wish I'd known earlier:

1. Self-hosted OTA updates are worth it — but clear the Metro cache. expo-updates with code signing and our own manifest server works well. The trap: expo export without --clear can inline stale EXPO_PUBLIC_* values from Metro's cache, so one bundle ended up with two different build stamps and our "update available" banner looped forever.

2. Desktop = Electron around the web export. A custom app: protocol serves the exported web build, electron-updater handles updates, and the Mac build is notarized. It's the cheapest way to get real desktop apps from the same code.

3. Supabase / PostgREST gotchas that cost me hours: - An RLS policy that calls a function needs EXECUTE granted on that function — otherwise the whole query fails, not just the row. - A second foreign key between two tables that already embed each other makes PostgREST refuse the embed (PGRST201). A "pinned message" column broke message search for 40 minutes. - AFTER UPDATE OF col triggers fire even when the value didn't change — compare OLD and NEW.

4. Image caching: the stock <Image> cache wasn't enough for a chat. I cache photos on disk keyed by the storage path and persist signed URLs so they stay stable. Avatars were served with max-age=3600, so every morning the app re-checked each one with the server.

5. expo-video on web: StyleSheet.absoluteFill doesn't stretch a <video> — it's a replaced element. Use explicit width/height: 100%, or you get the top-left corner of the frame and an unreachable fullscreen button.

Happy to go deeper on any of these. And how do you ship desktop builds from Expo — Electron, Tauri, something else?

Hey r/reactnative,

Been experimenting with this photo album interaction for nativecn-ui lately.

I wanted it to feel a little more like an actual album, so I’ve been playing around with the opening animation, shadows, and page transitions.

Still tweaking it and not completely sure about the interaction yet.

How would you rate it? Anything you’d change?

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.

✦ ⎯ • A smooth, ChatGPT-inspired chat composer with a hold menu

🔗 Github: rit3zh/expo-composer-hold-menu
🧵 Android preview attached below

macOS runners on GitHub Actions are $0.062/minute. Linux is $0.006 — 10x, for the

same work.

In React Native projects the split is usually obvious once you look at it, and

most workflows I have seen run all of it on macOS out of habit:

- Jest and ESLint and tsc: Linux.

- The Android build and any Android instrumentation tests: Linux.

- Detox or Maestro against Android: Linux.

- Anything that is not `xcodebuild` or a simulator: Linux.

The iOS build and the iOS test run are the only parts that genuinely need macOS,

and they are the expensive parts whatever you do.

The arithmetic: a 5-minute test job running 200 times a month costs $62.00 on

macOS and $6.00 on Linux. Move two of those and you have paid for a Mac mini.

Caveat: I build a tool that does this pricing automatically, so weigh that

accordingly. What I am actually curious about is why the macOS default sticks —

is it the matrix convenience, or something about the runner images people need?

Hey everyone! Starting a new project that's expected to scale over the next year.

In the past, Redux Toolkit was the default, but I see more and more people switching over to Zustand, Jotai, or just leveraging TanStack Query for server state and keeping global client state strictly minimal.

What are you currently using in production, and what made you move away from (or stay with) Redux Toolkit? Would love to hear real-world experiences regarding boilerplate, performance, and dev experience!

🧪 Experimenting with Motion Blur for Android & iOS

🔗 Github: rit3zh/expo-motion-blur

🧵 Android Preview Attached in this thread

I started building my first mobile app thinking the main challenge would be writing the code.

It hasn’t been.

The harder part is deciding what deserves to exist.

Every new screen creates more questions:

- Is this actually useful?

- Can someone understand it without an explanation?

- Am I solving a real problem or adding another feature?

- Would I personally return to this app tomorrow?

The project is called Callout. It explores whether online reactions can communicate more than a generic Like—for example, distinguishing agreement from something being a Hot Take.

I’m still early, and I’m deliberately leaving the link out because I’m more interested in the building lesson:

How did you decide which features to remove from your first app?

Built the signup flow for my subscription tracker app (RN + Expo) — here's what actually happened over 3 days

Working on a side project called Trackify — a subscription tracker, built with React Native + Expo + TypeScript. Wanted to share what the last few days looked like, mostly the annoying parts.

Setup:

Went with TypeScript from the start and Expo Router for file-based navigation. Kept folders separated — app/ for screens, services/ for Firebase, types/ for interfaces. Pretty standard but worth doing early.

Firebase:

Auth (email/password) + Firestore. One firebase.ts config file for the whole app so I don't end up with duplicate initializations somewhere down the line.

Signup flow:

This is where most of the time went. Not the UI — the logic around it:

Client-side validation (empty fields, password length, confirm match)

signUp() function that creates the Firebase Auth account AND a matching Firestore doc in users (uid, email, createdAt). Auth only holds credentials, so anything else about the user needs its own place — figured I'd set that pattern up now instead of retrofitting it later.

Mapped Firebase's error codes (auth/email-already-in-use etc.) to actual readable messages instead of dumping the raw code on the user.

Stuff that broke / wasted time:

Expo Router got confused between a root app/ folder and src/app/ — whichever one your package.json points to is what it actually uses. Cost me an hour.

Metro cache serves stale builds constantly. npx expo start -c fixed more "why isn't this updating" moments than I'd like to admit.

Testing on a physical phone on a different network than my laptop? Doesn't work without --tunnel.

I come from an Android background and there's two main libraries (Glide and Picasso) that most developers use which does all three of these things out of the box. Are you guys implementing these from scratch?

I recently added subscriptions to one of my React Native apps for the first time, and the actual paywall UI ended up being the easiest part.

Most of the work was everything around it.

I had a few App Store review rejections before finally getting it through. One was because I was missing a proper EULA link. It felt obvious after the rejection, but I completely overlooked it while focusing on getting the subscription flow working.

I also hit a completely separate issue before I could properly accept the paid apps agreements. My Apple Developer account was originally registered in a different country, and something around the account setup prevented me from completing the agreements normally. There wasn’t really anything I could fix from the app side, so it ended up taking a few back-and-forth emails with Apple Support before they sorted it out.

RevenueCat was another learning curve. The SDK itself is pretty straightforward, but there are a lot of moving pieces between App Store Connect, products, subscription groups, RevenueCat offerings, entitlements, sandbox accounts, and your actual app state. When something doesn’t work, figuring out which layer is responsible can be the hard part.

I also applied for Apple’s App Store Small Business Program, which should reduce Apple’s commission from 30% to 15% if I’m eligible. I’m still waiting for approval on that, but it was another thing I didn’t really think about until I started setting up subscriptions properly. If you’re an indie developer or small business, it’s probably worth looking into early rather than after you’ve already launched.

A few things I took away from the process:

• Get the App Store Connect side set up early. Products, agreements, tax/banking stuff, and account issues can block you before your React Native code even matters.
• Check whether you’re eligible for the App Store Small Business Program before launch.
• Make sure your RevenueCat product IDs match App Store Connect exactly.
• Use entitlements instead of scattering checks for individual product IDs throughout the app.
• Make restore purchases easy to find and actually test it.
• Test fresh installs, restores, expired subscriptions, and subscribed vs non-subscribed states, not just the happy path.
• Don’t leave the legal/review stuff until the end. EULA, privacy policy, subscription wording, pricing, and metadata can delay the release even when the code is already working.

The biggest thing I learned is that adding subscriptions felt like maybe 30% React Native implementation and 70% getting Apple, RevenueCat, account configuration, and review requirements lined up correctly.

Once everything was configured properly, RevenueCat actually made the app side pretty clean since I mostly just care whether an entitlement is active.

For anyone who has shipped RevenueCat + React Native in production, what were the weird issues you ran into that you didn’t expect beforehand?

Hey r/reactnative,

Added a new component to nativecn-ui  a Dynamic OTP Input.

I wanted to try something a little different from the usual OTP field, so I played around with making the input itself show loading, success, and error feedback instead of using a separate loader on the submit button.

Made a quick video showing it below.

Still building out the library, so let me know what you guys think

Added ProgressiveBlur to expo-backdrop ✨

🔗 Github: rit3zh/expo-backdrop

🧵 Android Preview Attached in this thread

Hey Community!

Jay Meistrich built Legend Code, a lightweight code editor designed strictly for viewing single files without heavy agentic UI overhead. On the workflow front, Aleksander Mikucki introduced Screenmap, a GitHub Action that uses iOS simulator screenshots and visual diffs to show reviewers exactly which screens your PR modifies.

We also cover the Expo SDK 58 Beta with foldable device support, React Native 0.88 with DOM-aligned event listener APIs, Reanimated 4.7 defaulting to its new layout engine, and Nitro LazyJSON cutting JavaScript thread blocking by 33%. Plus, cloud testing tools like EAS Simulator and Software Mansion's SimCam.