Refine Docs regarding the necessity of ejecting from expo

[thomas-woehrle]

Hi,

first of all, thanks a lot for this awesome piece of software!

Now, when finding this repository, I checked the installation section and was a bit bummed to see that it says:

If your project is initialized and built with Expo, you need to eject from the managed workflow by running expo eject or run npx expo prebuild in order to use this library. This allows you to integrate native libraries that are not supported in the managed workflow. Check the Expo documentation below for more details.

However, as it turned out, I didn't need to eject, because I am using expo development builds, which prebuilds automatically if no ios or android directories are available. It might be that this did not work before v1.0.9, because of the declaration of com.screenguard.ScreenGuardColorActivity (just speculation, I am not an expert).

It is awesome that the package does not require ejection from the managed workflow when using development builds and I think making this clear in the documentation would be good, so potential users aren't scared away.

(Disclaimer: I only used the basic register/unregister functionality, maybe ejection is needed for more intricate stuff)

[gbumps]

hi @thomas-woehrle , thanks for the response, I'm very appreciated. Of course, you can contribute not only library code, but also library document as well here.

If anything need to be improved, please let me know! I'm very supportive!

Thanks and happy hacking!