Amazing and inspiring

No problem at all :)

Makes sense - and looks fun!

Nice! Did you go for Readium, or did you roll your own using webview?

Doing tooling should be fully supported in Readium. Just ping me if you have questions.

I’ve made two RN epub apps using the Readium toolkit (swift/kotlin) - writing a few custom views that takes advantage of this rather mature library has worked out really well.

Love it :)

Appreciate it! <3

Wow… wizard!

Could you use `React.FC<Props>` to define the return type? It should be safe and sound now, shouldn't it?

Same! This is a good place to be!

It is not trivial - but to get an idea of what REA copies you can add logging to the `ShareableObject::toJSValue` method in the native code (Shareables.cpp#233) - just `cout` out the names of the properties it traverses - look for candidates for simplification if this makes sense for you.

I once had a worklet where I was using the React Native `Platform` object to check the OS version - changing this to passing the OS as a stand-alone string made the app so much more snappy since REA was copying the Platform object fully each time the function was called...

Optimizing worklets are often about the cost of copying the captured context of the function - REA automatically detects what you're using inside the worklet function and copies it into the worklet runtime when you call the worklet. Deep objects can add a big performance hit if passed in the ctx.