Modern API

[qusaieilouti99]

First of all, great job.

Moving to nitro modules is a good move, but I see the library isn't taking advantage of what nitro is capable of.

I mean like:
1- Being able to create multiple hybrid objects it's very useful for audio players ( currently stuck with expo-audio because of that).
2- A hook api, it'll be useful for quick usage and React familiarity for the users of the library.

I don't personally rely on hooks for the audio, but most of the major similar libraries do the same: react-native-video v7, react-native-nitro-image, expo-audio, and vision-camera.

Which BTW supports allowing multiple instances, I'm all into helping to move in this direction.

[hyochan]

That makes a lot of sense 🙏 — what you’re describing here is actually closely related to #695
about removing the singleton so multiple items can be initialized.

I’m currently working on this in PR #707
, which introduces hooks that already allow creating multiple instances. This PR is about to be merged and will go out in v0.2.0.

Also, the library was recently rebranded to React Native Nitro Sound. No breaking changes yet since it’s the same base, but going forward I plan to split sound and recorder into independent, composable APIs. That should make flexible extension and cleaner multi-instance handling a first-class part of the design as we track toward 1.0.0.

Would love to hear your thoughts as we move in that direction.