1 & 2) Yes, almost all of the mobile code lives in one repo, and the 10M number quoted is all in one mercurial repo.
3) There's a lot of different things we do to work around such issues. Some things that come to mind right now:
- We have plugins for Android Studio to avoid loading all the code at once that help.
- We had forks for the Kotlin plugin for Android Studio to deal with some issues that were worse for our repo. (especially around module loading)
- We also worked with JetBrains by pushing some fixes and they fixed a lot of the issues over time.
- We do a lot of work as async jobs that run on the repo without you waiting for them, so you don't have to wait for such tools.
3) There's a lot of different things we do to work around such issues. Some things that come to mind right now: - We have plugins for Android Studio to avoid loading all the code at once that help. - We had forks for the Kotlin plugin for Android Studio to deal with some issues that were worse for our repo. (especially around module loading) - We also worked with JetBrains by pushing some fixes and they fixed a lot of the issues over time. - We do a lot of work as async jobs that run on the repo without you waiting for them, so you don't have to wait for such tools.