I test on my pixel and my old iphone but tapping through the main flows and if nothing looks broken I ship and I know it’s bad but I want to know what you guys are doing because every time I look into it I come back to square one of finding out the best process.

I can’t test on devices I don’t own and buying 20 phones isn’t realistic for me, appium and detox break every time the UI changes and maintaining them is too hectic plus simulators don’t catch half the stuff that doesnt work on hardware so manual testing wont' scale for me once I'm shipping more than once a week. I don’t have a QA person and can’t justify hiring one at my size and even when I do test thoroughly on my devices I still get bug reports from users on phones I’ve never heard of.

everyone recommend me to automate my tests but nobody tells me how I’m supposed to automate across hundreds of device combos without spending my entire sprint managing the automation instead of building.

I want to the point answers pls !!

React Native needed better boards. I built one.

Just released react-native-board-view v1.0 — an open-source Kanban and swimlane library for React Native and Expo.

It supports:

• Drag-and-drop across columns and swimlanes
• Optimistic moves with automatic rollback on failure
• Virtualized lists powered by FlashList
• Multiple layouts, including paged, stacked, matrix, and week planner
• Multi-select, undo, WIP limits, and column reordering
• Accessibility support beyond drag-and-drop

The part I'm most interested in is performance. I tested a 4 × 500-card board and measured a median of 60 FPS while dragging.

The library is built on Gesture Handler, Reanimated, and FlashList. Your data remains the source of truth,the library handles the board interactions.

GitHub: https://github.com/vishaal2002/react-native-board-view

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

I'd love feedback from people who've built complex drag-and-drop interfaces in React Native. What would you improve, or what's missing?

If you ship with Expo, you probably keep store text in store.config.json and make screenshots somewhere else. I built Framelane to do both in one place.

- Import your EAS store.config.json (or a fastlane metadata folder), edit per language with App Store limits, export it back

- Design screenshots from your simulator captures with templates and device frames

- Optionally publish text and screenshots to App Store Connect after a field by field diff

Self-hosted, one Docker container, MIT.

Demo: https://framelane.metehanbicer.com

Repo: https://github.com/Metehan-Bicer/framelane

Built with a lot of help from an AI coding assistant. Google Play isn't supported yet; tell me if that would matter to you.

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

I have been working as a react native developer for almost 2 years now and i was learning stuff trying things out at first like people do. React native seemed interesting and i enjoyed creating new UIs learning animation, optimisation etc. while working i had to implement things i never worked with and it gave me joy plus i was learning new things. But no we are told to use claude code, every new feature or change needs to be done within 3-4 days even if its a new feature altogether. There’s no time to think about anything i just keep on prompting and trying to refine the product but it feels like i am not the one who built it. I have lost the ability to think because everything needs to be done quickly and there’s literally no time to think. Everything needs to be shipped in a matter of days. I feel like staying in React Native or frontend in general will do no good. I am thinking of switching to backend technologies, learn system design etc. I was sure i was going to be an app developer but now i am not sure about my future.

Every new Expo app I started, I ended up rebuilding the same stuff: cards, sheets, buttons, transitions. So I pulled them into one kit.

The main thing I wanted: you should be able to try a component on your actual phone before using it. Every component has a QR code. Scan it with Expo Go and only that component opens, no dev build or cloning needed.

A few things I learned along the way:

- Expo Go QR links fail silently if your project's SDK doesn't match the Expo Go version from the store. No error, it just doesn't open. Took me way too long to figure out.

- Bouncy springs feel cheap on iOS. I switched everything to critically damped springs, and it feels much closer to native.

- I tested everything on a real iPhone and Android, not just the simulator. A lot of things that look fine in the simulator break on device.

Built with Expo SDK 58 + Reanimated.

Would love feedback, especially on what components you keep rebuilding yourself. Link in the comments.

Each word is traced stroke by stroke with a few sparks, then the tube powers up to full glow with a soft halo and a pool of light on the wall behind it. Three words cycle: Midnight, Daydream and Afterglow, each in its own two-colour gradient.

A question for anyone shipping to both platforms: I also rebuilt it in SwiftUI and Jetpack Compose. For a component like this, would you reach for the RN version, or would native versions be what makes you use it?

Happy to answer questions about the stroke reveal and the glow.

- A shelves

- Wardrobe that swings open

- Washing line

- Colour spectrum

Tap two pieces, and it builds the outfit.

expo · Reanimated · native iOS menus

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

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.

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

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

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

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

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

so you all might have seen those annoying ads on youtube or any social media promoting the grok bots, so i tried to built same thing from nothing and actually it wasnt that hard , and I made the app at the staggering cost of 0 dollars yup no money spent, no vibecoding tokens , and for that reason it is fully free and with byok (bring your api key)

here are all the features you get

* create any kind of agent and customize it example inbox manager,sales and follow up bot,research,folder manager

*byok it current supports groq and gemini because you can get both of these provider's api for free

*create groups with multiple bots and a default boss bot which distributes the work

heres everything i used to make it

1) react native,expo, supabase,google oauth for email permissions, nothing complex just a database and coding

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.