-
-
Notifications
You must be signed in to change notification settings - Fork 324
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A GDPR compliant version #1182
Comments
@Theweird Yeah, going to pure react native instead of Expo sounds good to me. Though I'm not sure when will we have internal bandwidth at SysGears to make the switch, I will certainly welcome contributions in this direction. |
My issue in expo/expo was closed with a fortunate message. |
Update: expo added a new experimental feature to exclude unused libraries from the APK build. However, this still leaves 3 statistical trackers in the build. |
After the big waves tossed by privacy scandals around the medical app ADA (https://www.heise.de/ct/artikel/Massive-privacy-deficiencies-in-the-health-app-Ada-4551629.html) we started investigating the state of privacy of the app built on this kit.
While this kit is really great to work with and expo might be good in development, for building an app that works with customer information and therefor has to respect the GDPR on the european market, expo seems to be a pain in the ass.
see https://expo.io/privacy and https://forums.expo.io/t/expo-list-of-vendors/18511
I already opened a request to expo to make SDKs and functionality with outbound calls configurable.
expo/expo#6763
In addition to that, to give developers the possibility to avoid expo if they dont want to use it, would it be possible to create a second mobile client working as bare react native app without expo?
The text was updated successfully, but these errors were encountered: