81–90 of 216 posts
what an unhelpful title EDIT: for those downvoting me, how is "Update from the CEO" in any way relevant to the article's content?
I had quite a few random downvotes today too (for completely aseptic claims) so I suspect someone's trolling.
Earlier quoted context omitted.
Device fragmentation on Android is nothing like fragmentation used to be. At least on Android you can write one app and then tweak it to work on different devices, previously you had to write apps as different as Android/iOS/Windows for each device - and often individual manufacturers even had multiple platforms to write for. And don't even get me started on distribution. You used to have to negotiate with carriers i…
>At least on Android you can write one app and then tweak it to work on different devices, previously you had to write apps as different as Android/iOS/Windows for each device - and often individual manufacturers even had multiple platforms to write for. >So I think we owe Google some congratulations. Before Android, you could write a Windows Mobile app and have it run pretty much on every Windows Mobile device and t…
Earlier quoted context omitted.
How would that work? What would it be like? Android is powered by native apps, Chrome by cloud apps. Chrome already runs on Android. They have different approaches and I don't see how they how they could form a coherent whole or how one would benefit from a merger with the other. :/
> How would that work? Move Native Client for ARM into Chrome on Android (or, wait until PNaCl is ready, and move that into Chrome for Android). Focus effort on exposing functionality currently available to native Android apps through web APIs in Chrome to make Chrome apps (using NaCl/PNaCl where that kind of performance is needed), rather than Dalvik ones, the preferred mechanism for delivering apps on Android. At t…
But would that improve the Android platform? I'm wondering if it would be confusing or complicated for users, getting some apps from play and other from the Chrome store. Having apps in the launcher and some other apps you have to run from Chrome. Although at that point Google could merge the Chrome store and Google Play and have shortcuts for Chrome apps that launch a chrome-less browser to look native. Now that I've though about it I think it could work rather well, but I'm still wondering what would be the benefit for the users of Android.
Edit: Now that I've seen vibrunazo's comment I think I get it. If Google build a web programming api that is the same as Android's programming for one is programming for the other. I think that would be truly awesome indeed, I enjoy developing for android, not so much for web.
> But his insight immediately struck a chord because at the time it was extremely painful developing services for mobile devices. We had a closet full of more than 100 phones and were building our software pretty much device by device. It was nearly impossible for us to make truly great mobile experiences. This is highly ironic statement given that one of the biggest pain developers trying to build mobile experiences…
Obviously the real driver for "fragmentation" is that there exists a market which is (1) lucrative and (2) easy to enter. So everyone rushes in with their devices and competes. And somehow you think this is a bad thing?
Stated simply: "fragmentation" is a side effect of "market efficiency". The reason almost everyone (for the appropriate definitions of "everyone", of course) in the developed world has a smartphone (be it an iOS one or not) is precisely because of this efficiency. And you can't have it without a little fragmentation to go along with it.
Basically, your utopia where everyone uses one device not only doesn't exist, it can't exist.
Since Sundar Pichai is the head of ChromeOS, perhaps this move is part of a larger move to unify Android and ChromeOS.
> Since Sundar Pichai is the head of ChromeOS, perhaps this move is part of a larger move to unify Android and ChromeOS. I can't see both exist at the same time for much longer, and Android is encroaching on ChromeOS' domain much faster than the other way around. I'm predicting that ChromeOS will be shut down within a couple of years.
Since Sundar Pichai is the head of ChromeOS, perhaps this move is part of a larger move to unify Android and ChromeOS.
> Since Sundar Pichai is the head of ChromeOS, perhaps this move is part of a larger move to unify Android and ChromeOS. I can't see both exist at the same time for much longer, and Android is encroaching on ChromeOS' domain much faster than the other way around. I'm predicting that ChromeOS will be shut down within a couple of years.
Better title "Andy Rubin hands Android team to former Chrome lead, stays at Google".
Earlier quoted context omitted.
>At least on Android you can write one app and then tweak it to work on different devices, previously you had to write apps as different as Android/iOS/Windows for each device - and often individual manufacturers even had multiple platforms to write for. >So I think we owe Google some congratulations. Before Android, you could write a Windows Mobile app and have it run pretty much on every Windows Mobile device and t…
It wouldn't have been adopted if they had taken a hard line on that issue.