POC: Reduce loading of app due to crypto feature

[zatteo]

• Use react-native-quick-crypto when possible
• Delay CryptoWebview loading (getClient and useAppBootstrap can start before CryptoWebview loading)

Todo

• check if it is the delay is not too long
• check on iOS
• check on Android

[Crash--]

Since we open signup now to login / register, we can remove this cryptowebview, right?

[zatteo]

Since we open signup now to login / register, we can remove this cryptowebview, right?

Interesting, at least we do not need to open it at startup. It still used after but it can helps the loading time 👍

[Crash--]

Why do we still need it? I can't remember

[zatteo]

Why do we still need it? I can't remember

To polyfill crypto API in WebView in iOS if I remember well?

[Crash--]

Yeah but when do we need this crypto api anymore since we don't have Registration / Login?

[Crash--]

Oh, for Clisk connector maybe?

[zatteo]

Oh, for Clisk connector maybe?

All usage of Crypto WebView

• the onboarding process (see this commit) => this may not be necessary anymore as you said 👍
• initialisation of the local httpServer (to limit access to routes by cozy-apps, see this commit)
• to allow apps served over HTTP (non-secure) to access cryptography methods (see this PR)
  • on cozy-settings to enable or disable 2FA
  • on all apps that use cozy-keys-lib (= Harvest)

[Crash--]

on cozy-settings to enable or disable 2FA

We don't allow that anymore for new / migrated account.

initialisation of the local httpServer (to limit access to routes by cozy-apps, see this commit)

We can do without this kind of crypto.

And once we'll be able to load html file from http://localhost/file.html instead of getting the htmlContent and inject it (and with the dataproxy, we should be able to achieve this, we should take one or two hours together to test)