Hey Hana & Josue, congrats on the launch. I like your approach of how to integrate it into products (via native React libs). I think you could go even a little bit further. One concern I would have is that by using your react library, I also bring in a new state management (mobx). In our case it would be fine, because we are using it already, for others it might be an issue. The most extreme version I found is from feedback.fish, which gives a native react component, but internally imports their scripts still in an iframe.

The other thing would be, that the react package could export not only hooks to interact (useMagicBellEvent), but also provide some hooks or headless components to easier integrate with existing UIs. Something like this is very important to all external services we bring in, because our Product Design should feel like one.

1. We are going to remove Mobx. It will also reduce the learning curve for our customers. This change won't affect our API and will be fully backward compatible. We are considering Valtio as an alternative [0]. 2. As much as we can help it, we are not going to embed iframes. We'd love to deliver a native, and lean experience. 3. We already provide a network layer library [1] and want to offer more headless components. Can you give us some feedback on what you'd like to see? We are very inspired by Downshift's approach [2].

[0] https://github.com/pmndrs/valtio [1] https://www.npmjs.com/package/@magicbell/core [2] https://github.com/downshift-js/downshift