- Nov 3, 2011
- 6,622
- 0
- 0
Lately, there has been a lot of news revolving around MS' involvement with Android, causing many of us to shake our heads in disbelief. Not long ago, many of us were calling the Nokia Normandy fake, which is turning out to be real. Now we have reports saying that MS may attempt to bring Android apps over to WP, which sounds even more outrageous. In isolation, and individually, I find these steps quite ridiculous, but if pieced together to a larger and cohesive strategy, then I'm not so sure. What follows will sound crazy (possibly not just at first), but bear with me...
Preface:
I've spent a good three hours looking at AOSP. Much of it is factually dead. By that I mean nobody is expecting Google to update those bits again. Messaging is one example, where the newer and more powerful implementations have been moved out of AOSP and into the closed-source parts of Android (GSM). Google is expected to continue this trend, aggressively improving GSM and encouraging developers to prefer them over their AOSP equivalents. Why? Because Google's primary goal is to decrease the number of apps that are compatible with AOSP and increase the number of apps that run only on fully certified Android (AOSP+GSM). This is a fully justifiable protectionist play to keep their most important asset (the apps in the Android ecosystem) fully under their control. Anyone can open an app store for AOSP based apps (like Amazon has), but Google has legally ensured that they are the only company that can offer AOSP+GSM based apps.
I must assume that the companies who currently rely on AOSP aren't entirely pleased by this, because the parts of Android they rely on are really just Google's red headed stepchildren. Far worse is that the number of apps that run on their products is steadily decreasing, relative to the number of apps that run only on AOSP+GSM. For example, compared to Google Play, the Amazon app store is already rather outdated. That is of course just another benefit to Google, as they hope to eventually convert every AOSP company to an AOSP+GSM company.
Chapter 1... Embrace:
MS forks AOSP Android and hands it over to a newly created FHA (Free Handset Alliance), of which Microsoft, Amazon, and most (if not all) of the Chinese handset manufacturers are founding members. The FHA would continually lobby Samsung to also join in with Tizen. In 2016, when Nokia can legally jump back into the Smartphone business, it would join the FHA as well.
While MS' fork of AOSP must remain compatible with the branch maintained by Google, everything else is developed through a community effort, in which any and all can participate and contribute to, including individual developers and none FHA members. The core management, leadership and development teams operate from Finland (ex Nokia).
The only restriction for FHA handsets is that they may not include any of Google's services (think of the marketing tagline... "Spyware free Android"). Instead, FHA handsets would ship with the full complement of MS' services. MS offers these services to FHA members at no cost. MS does this not only as a means of promoting their own services over their competitors, but primarily as a means of replicating all the features Google moves out of AOSP and into GSM. The idea is that FHA handsets run not only AOSP apps, but AOSP+GSM apps as well, with zero modifications. Recompile the AOSP+GSM app in Visual Studio... publish to the FHA app store... finished.
This must all combine into a single ecosystem. The Nokia Normandy will run FHA apps. Amazon Kindle Fire will run FHA apps (meaning all FHA devices also get 1st class access to Amazon's content library).Windows and WP will also run FHA apps, but only the subset which is deemed compatible with WinPRT's security model. Apps that violate any of WP's security principles or otherwise require features deemed unsafe wouldn't be distributed through the Windows Store.
Why would any company join the FHA? Firstly, members would gain access to services typically only available to members licensing the full Google experience (AOSP+GSM), at no extra cost. Second, In contrast to Google, MS doesn't dictate what OEMs may and may not include on their devices. If Samsung wants to replace any one of MS services with their own, they are free to do so. Third, the FHM reduces OEM risk, as they are no longer at the mercy of a single OS supplier, giving them more leverage against both Google and MS. Finally, and most importantly, MS doesn't ask for IP licensing fees from FHA members. MS asks that only of those in the OHA.
Chapter 2... Extend
For companies using AOSP, I think FHA Android would be a no-brainer. For companies using AOSP+GSM, choosing FHA over AOSP+GSM would at least be a very interesting proposition.
Although some might view this as MS giving up on WP, it would actually be more about assimilating Android and its hardware base, essentially making it impossible for Google to control either. If enough OEMs decide that consumers see little difference between FHA and AOSP+GSM handsets, while improving profits, I could imagine quite a large wave of FHA devices replacing the AOSP+GSM devices currently on store shelves. If that ever translates into a majority of the Android market, then I suspect it's game over for AOSP+GSM.
Anyway, assuming FHA devices can at some point achieve market dominance, that is when MS can start playing the same game Google is playing with GSM today. MS can start incorporating new features available only on FHA devices and encourage developers to make use of them, deliberately fracturing the Android ecosystem. Over time, FHA Android would start looking ever more like WP. The differences between AOSP+GSM Android and FHM Android would continually grow, while the differences to WP would shrink.
Chapter 3... Exterminate
At some point, FHA Android can be slowly relegated to the low end, while offering WP as the natural path forward.
Why would MS want to get rid of FHA Android after proving itself so successful? For the same reasons Google is trying to deemphasize and get rid of AOSP now... a protectionist play...
Epilogue
This sounds a little too much like a Hollywood movie, but I don't see how Google could effectively counter such a move by MS.
It also comes with a lot of IF's, I know. I'm not saying this can work... I'm just thinking out loud and putting it out there for everyone's consideration. Obviously there are a lot of possible variations on this plan, and I'm definitely not saying this is best. It's crazy... but how crazy is it?
TL;DR;
How Obi Wan Gates and Satya Skywalker may plot to overthrow The Empire and free the galaxy from Android dominance.
Preface:
I've spent a good three hours looking at AOSP. Much of it is factually dead. By that I mean nobody is expecting Google to update those bits again. Messaging is one example, where the newer and more powerful implementations have been moved out of AOSP and into the closed-source parts of Android (GSM). Google is expected to continue this trend, aggressively improving GSM and encouraging developers to prefer them over their AOSP equivalents. Why? Because Google's primary goal is to decrease the number of apps that are compatible with AOSP and increase the number of apps that run only on fully certified Android (AOSP+GSM). This is a fully justifiable protectionist play to keep their most important asset (the apps in the Android ecosystem) fully under their control. Anyone can open an app store for AOSP based apps (like Amazon has), but Google has legally ensured that they are the only company that can offer AOSP+GSM based apps.
I must assume that the companies who currently rely on AOSP aren't entirely pleased by this, because the parts of Android they rely on are really just Google's red headed stepchildren. Far worse is that the number of apps that run on their products is steadily decreasing, relative to the number of apps that run only on AOSP+GSM. For example, compared to Google Play, the Amazon app store is already rather outdated. That is of course just another benefit to Google, as they hope to eventually convert every AOSP company to an AOSP+GSM company.
Chapter 1... Embrace:
MS forks AOSP Android and hands it over to a newly created FHA (Free Handset Alliance), of which Microsoft, Amazon, and most (if not all) of the Chinese handset manufacturers are founding members. The FHA would continually lobby Samsung to also join in with Tizen. In 2016, when Nokia can legally jump back into the Smartphone business, it would join the FHA as well.
While MS' fork of AOSP must remain compatible with the branch maintained by Google, everything else is developed through a community effort, in which any and all can participate and contribute to, including individual developers and none FHA members. The core management, leadership and development teams operate from Finland (ex Nokia).
The only restriction for FHA handsets is that they may not include any of Google's services (think of the marketing tagline... "Spyware free Android"). Instead, FHA handsets would ship with the full complement of MS' services. MS offers these services to FHA members at no cost. MS does this not only as a means of promoting their own services over their competitors, but primarily as a means of replicating all the features Google moves out of AOSP and into GSM. The idea is that FHA handsets run not only AOSP apps, but AOSP+GSM apps as well, with zero modifications. Recompile the AOSP+GSM app in Visual Studio... publish to the FHA app store... finished.
This must all combine into a single ecosystem. The Nokia Normandy will run FHA apps. Amazon Kindle Fire will run FHA apps (meaning all FHA devices also get 1st class access to Amazon's content library).Windows and WP will also run FHA apps, but only the subset which is deemed compatible with WinPRT's security model. Apps that violate any of WP's security principles or otherwise require features deemed unsafe wouldn't be distributed through the Windows Store.
Why would any company join the FHA? Firstly, members would gain access to services typically only available to members licensing the full Google experience (AOSP+GSM), at no extra cost. Second, In contrast to Google, MS doesn't dictate what OEMs may and may not include on their devices. If Samsung wants to replace any one of MS services with their own, they are free to do so. Third, the FHM reduces OEM risk, as they are no longer at the mercy of a single OS supplier, giving them more leverage against both Google and MS. Finally, and most importantly, MS doesn't ask for IP licensing fees from FHA members. MS asks that only of those in the OHA.
Chapter 2... Extend
For companies using AOSP, I think FHA Android would be a no-brainer. For companies using AOSP+GSM, choosing FHA over AOSP+GSM would at least be a very interesting proposition.
Although some might view this as MS giving up on WP, it would actually be more about assimilating Android and its hardware base, essentially making it impossible for Google to control either. If enough OEMs decide that consumers see little difference between FHA and AOSP+GSM handsets, while improving profits, I could imagine quite a large wave of FHA devices replacing the AOSP+GSM devices currently on store shelves. If that ever translates into a majority of the Android market, then I suspect it's game over for AOSP+GSM.
Anyway, assuming FHA devices can at some point achieve market dominance, that is when MS can start playing the same game Google is playing with GSM today. MS can start incorporating new features available only on FHA devices and encourage developers to make use of them, deliberately fracturing the Android ecosystem. Over time, FHA Android would start looking ever more like WP. The differences between AOSP+GSM Android and FHM Android would continually grow, while the differences to WP would shrink.
Chapter 3... Exterminate
At some point, FHA Android can be slowly relegated to the low end, while offering WP as the natural path forward.
Why would MS want to get rid of FHA Android after proving itself so successful? For the same reasons Google is trying to deemphasize and get rid of AOSP now... a protectionist play...
Epilogue
This sounds a little too much like a Hollywood movie, but I don't see how Google could effectively counter such a move by MS.
It also comes with a lot of IF's, I know. I'm not saying this can work... I'm just thinking out loud and putting it out there for everyone's consideration. Obviously there are a lot of possible variations on this plan, and I'm definitely not saying this is best. It's crazy... but how crazy is it?
TL;DR;
How Obi Wan Gates and Satya Skywalker may plot to overthrow The Empire and free the galaxy from Android dominance.
Last edited: