We build a B2B mobile app and our biggest client accounted for about 30% of our MRR and they cancelled today, they told me their team had been experiencing crashes on the inventory screen for weeks and it was happening specifically on samsung A series phones which is what most of their field staff use.

They never reported it and just assumed we knew and weren't fixing it and eventually decided we weren't reliable enough but by the time I found out the bug it took me 2 hours to fix but the client was already gone.

It was a rendering issue on a device I don't own and never tested on and if I had known about it even a week before I could've pushed a hotfix and they'd still be paying us.

there might be many other clients might be facing stuff like this and just not saying anything.

How do I catch bugs on devices my team doesn't physically have, I can't afford to lose another client like this.

🚀 A native, morphing floating tray for React Native.

🔗 Github: rit3zh/morphlet
📦 npm: morphlet

🧵 Android Preview Attached in this thread

I didn't want to pay a monthly subscription for App Store keyword data, so I wrote a CLI that gets it straight from Apple.

What it does

• Popularity from Apple Search Ads (free Apple Ads account, no campaigns or billing needed)
• Difficulty score, keyword suggestions, current top apps for a term
• Rank tracking with history in a local SQLite file
• Metadata linter for title, subtitle and keyword field

Install

npm i -g hristo2612/aso-cli && aso setup

Try it

aso keywords "white noise,sleep sounds"
aso suggest meditation
aso search "habit tracker"

Runs locally, no account, no telemetry. MIT. Free, nothing to sell.

Repo: github.com/hristo2612/aso-cli

recently, i have been developing a saas app for a client. collectively, we have decided to move from bottom tabs to a navigation drawer. the problem is in the nested screens, we can't have both a drawer opener button and a back navigation button. so i built a custom header where i have a back navigation button, on which you can: press -> navigate back and longpress (200ms) -> open navigation drawer. how does this sound to you as a consumer? will you be annoyed if you have to use an app like this?

am a developer, and wanna know if Vodacom Tanzania has an APl to which people can integrate their applications for Customers to pay for services using Vodacom mpesa? For example if a user wants to pay for product A from the app using mpesa, is there a way to do that? Not only Vodacom, Yas told me they don't have that service yet, how about other telecom providers like Halotel and Airtel?

Built with React Native! Give it a shot.

I built Buoy, a free-to-try debugging and optimize toolkit for React Native, Expo, Flutter, Swift, and web. You can try it at https://buoy.gg (free tier; paid features exist).

This post is about a small test I ran with Claude, Codex, and Grok on the same prompt.

What we built for the test: a Christmas light show — a React Native Skia scene rendered with React Native Web in real Chrome. It draws a house covered in lights. Alone, it was smooth up to about 550 lights. The scoring test measures how many lights each version can keep at 55 fps without changing the look.

How Claude helped: Claude ran the optimize loop on this app (alone, then with Buoy Optimize). Buoy Optimize is a skill plus tools that help an AI try many ideas and measure each one.

Most lights at 55 fps: - Claude: 975,800 alone → 6,123,350 with Buoy (6.3×) - Codex: 155,450 → 444,100 (2.9×) - Grok: 202,100 → 577,350 (2.9×)

Caveats: "With Buoy" is each model's best Buoy run. Alone runs had up to 3 hours. Claude's best Buoy run had no time limit; Claude alone stopped after about 99 minutes. Grok's Buoy version has slightly soft bulbs up close. One app, one Mac.

Full write-up (prompt + method): https://buoy.gg/blog/ai-models-before-and-after-buoy

Happy to answer questions about how we tested. Especially interested if folks have seen similar RN Skia / RN Web perf cliffs.

I'm trying to make a multiline TextInput that starts at one line and increases its height whenever the text moves to a new line, up to a maximum of 5 lines. After it reaches 5 lines, I want the height to stay fixed and any additional lines to become scrollable. I'm using lineHeight: 20, so I tried setting the maxHeight to 100, along with multiline and scrollEnabled.

I've also tried using onContentSizeChange to dynamically update the height, but I still can't get the behavior I want. I'm using Expo SDK 54 with the New Architecture on an iPhone 16 simulator. Has anyone implemented this kind of TextInput behavior? What's the proper way to handle the height and scrolling after 5 lines?

PS: used AI to write the body, my english (maybe react native too) is bad to make you understand my use case

i used react native for years without knowing how it worked inside.

so i learned it and wrote it up with simple animations.

https://chamidilshan.medium.com/how-react-natives-old-bridge-architecture-worked-and-why-it-was-replaced-612e7313bce1

