Update multi-modules.mdx to add a note about it being a good idea to mark your schema module as a jvm-only module (#6277)

* Update multi-modules.mdx

Add a note about it being a good idea to make your schema module a jvm-only module when building for Android

* Update docs/source/advanced/multi-modules.mdx

Co-authored-by: Benoit 'BoD' Lubek <[email protected]>

* Update docs/source/advanced/multi-modules.mdx

Co-authored-by: Benoit 'BoD' Lubek <[email protected]>

---------

Co-authored-by: Benoit 'BoD' Lubek <[email protected]>

Author: StylianosGakis

docs/source/advanced/multi-modules.mdx

@@ -118,3 +118,8 @@ The `bidirectional` parameter is experimental and not compatible with <a href="h
 
 </ExperimentalFeature>
 
+## Optional optimizations
+
+In Android projects, to further improve build times you can consider making your schema module a JVM module instead of an Android library. Since Apollo Kotlin is multiplatform, and Android is capable of depending on JVM-only modules, you can benefit from reducing the amount of work needed to compile the schema module. This is true because JVM modules build faster than Android libraries even with identical source code.  
+This is often a good idea because Apollo often happens to be on the critical path of compiling your app. This happens when all the feature modules that use Apollo need to wait for all the type-safe code to be generated before they themselves can start building too.
+