Post

I honestly never even thought about accessibility. We even use the NativeView and NativeText components directly to optimize performance by skipping all of that. We iterate so fast in startups, there’s no room for it until we have PMF.

> I honestly never even thought about accessibility. Probably why they did there best to make it accessible by default

Is this an actual memory leak? From the code samples, it looks like it should pile up some memory but then let that go. I agree this isn't a good default, and perhaps a dev-only warning saying "need an accessibility label on <view name>" would be best.

From 300MB to 7GB plus a full hang is even worse. Yeah, it’s not a leak, but an infinite traversal bug. In some very rare and not reliably reproducible cases, nested touchables can trigger this bug and completely freeze the app in our case. Adding a fallback `accessibilityLabel` did the trick.

Generally speaking, I don’t like these automated and expensive lookups. I’d rather have a dev-only warning that forces users to handle accessibility manually. And lookups should bail out fast and have some railguards.

FYI nested touchables are inaccessible as well.

I added a simple "fuck off" as Label and the rare bug is gone. This is just madness and a really bad default by RNGH and React Native. 2/4

Imagine, that change made our app the snappiest and fastest react native app I've ever seen. The fucking FPS counter is finally going up, not down when tapping a button. :D