Still way less how Google handles Android development, where recommended API in version X, turns out legacy in version X+1, replaced in X+2, but all need to be supported thanks to lack of updates.
Unlike the chaos, constant churn and developer frustration of Windows Phone development, Android development hasn't needed to osbourne their development environment and tools every year because of incompetence.
Instead they show incompetence at stuff like fragments, replacing build systems, broken Gradle builds at each update, outdated documentation, broken Android Studio and Support library releases, removing AS plugins without documenting how to work with them gone, adding PWAs and Flutter to the mix, ...
Which so much Android love I am curious to see how many apps you have released, since you seem to like the experience so much.
Incompetence was trying to convince developers to use that Flash ripoff Silverlight for mobile app development or trying to debug that horrible XAML pile of garbage or trying to build UI's with that bug infested piece of garbage expression studio. With Windows phone development you could never get comfortable because they were always osbourning the OS once they realized what a piece of garbage it was.
It's amusing how forgetful you are of all of the Windows phone development environment failures and the nightmares it entailed for developers, but somehow have Android development issues burned into your brain. I'm guessing you still harbor resentment towards Google for the failure of Windows phone. In time you'll eventually recognize that it was all due to the incompetence of Microsoft.