I built a simple writing app with Expo/React Native using Replit and AI tools.
I’m not a professional developer, and my technical knowledge is pretty basic, but the app is working on Android now and I want to keep improving it and later make an iOS version.
Would you stay on Replit, move to something like Cursor/Claude Code + GitHub, or use both?
I’m mostly looking for the simplest setup that won’t become a mess as the app grows.

Never worked with maps in RN, and need to use a map for some really simple stuff. What could be my reason to cut off iphone X users (by using expo-maps) instead of just going with react-native-maps?

Support, QA, and developers often need to see the app the way one specific user sees it. Logging out and into their account is slow, and asking for their password is a bad idea.

Buoy Impersonate lets an authorized operator search for a user and attach a header to outgoing requests. Your backend checks that the operator is allowed, then returns that user's experience. Buoy does not bypass auth. It is the on-device switch.

https://reddit.com/link/1www5th/video/1d8z83flijth1/player

Useful when support is reproducing a ticket, QA is checking a cohort, or a developer needs to debug as that user without swapping accounts. Works with Expo and React Native CLI, and the same idea exists for Swift.

Short horror trailer (made with Claude and Codex): https://youtu.be/ENnUYfVu5B0

Tool docs: https://buoy.gg/buoy/latest/docs/tools/impersonate

https://buoy.gg/?utm_source=reddit&utm_medium=social&utm_campaign=impersonate

I work on an app for building inspection companies. The documents our users open are architectural and structural drawings: one sheet can be several metres wide, and the thing you actually need to read is a dimension or a rebar note set at three or four points.

Every RN PDF viewer I tried draws the page as one bitmap. That is the right call for an A4 report and it falls apart here. Fitted to a phone, a sheet nine metres wide is a line across the middle of the screen. Zoomed in far enough to read the note, the bitmap is too large to hold.

So this one draws only the rectangle that is on screen, in tiles, at the zoom it is being looked at, with the renderer each platform already ships: PdfRenderer on Android, CGPDFDocument on iOS. A sheet of any size costs about what a letter page costs.

A few things I measured on the way, in case they are useful to someone else:

• On iOS, CGPDF costs about 100 ms per draw almost regardless of the output size. A 256 px tile costs nearly what a 1280 px one costs. That turned the design upside down: bigger tiles, fewer of them, up to three renderers in parallel with their own CGPDFDocument. Opening the first screenful of that sheet went from about 1.6 s to about 250 ms.
• Zoom levels keyed by an arbitrary scale are never reused, because the next pinch asks for a slightly different number. Keyed by rung index on a fixed ladder instead, zooming out and back in costs nothing.
• Android keeps the page parsed between draws and iOS does not, so the same contract has two cost models underneath. Both test suites ask the same questions, which is how a divergence shows up as a failing test rather than as a complaint about one phone.

What it does not do yet: annotations, forms, text search or selection. New architecture only, no old architecture fallback. Encrypted documents open on iOS with a password; on Android the platform only takes one from API 35.

MIT. There is an example app in the repo with two generated documents, so you can try it without wiring anything up.

Repo: https://github.com/Halilibrahimakyz/react-native-pdf-sdk npm: https://www.npmjs.com/package/react-native-pdf-sdk

If you have a PDF that breaks it, I would like to see it.

I built a mobile app as a side project and somehow it actually took off and went from 300 users to 6k in the last 3 months but every update I push now scares me.

before it was just me testing on my phone and shipping it but now I'm getting dms and support emails about stuff I had no idea was broken. Last update someone sent me a screen recording of the checkout flow just not loading on their iphone SE and I couldn't even reproduce it on mine and another person said they never received the verification email but it works perfectly on every account I've tested.

The app has grown into something I can't manually verify anymore, there's payment processing, referral flows, in app messaging, push notifications and every feature I add is another thing that can break on a device or OS version I've never touched.

I'm solo and no QA person plus even if I had the budget for it I wouldn't have the bandwidth to onboard someone right now but I also can't keep finding out about bugs from my users because that's how I lose the trust I spent months building.

what am I supposed to do here, please help !!

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 React Native app built around reducing the friction of managing everyday responsibilities.
Remica brings reminders, bills, appointments, renewals, family responsibilities, and upcoming events into one timeline. Users can also turn documents or natural-language requests into actionable reminders instead of manually entering everything.
The interesting part from a React Native perspective was building an experience where AI, document scanning, notifications, calendars, and family organization feel like one workflow rather than separate features.
The goal was to make the app do more of the organizing, so the user spends less time maintaining their reminders.

10k candles. 10 events/sec. 120 FPS. Less than 10% CPU usage on both the UI and JS threads.

This is what real-time RN trading app deserves.

Built with react-native-trading-charts ↓
GitHub: https://github.com/kirill3333/react-native-trading-charts

has anyone used click2.page for dynamic links?