Google Archive

There's another interesting thing happening here. If you take a look at stock Android 4.3, you will see that the current launcher's package name is com.android.launcher. The new one is com.google.android.gel. Now look at Google's current selection of apps in the Play Store. Almost all of them start with "com.google.android" instead of "com.android."

I'm not saying with 100% certainty that we're going to see the launcher released to the Play Store, but to me, it certainly looks like it. At least eventually and not necessarily with KitKat.

Chrome OS is extremely purpose built and it is something that should bring about great concern to those at Microsoft. I personally don't have a problem with Windows 8, but purpose built is hardly a phrase that applies to the OS - at least if you're talking about it on a more traditional PC. I suspect by the time we get to Windows 9, Microsoft will have a better answer to the critics of 8/8.1, but that gives Google and its Chrome OS partners at least another year of marketshare erosion. At the beginning of this mobile journey I remember x86 being an advantage for Intel, and we all know what happened to that. Similarly, I remember Windows/Office being advantages for Microsoft. If Microsoft doesn't find a quick solution for making low cost Windows PCs just as well executed as Chrome OS devices, it'll find itself in a world where Windows no longer matters to entry-level/mainstream users.

Until now, Chromebook buyers have had to make a choice. You could get either a cheap laptop with cheap components or the premium-but-ridiculously-expensive Chromebook Pixel. When Google says that HP's new $279 Chromebook 11 is 'inspired' by the Pixel, it's not about components - the Chromebook 11 lacks the high-resolution touchscreen, the high-end Ivy Bridge CPU, and the solid aluminum construction - the Pixel's banner features. Rather, it's about making a laptop that makes enthusiasts happy without the Pixel's sticker shock.

Until now, Google hasn't talked about malware on Android because it did not have the data or analytic platform to back its security claims. But that changed dramatically today when Google's Android Security chief Adrian Ludwig reported data showing that less than an estimated 0.001% of app installations on Android are able to evade the system's multi-layered defenses and cause harm to users. Android, built on an open innovation model, has quietly resisted the locked down, total control model spawned by decades of Windows malware. Ludwig spoke today at the Virus Bulletin conference in Berlin because he has the data to dispute the claims of pervasive Android malware threats.

Starting today we’re making Quickoffice for Android and iOS available for free, for everyone. With Quickoffice, you can edit Microsoft Office documents across your devices, giving you the freedom to work with anyone no matter what hardware or software they’re using. Plus, it’s integrated with Google Drive storage so you can safely access your files from anywhere.

The new apps look and behave much like the native apps you find on Windows and OS X. They're built using web technologies, but also with Chrome-specific code that means they won't be able to run on other web browsers - they're truly Chrome apps. They can exist outside of your browser window as distinct apps, work offline, and sync across devices and operating systems. They can also access your computer's GPU, storage, camera, ports, and Bluetooth connection. Chrome Apps are, for now, only available through Chrome on Windows or Chrome OS on a Chromebook. Mac users will have to wait another six weeks before their version of Chrome will be updated.

Google's strategy is clear. Play Services has system-level powers, but it's updatable. It's part of the Google apps package, so it's not open source. OEMs are not allowed to modify it, making it completely under Google's control. Play Services basically acts as a shim between the normal apps and the installed Android OS. Right now Play Services handles the Google Maps API, Google Account syncing, remote wipe, push messages, the Play Games back end, and many other duties. If you ever question the power of Google Play Services, try disabling it. Nearly every Google App on your device will break.

Noticed any differences when using Google's Hangouts video chat lately? If you did, then you may be one of the lucky users who has already received an upgrade to 720p HD video. The company quietly started to roll out HD for Hangouts to a subset of its users in the last few weeks and hopes to complete the rollout soon. But the change isn't just a quality upgrade - it's part of a bigger move towards open standards that will eventually bring us video chat in the browser without the need for any plugins.

To enable HD, and prepare for this plugin-free future, Google quietly started to transition Hangouts from the H.264 video codec to VP8, an open and royalty-free video codec the company released back in 2010. Google's Vice President of Engineering Chee Chew told me during a recent interview that the switchover from H.264 to VP8 should be more or less invisible to consumers, with some possibly noticing a little less choppiness. "It will be cleaner, better video," Chew said.

Apps and their ads must not add homescreen shortcuts, browser bookmarks, or icons on the user's device as a service to third parties or for advertising purposes. Apps and their ads must not display advertisements through system level notifications on the user's device, unless the notifications derive from an integral feature provided by the installed app. (e.g., an airline app that notifies users of special deals, or a game that notifies users of in-game promotions).

Early this morning on Google+, he showed off his latest project, which will allow any audio or video file to be casted to your TV using a CyanogenMod-powered device and the Chromecast dongle. In his demo above he shows it off using the Twit.TV app, but he explains that the process should be the same for any media you can play through any app.

Well, I see that people have figured out why I'm quitting AOSP.

There's no point being the maintainer of an Operating System that can't boot to the home screen on its flagship device for lack of GPU support, especially when I'm getting the blame for something that I don't have authority to fix myself and that I had anticipated and escalated more than 6 months ahead.

That feeling when lawyers sabotage the launch you spent 6 months working on? I haz it. Sad sad sad sad sad sad.

But once I used the phone heavily, I started to come around to the Moto X in a way I hadn't expected. The additions to the software that Motorola has made are legitimately useful and really quite impressive. They add to the experience of Android without removing what is most vital in Google's software, unlike the competition, which seems intent on obscuring what's already a sophisticated and beautiful operating system. If Motorola ends up producing a Google Play Edition of this phone that retains the customizable hardware and software additions like Assist and Active Notifications - this could be as good an option as the S4 or One.

And the phone is nice. I mean, really nice to use. It's a reminder that the way something is built can be as important as what it's made of.

If I'm right in reading between the lines of Google's marketing speak, the Moto X was made in the image of the everyman. The 4.7-inch screen size, the curvature of its back, the composite materials, its weight and front-face look were focus-tested for maximum inoffensiveness. The Moto X exudes no tech halo like the Galaxy S 4 or the HTC One because it is the sum of averages. Here's how I see it: You know those people who own iPhones, but don't know which model number they own and also refer to all Android phones as Droids? This phone is for them.