Because Android achieved dominance, it's now starting to lock down how much its OS can be modified by other vendors and locking manufacturers into using either Google's services or having to make their own from scratch on top of an outdated OS shell. Microsoft is probably wondering how much appetite there is for vendors to make a break with Android and try to replicate their past successes with a new, more modern mobile OS.
At the same time, it's trying to take care of its legacy users and giving them what they want and what they ask rather than simply dictating to them "here's how you will be using your computers." Also, not what you'd call nuts, just listening to consumers and learning from their experiments.
One would think that you wouldn't want to switch out a framework later. After all, your choice of network is one of the defining factors of how everything will work. Swapping it out means rewriting most, if not all, of your CRUD functionality and then doing a whole lot of regression testing. Doesn't seem very cost or time-effective.
Because Android achieved dominance, it's now starting to lock down how much its OS can be modified by other vendors and locking manufacturers into using either Google's services or having to make their own from scratch on top of an outdated OS shell. Microsoft is probably wondering how much appetite there is for vendors to make a break with Android and try to replicate their past successes with a new, more modern mobile OS.
At the same time, it's trying to take care of its legacy users and giving them what they want and what they ask rather than simply dictating to them "here's how you will be using your computers." Also, not what you'd call nuts, just listening to consumers and learning from their experiments.