Request: update docs about MobileAds.initialize, of when it's ok to use it

"

If you have to initialize the Google Mobile Ads SDK on app launch, that is fine but not something we recommend for implementation purposes." ...Yes the documentation is correct but as a best practice we recommend explicitly calling MobileAds.initialize. If by "it on the UI thread" you're referring to initializing the SDK it is strongly recommended to call this methods on the main thread. 

"

The docs say it should be called as soon as possible :

"Initializes the Google Mobile Ads SDK.
Call this method as early as possible after the app launches to reduce latency on the session's first ad request.
If this method is not called, the first ad request automatically initializes the Google Mobile Ads SDK"

So, please update the docs accordingly:

1. Explain that even if ad-consent wasn't granted yet, it will be used on ad-request anyway, so it's ok to call it. 

2. Explain what is truly recommended, because currently it's a contradiction : as soon as possible after app launch, vs after ad-consent.

3. Write that it should be done on the UI thread, and also do it for other functions.

Please either you or them solve this and update the docs about this function. 

Talk together. Don't let each team tell me to talk to the other team.