Laurent Savaete

Hi @adrian7031 sorry for taking so long to reply. You're mentioning a few different issues, so I'll try to address them all: > The problem is that the zoomed tiles...

This actually is the same issue as #213 Summary of our discussion with @Hagellach37 - this happens because we are using the wrong data source in the code (app side)...

Some ideas: - analyze JS bundle content: https://create-react-app.dev/docs/analyzing-the-bundle-size/ or https://github.com/IjzerenHein/react-native-bundle-visualizer - use Hermes as the JS engine: https://reactnative.dev/docs/hermes - enable proguard: https://reactnative.dev/docs/signed-apk-android#enabling-proguard-to-reduce-the-size-of-the-apk-optional - possibly use google's AAB packaging format to...

Using AAB requires letting google manage signing keys, which means we lose control over the process and cannot distribute a compatible APK outside the playstore. This would probably cause a...

Other ideas: - drop unused architectures if usage stats suggest we can. Currently we build for `x86_64`, `x86`, `arm64_v8a` and `armeabi_v7a`. Each weighs between 6 and 8MB. - switch to...

> @laurentS should we close this one? as you've merged this: #594 I'd leave it open, there are still a few things we can do to reduce the size of...

Yes, we can definitely have both. I was thinking of analytics because adding a parameter is half a line of code, and would give more meaning to the stats we're...

Related #202

Thanks for reporting this. It's not ideal indeed. Short term trick: you can tap the text box to move it further down. I'm not sure what the long term solution...

To expand on this, we could even add a little extra logic to do something like this: - allow default tutorials to be translated like we mentioned above. All we...