Chrome Mobile OS. Not if and not when, but how.

Chrome Mobile OS

The Android Emulator home screen. (Photo credit: Wikipedia)
The Android Emulator home screen. (Photo credit: Wikipedia)

Update 2017 Oct 16

Ah was I right again?

Update 2015 Oct 30


(AFAIK, name invented by me today 🙂 )

Alphabet’s Google to Fold Chrome Operating System Into Android (The Wall Street Journal)

  1. Which one is “folding” into which one?  None. They are merging into one.
    1. Technically Chrome OS is a real OS
      1. My (safe) speculation is that as much as possible of the Chrome will be kept and used as foundation.
    2. Android is a kindergarten OS, that was released to early and was never meant to be.
      1. But children liked it.
    3. But even now it is very likely Chrome Books will be gradually updated (as ever) to the state of being totally “new” OS. Which is not that “new”.
      1. Which for Chrome Books is just new part of the top layer, to host JVM
        1. And “something more” so that Android App’s can run natively
        2. This in essence is not far from new (Android) SDK rewritten to run on Chrome OS
        1. With Chrome Browser untouched of course.
  2. Marketing is all about Manipulating the Focus.
    1. All the news that you will initially read on this subject is about manipulating your focus away from the point 1.
  3. Name is extremely important. My speculations bellow have ignored this point.
    1. Of course it will be based on the word “Android”, as per point 2
      1. Certainly “ChromA” is out of the question
      2. Like “ChromUX” was out of the question
        1. Regardless of the fact that Chrome OS is Linux + Chrome browser
  4. 2017?
    1. As I said bellow: transition will be done extremely carefully
    2. By 2017 Google will know and see where is the best place to attack Microsoft
      1. Win10 situation will be definitely clarified by then

So here we are. Yer another speculation turned out not to be a speculaltion.

Update 2014 Sep 12

Well almost exactly a year latter this little (nasty) speculation of mine, it seems, might not be that speculative?

One (extremely) careful migration from Android to Chrome OS has started. Just after Android Lemmings have readily swallowed one very large does of anesthetic called: Android L.

But today (I noticed that) a lot of people are scrambling back to to this Google video from June 2014.

Google I/O 2014 Keynote.Watch very carefully:

Sep 08 2013

Well of course I could not miss the whole of today’s Google “Chrome Apps” charade. How could anyone ? There was also one single thought I could not escape. One agonizing question drilling into my consciousness (hint: I am being overly sarcastic here) One sinful question I have to confess :

What is the Android Staying power ?

Is it really possible this is already a valid question to ask ? Can this really be true?
Continue reading “Chrome Mobile OS. Not if and not when, but how.”

New Office has decided the faith of Xamarin

[2016 Mar 31]

Xamarin now free in Visual Studio

Before you jump to conclusions please consider this:  By this move, Microsoft is not using Xamarin, Microsoft is giving it away. And that is the core logic here.

[2014 Nov 18]


The reason Microsoft has been able to keep both Android and iOS versions identical is thanks to a new cross-platform approach to the codebase of Office. “It has required us to be great at writing platform code for Android, code for iOS, and code for Windows,” says Atalla. All of that effort has been put together into a single platform so Microsoft can share code across iOS, Android, and Windows. The benefit is faster updates and more features for Office users. “Over the past year, we’ve had 150 different updates to Office applications across all platforms,” says Atalla. “We’re moving very very quickly in adding capability and adding functionality.”


They are talking about Xamarin here surely? Well… no. They do not talk about Xamarin.

This is description of pure C++, MSFT multi platform foundation made for next wave of Office Apps. Put this together with already brewing confusion about Xamarin vs MSFT, and you do not need a lot of spice for a very juicy gossip.

Yes here they/we/whoever are not talking common multiplatform runtime, that is true. But, I think Xamarin has lost. MSFT has decided to implement common multi-platform platform (sic) itself, vs buying Xamarin or working with Xamarin or some such long winded excersize. Microsoft solution is currently not a single monolithic executable providing a common runtime that is true. And significant. For me this means they have finally concluded that is not a best approach. Especially when needing and using native UI.

In essence now after next Office wave is shaping up publicly, it is clear MSFT does not need Xamarin. I do not think MSFT will be against Xamarin efforts, quite the contrary, but still Xamarin will not be the foundation of any MSFT made, cross platform code.

End of story? Not yet. The end of Xamarin story is detailed here. It is called “AirSpace”. The new Microsoft Cross Platform Architecture.

It is hard to imagine this will be used just for Office apps.
It is hard to imagine this will be used just for Office apps.

It is not entirely clear is this architecture implemented as a “tool chain” or a “platform”. I think this is combination of both.  The “thing” spills out common modules yes, but they are compiled in different binaries for different platforms.  (platforms are listed on the left).

As the UI parts are definitely different since native UI’s are used, it is even less clear (from this picture) what is this “AirSpace Frontend”. Probably some abstractions (and tools)  to ease up the multi-platform UI building.

But one (key) fact is certain here: Microsoft has left common run-time architecture behind.  Above is a “tool chain” and “common” platform. But for multi-platform software production. Not for providing common run-time.

In case you have not noticed, Office and other Microsoft flagship products have never been running on top of CLR. Or implemented using .NET, C# and a such.

This all, seems to me as an EOL (end of line) for Common Language Runtime too.  In any case, end of story for Xamarin, foster-child.

(For the continuation of this speculation please proceed here)

[Update 2015 Feb 04]

Yet another merciless nail into the Mono coffin: Microsoft takes lid off .Net Common Language Runtime sauce