Removing expo dependency from react-native-executorch

[jakmro]

Hi everyone! 👋

Currently, our project relies on expo, expo-file-system, and expo-asset to download and store models. However, we've received feedback that integrating Expo into existing apps has caused issues for some users.

Right now, we handle downloading and storing the models for you. But to reduce friction and dependencies, we're exploring the possibility of removing the Expo dependency entirely.

Key questions:

1. How important is it for you that we manage file downloads and storage for you?
2. Would you be willing to handle model downloading and storage yourself if it meant we could remove the Expo dependency?

Your feedback will help shape the future of the project. Please let us know your thoughts — whether you're strongly in favor, against, or somewhere in between.

Thanks for being part of the project! 🙌

[DarkSorrow]

I think its a good idea to keep the file management outside of this library and worst case maybe just make it as a second library that people can use. Downloading and managing files for an app is something that directly touch the user experience and in my opinion should be handled with the final app philosophy / design.