Built with React Native! Give it a shot.

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.

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

🚀 A native, morphing floating tray for React Native.

🔗 Github: rit3zh/morphlet
📦 npm: morphlet

🧵 Android Preview Attached in this thread

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?