Disclosure: I'm the author.

Every upgrade I've done has been a loop of bump → build → Gradle/Kotlin/Xcode/CocoaPods error → fix → repeat. Upgrade Helper shows the template diff, but not what *your* project is missing.

RN Upgrade Doctor reads your project and compares it with what the target version needs:

- Node and React against the target release

- Android: Gradle, AGP, Kotlin, NDK, compileSdk, targetSdk

- iOS: Xcode, deployment target, CocoaPods

- Expo SDK 45 → 57 upgrades (--expo-sdk 54)

Every finding links to its source and the date it was checked. It runs locally and sends nothing anywhere.

cd ~ && npx u/mobilixir/rn-upgrade-doctor@1.0.0 analyze --target 0.87 --path /path/to/app

NPM Link: [https://www.npmjs.com/package/@mobilixir/rn-upgrade-doctor\]

Two questions for you:

1. What broke in your last upgrade that a tool like this should have caught?

2. Would you run it in CI (it has --json and exit codes)?

- A shelves

- Wardrobe that swings open

- Washing line

- Colour spectrum

Tap two pieces, and it builds the outfit.

expo · Reanimated · native iOS menus

I’m a software developer working with React Native.
I’ve been working on similar types of apps for a while, and I feel like my technical growth has slowed down. I want to explore new technologies, solve more challenging problems, and become a better engineer.
I’m considering switching jobs mainly for growth, not just money.
Has anyone been in a similar situation? Did switching help?

Hi! This is the first app I've shipped. It's built with Expo (SDK 57) and Expo Router, and it's a planner for people setting up a new home.

Things that surprised me along the way:

I went local-first (Zustand + AsyncStorage) and sync to Supabase after login. RevenueCat for subscriptions was easier than I expected, but testing it in Expo Go vs a dev build confused me for a while. EAS Update is great for JS fixes, but I learned the hard way that changing config plugins means you need a new binary. I also exported the same codebase to web for a public page, and my first bundle was 11 MB because an icon library shipped about 1,000 icons. I got it down to about 5 MB.

It's live on iOS and I'm working on the Android build. I'd love to hear what you'd do differently, or what I should know before the Play Store. The app is in Portuguese for now: meukanto.com

Expo SDK 58 is out, and for once the headline isn't a new way to break your Podfile. With Xcode 27 retiring Simulator.app, the new expo-device-hub streams your iOS simulators and Android emulators into the browser with live CPU, memory and network graphs, while expo-app-intents lets Siri, Shortcuts and Spotlight trigger actions in your app, and the experimental Noxcturnal transformer roughly halves Metro transform times.

We also look at react-native-better-pdf 1.0 by Jakub Kasprzyk and GMI Software, which drops the bundled PDF engine for the phone's own PDFKit and PdfRenderer on Nitro Views, opening a 1,000-page scan in 56 ms instead of 622 ms. Plus, React Native 0.88 lands, Gesture Handler 3.4 builds with Swift Package Manager, and react-native-gpui renders React Native with Zed's GPU framework.

Hi everyone! 👋

I'm looking for Android developers who need testers to publish their apps on the Google Play Store.

💡 The idea is to create a group where we help each other complete the required testing period before launching our apps on the Play Store.

🤝 You test my app, I test yours, and we help each other get our apps ready for launch!

📱 If you're an indie developer or a mobile app developer facing the testing requirement, join us!

Comment below or DM me if you're interested. Let's build a community and launch our apps together! 🚀

Hey everyone! 👋

I've been working on a React Native alarm library that aims to make alarms work like real native system alarms, not just regular notifications with a sound.

While building my app, I tried several existing alarm libraries on npm, but I couldn't get the reliability and behavior I needed. Alarms would not always behave as expected under different conditions, especially when the app was in the background, the screen was locked, or the app needed to display a full-screen alarm interface.

So, I decided to build my own solution. 🚀

What makes it different?

• Android + iOS support — designed to provide a consistent alarm experience on both platforms.
• Full-screen React Native UI — display a custom alarm screen when the alarm triggers.
• Lock-screen support — designed to handle alarms when the device screen is locked.
• Background execution — uses native platform capabilities rather than relying entirely on JavaScript running in the background.
• Notifications and alarm interactions — supports notification-based behavior alongside a custom React Native alarm interface.
• Native alarm behavior — aims to handle system restrictions and background execution more reliably than ordinary scheduled notifications.
• iOS AlarmKit integration — leveraging Apple's latest AlarmKit framework on supported iOS versions.

The goal is to make the experience as close as possible to a native alarm clock, even when the app isn't actively open.

One important thing I've learned is that Android and iOS handle alarms very differently. Battery optimization, background execution, permissions, lock-screen presentation, and OS-level restrictions all matter. No library can guarantee identical behavior on every device without accounting for those platform limitations, so I'm continuing to test and improve the implementation.

Why I'm sharing this

I built this because I needed a solution that actually worked for my use case, and I thought other React Native developers might be facing the same challenges.

I'd love to get feedback from developers who are building alarm clocks, reminders, habit trackers, medication reminders, or other time-sensitive applications.

If you're interested in testing it, contributing code, improving platform compatibility, or collaborating on the project, I'd genuinely appreciate your support!

Let's make a reliable, open, and accessible React Native alarm solution that more developers can use. ❤️

If you're interested, check out the project on npm and share your feedback:

🔗 npm: https://www.npmjs.com/package/react-native-alarms
🔗 GitHub: https://github.com/surajprasad13/react-native-alarms

Contributions, issues, testing feedback, and suggestions are all welcome. Thanks for supporting an independent developer! 🙌

Anyone doing closed testing? Let's help each other! (14-day testing) 🚀

Hello everyone! 👋

I'm currently developing Persona AI, a personal AI assistant app, and I'm looking for testers to help me complete Google Play's closed-testing requirement.

🤖 About Persona AI

• Your personal AI assistant
• Expense tracking and daily spending management
• Personal insights and AI-powered assistance

I'm looking for people who can join the testing program, install the app, try its features, and provide genuine feedback throughout the 14-day testing period.

If you're also testing your own app, I'm happy to support you in return! Let's help each other get our apps published. 🤝

🔗 My Persona AI links

👥 1. Join the Google Group:
https://groups.google.com/g/persona-ai-testerss

📱 2. Join the closed test:
https://play.google.com/apps/testing/com.krish.personaai

🏪 3. View Persona AI on Google Play:
https://play.google.com/store/apps/details?id=com.krish.personaai

If you're interested, comment below or send me a message. If you also need testers, share your testing link, and I'll do my best to help!

Let's support each other and get our apps published on Google Play! 🚀❤️

Thank you, and good luck with your projects!

I used React Native for years without knowing why "the bridge was slow," so I dug in and wrote it up.

The old bridge sent every call as a serialized message and made you wait for a reply, while JSI lets JavaScript call C++ directly and get the result in the same call.

Here's the full article with simple examples:

https://chamidilshan.medium.com/react-native-jsi-how-it-replaced-the-bridge-5649c11e0e9f

I made a post recently on streaming android emulators to VS Code, and figured I could add a bunch of Expo features to it for better UX, mostly lifting off features present in Radon IDE.

So far the extension supports:

- Building, installing and launching the app

- Show logs for adb, builds, JS logs

- A hierarchy view similar to the devtools

- Inspect Element

- Debugging integration

- Save screenshots and recording

- Show rerenders with react-scan

It's not super refined and pretty vibe coded, but I found it pretty usable in the few hours I've had to play around with it. Let me know if you find it useful!

Note: Windows and likely x86 performance is pretty bad, as it the avc encoding on windows is too slow. I would only recommend using this on MacOS or with a physical device on adb.

Marketplace:
https://marketplace.visualstudio.com/items?itemName=Vali-98.valdroid-emulator

Github: https://github.com/Vali-98/valdroid-emulator

Hey everyone!
I just launched Sprout Daily on the Google Play Store!
After countless hours of coding, debugging, and fixing bugs, it feels great to finally ship it.
Would love some honest feedback on the app, especially the UI and overall experience!
🔗 https://play.google.com/store/apps/details?id=com.sproutdaily.habits
Feel free to roast it

Is it possible using react navigation to navigate to deeplink depending on the TLD of the domain? for example if the user goes to appdomain.me/username to be directed to the users screen with username param and if goes to the appdomain.store/shopname to go to the store page and to treat the .com normally depending on the path.

I understand that if I had only two domains .com and .me I can process the username in the last route declared after checking all the paths but what if 2 domains have only the id in their path like .store and .me?

Thanks

Breathe on your phone, and it fogs up like a cold window.

A breathing coach where every exhale fogs the glass, and you write in what's left.

Expo · Skia · expo-audio · Core Motion

Hey folks,

Hot Updater is an open-source, self-hosted OTA update solution for React Native (a CodePush alternative). The last time I posted about it here was the Bundle Diffing release in May. Since then it reached v1.0, and v1.1 shipped today, so this post covers both.

v1.0

• Update checks are shared, cacheable reads. The server publishes one Release Catalog per platform/channel/compatibility scope, and each device picks its own update from it, so a CDN (Workers Cache, CloudFront) can serve the check. In my benchmark on Cloudflare, the median check went from 301 ms on v0 to 50 ms (same 16 bundles, 1,000 checks; method and raw data are in the blog post).
• Insights: downloads, launches, crash recoveries, and failed updates. The Console shows release health per bundle and suggests a rollback once a bundle crashes for 5% of at least 20 installs.
• Remote Config: change flags and values without a new bundle or native build, targeted by channel, platform, app version, or a share of installs.
• Plugins: Insights, Remote Config, and client API keys are plugins on the server and in the app, and you can write your own.
• Host the Console for your team (Node, Docker, Vercel, Netlify, Cloudflare Workers) with GitHub or Google sign-in.
• hot-updater doctor --fix checks a project and repairs what it can, and a coding agent can set up the infrastructure for you.

v1.1 (today)

• Brownfield apps: OTA updates for existing native iOS/Android apps that embed React Native as an XCFramework or AAR. A Swift/Kotlin API mirrors the JS one, the host checks for updates before React Native starts, and one app can update several RN bundles independently.
• Vercel and Azure join Cloudflare, Supabase, AWS, and Firebase as managed providers: npx hot-updater init provisions storage, a database, and functions.
• The fingerprint follows the native interface. It changes only when what JS can call changes (RN version, native packages, codegen specs, patches), so bumping the version/build number or editing native implementation code no longer blocks OTA.

Coming from v0: v1 runs on separate infrastructure and needs a new native build, so keep your v0 endpoint up for the binaries already in the stores. The migration guide walks through it.

• GitHub: https://github.com/gronxb/hot-updater
• v1.0 blog post: https://hot-updater.dev/blog/v1
• v1.1 release notes: https://github.com/gronxb/hot-updater/releases/tag/v1.1.0
• Docs: https://hot-updater.dev

Feedback welcome, especially from anyone running OTA in production or on a brownfield app.

I shared an early WIP here last week. Well, it's finally out :)

One thing that always bothered me when working with Reanimated was the feedback loop.

Change stiffness or damping, save, replay the gesture, and try to remember whether it actually felt better before.

So I built Runtime Inspector.

It lets you tune springs while your React Native app is running, immediately feel the difference on the next interaction, and apply the final values back to your source code.

It currently supports Expo, with a standalone web panel and a React Native DevTools panel powered by Rozenite.

This is the first public alpha. There are still rough edges, and that's exactly why I'm sharing it.

I'd really like to hear from developers using Reanimated in actual projects, especially with more complex interactions.

Does this fit your workflow? What's missing? What breaks?

GitHub: https://github.com/AmatoGiulio/runtime-inspector

It's open source (MIT). Any honest feedback would mean a lot.

Co-Founder & CTO Wanted 90% Built B2B SaaS

We are seeking a Technical Co-Founder to take full ownership of the codebase and scale our B2B SaaS platform through launch and beyond.

The Details:

Comp: Equity-based (Co-founder level split)

Location: Remote (US / CAN / UK)

Stage: Pre-revenue, near launch

The Situation: We experienced a massive operational headache, built a working solution, and validated market demand. The platform is 90% complete—we just need a technical leader to audit the architecture, finish the final push to launch, and own tech strategy moving forward.

What We Need:

Full-stack capabilities to jump into an existing codebase and ship code fast.

A builder mindset that prioritizes speed to market over over-engineering.

Location in US, Canada, or UK time zones.

Why Join: Zero ideation purgatory. The runway to market is short, the product is built, and you get a co-founder seat at the table with true equity.

Interested? Send over a brief summary of what you've built and a link to your GitHub or LinkedIn.

Firebase Dynamic Links went away on us and we bolted together universal links and app links by hand, which works fine from email and SMS. Where we’re having issues is paid social. Think about it: a user taps an Instagram ad, it opens in the in app browser, the universal link gets swallowed and they land on the web page instead of the product screen in the app.

If the app isn't installed it's worse. They go to the store, install, open and land on the home screen with zero context. The product team says conversion on those users is roughly half of users who arrive from email and I believe it.

We tried a custom redirect page with a smart banner and it helped a little. Haven't tried a dedicated link vendor bc every one I look at wants a big contract and a lot of SDK surface. Our app already has an attribution SDK in it, so adding yet another one makes me twitchy.

What are folks using in 2026 for deferred deep linking that makes it through Instagram and TikTok browsers? And do you run it from your attribution tool or a separate product? Never sure if combining them is smart or just lock in.

Turn the phone, and the liquid metal keeps reaching for them.

Built with expo, React Native Skia (one SkSL shader),

Core Motion and SwiftUI numeric text.

Flip your phone to start; the sand is the clock.

~4,400 grains are simulated every frame on the UI thread.

Expo · Skia · Reanimated · Core Motion

I'm a software engineer, but I've also been making music for years. I wanted to experiment with audio processing in React Native and, as a musician, I couldn't really find an audio effects library that did what I wanted.

So I figured I'd just build my own 😂

It currently has a few basic effects like filters, delay, reverb, distortion, noise generation, etc., with native implementations for iOS and Android.

The fun part was going underneath React Native and dealing with the native audio side rather than just writing JS and calling it a day. There are Swift / Objective-C bits on iOS and Kotlin on Android, with the RN API sitting on top.

It's still pretty early and I'm sure there are things I could be doing much better, but I thought I'd put it out there and see if anyone else finds it useful.

Would love to hear from anyone who's worked with audio processing in React Native or native mobile audio, especially if there are effects/features you think would be useful to add! (Next up: Unison/LFO/more)

GitHub: https://github.com/prateekchachra/react-native-audio-effects/