As you know, Chrome Beta for Android was released just yesterday. But today, our eyes were opened to a few Easter eggs the devs incorporated. It’s nothing too special – but most of all, they were included to show how well Chrome can perform both graphically and under a heavy system load. It’s too bad the application is only available on Android 4.0, they haven’t released any information regarding a possible Honeycomb or Gingerbread release – but we can only hope it’s coming.

We were really hoping to see some new gadgets from Samsung unveiled at Mobile World Congress in Barcelona, but it seems they won’t evenbe hosting press conference this year. They will likely just hold out, and assemble their own conference later on. This is a very ‘Apple-esque’ move, and I wouldn’t be surprised to see it trend throughout other manufactures over time as well.

Lastly, the US gaming population has almost tripled since 2008, and there’s no doubt smartphones have cause quite a bit of this growth. Thus, now that smartphones are much more affordable – we’ll see the amount of gaming adopters eventually start to taper off. There was quite a boom these past three years, and though mobile gaming isn’t the only avenue gamers take – it has been the most progressive.

The first trick is easy enough to pull off: on the smartphone version, tap the Tabs button and slide the tabs up until the foreground tab fills the whole screen. Swipe up quickly and multiple times, and the entire stack will flip vertically, displaying a Chrome icon. This shows off Chrome’s animation power, which you can see elsewhere in the normal interface: swipe the tabs left or right to dismiss them in a circular motion. It’s neat, but mostly useless.

Observe:

The second Easter egg will take a little doing. Open up as many tabs as you can. Then do it again. Notice that the number of tabs is displayed in the address bar. When you reach a total of 100 open tabs, the icon will change to a smiley emoticon. Again, this is mostly useless, but it’s Google’s way of showing off Chrome’s impressive memory management abilities – try opening 100 tabs in the stock browser or any third-party browser and they’ll cry in frustration.

As Chrome for Android is still in Beta, there’s probably at least a few more of these left to find.

[via Cnet]

The biggest change in the new extension is the ability to send links to devices selectively: you can finally pick which Android phone or tablet you need to send the link to. (This seems tailor-made for jaded mobile reviewers who are logged in to a couple of dozen devices at a time – thanks, Google!) You can still use the service to send phone numbers or texts, but wait, there’s more: now the Chrome to Mobile function can also send an offline version of the page directly to your Android device, making it accessible later when you don’t have a connection, such as on a plane or in the subway.

Unfortunately the service isn’t interchangeable with the old Chrome to Phone app, just the new Chrome browser. That means that this new toy is just for Ice Cream Sandwich users for the time being. On the plus side, once the link is sent you can open it in any Android browser - good news for those who aren’t impressed with Chrome Beta’s somewhat lacking initial feature set. Once the connection is set up, you don’t need the old Chrome to Phone on either your desktop or mobile device, so feel free to uninstall them both.

To start I’d like to mention again that this was only released today. It is still in beta although is widely available to the public right now in the Android Market. This is a great start but in some ways it does feel a little like a beta product, but we have a feeling it will grow into much more and soon replace our stock browser for Android. First the bookmark icons don’t display much and the UI is extremely ugly. On the other hand you toss it on a tablet and it looks amazing.

So yes this is very much still a beta (and you see what I mean when it crashes in my video) but for a first try and initial release it’s pretty freaking awesome. I’ll start with the video below in which you’ll see the Galaxy Nexus and ASUS Transformer Prime giving Chrome for Android a try. I cover a few neat new features, the “cards” style tabbed browsing and more.

Chrome for Android Beta hands-on

First, lets talk about Sync. The fact that we can now seamlessly sync from device to device, and from computer to device is awesome. I’ve waited for something this simple for a long time and so far it works great, but I don’t see any settings to tweak this option. In the video you can see it shows the sync between the Prime and the Nexus — showing it was just synced 5 minutes ago. This is awesome and highly impressive. Not only does it show me what I was browsing on the other device, but it loads them in the background and I just tap “devices” and chose what I want. You can run out of the office and be right where you were in a few seconds flat.

Other browsers offer this and Honeycomb sort of had this where it backed up bookmarks, but this real-time live sync is convenient to say the least. I’ve not found a way to get it to manually sync but it seems to check every few minutes. Hopefully more options will be adding to that later.

Next I want to compare a little between the stock Android 4.0 ICS browser, and Chrome. Both are very similar, and are about the same in regards to look, feel, and speed although both have their advantages and disadvantages. Here is a side-by-side comparison.

For one, Chrome doesn’t support Flash as we mentioned earlier today, so that might be a concern for many users. HTML 5 support will continue to grow but in the meantime no flash here, so you’ll have to use something else on mobile if that matters to you.

We also ran a few Sunspider benchmark tests just to see how she performed and I was actually quite impressed. Between Android 4.0 Ice Cream Sandwich and Chrome we scored under 1,900. Most devices in the past struggle to get under 2,100. The screenshot below again shows Chrome for Android on the left, and stock ICS browser on the right (full size images in the gallery below).

Chrome scored 1880 while stock ICS was at 1912. So pretty dead even. Performance across the board seems to reflect a similar result with actual real-world usage too. Overall the stock Android browser has a better and more friendly UI in general, but the few tweaks to tabbed browsing and the “cards” effect in Chrome are awesome. If we could have a nice blend of these two I’d be in heaven. I have a feeling that is exactly where Google is headed — so it’s only a matter of time.

Now to wrap things up I want to mention the lack of “Quick Controls”. A feature in the labs section of the Android browser that I’m missing dearly. Obviously Chrome is its own browser and not integrated into Android, but we have a feeling it will be the main browser in the future. Same goes for the UI. While it has some extra polish, smooth animations, and a decent design it doesn’t resemble Ice Cream Sandwich other than the menu layout. Hopefully this will get blended together.

We have a few issues and shortcomings so far but the awesome features and overall polish make this my new default browser. Syncing everything from my PC over really has sealed the deal for me. Once they work out the bugs, make things a bit prettier, and enhance the overall experience nothing will come close and all those 3rd party browsers will be permanently replaced for me.

Get the Chrome for Android Beta in the link below, and check out the gallery for the rest of our images. Feel free to let us know what you think in the comments below. Do you like Chrome? Will it replace your stock browser on mobile?

Chrome for Android Link

Chrome for Android Beta doesn’t support Adobe Flash and according to Adobe we shouldn’t be all that surprised by that. Within the first few lines of their official comment they quickly got down to what they had to say, and here it is:

Adobe is no longer developing Flash Player for mobile browsers, and thus Chrome for Android Beta does not support Flash content.

They do however mention that they still support flash in the stock browser, and will continue to do so as they promised back in November. Other comments suggest they are actively working to move HTML5 forward, and will continue to support that community, as well as Adobe Air for Android.

Does this come as a surprise to anyone? Will this make you abandon the new and impressive Chrome for Android until we have more options available? Google worked so hard with Adobe to make Flash a feature but quickly things have changed and it will no longer be present moving forward. If you need Flash keep those alternative or stock browsers folks, because Chrome wont be getting it.

[via Adobe]

Google’s intentions to integrate its desktop browser, Chrome OS and the relatively feature-light Android browser have been suspected for months. An important clue to the more practical applications of the project came with the Nexus Prime app leak, which included “ChromeBookmarksSyncAdapter.apk”. The inclusion of a bookmark sync (a feature which mobile versions of Opera and Firefox already have in place) indicates that while a Chrome browser almost certainly isn’t ready for Ice Cream Sandwich, the beginnings of the integration are already well underway.

It’ll be interesting to see how Google positions Chrome on Android, considering that they’re already marketing netbook-style hardware running Chrome as an operating system. While extensions are certainly possible on a mobile browser a la Dolphin and Firefox, some of the heavier web apps probably wouldn’t be practical. Indeed, in the case of popular apps like Angry Birds and TweetDeck, versions already exist for both Android and Chrome OS. In any case, a more powerful native browser can only make Android, and in particular Android tablets, more compelling.

Chrome for Android is still a long way off, and we probably won’t see any major software additions until Android “Jelly Bean” at least.

[via Recombu]

So what in the world does all that mean, you might be asking? First of all you’ve got to know that Popescu also noted the following:

The Android Browser has come to share more and more code
with Chrome (both WebKit and Chromium). This approach has a number of
advantages for the WebKit community:

1. Android WebKit no longer requires a separate build system because
we are able to reuse Chromium’s gyp system for building.
2. Android no longer requires a separate set of WebCore clients,
platform abstractions, and embedder APIs because Android shares much
of this code with the Chromium port.
3. The Android layout tests results more closely match chromium-linux
and more expected results can be shared.

What all of this means is that by bringing the Android web browser code into the Chromium project and therefor making it open source, WebKit developers no longer have to work with two totally different systems. As the Android version of stock web browsing and Chrome web browsing become more and more similar, we can (hopefully) expect a much more optimized experience overall. At the moment, as you may already be aware, Firefox generally turns up better browsing speeds than Webkit, though should “Chrome” come to Android, we may have different results popping up.

If at all, we can expect a Chrome browser for Android inside 2012, more than likely.

[via Webkit.org]

To stay attuned and tuned to everything we’ve got to offer on the Google I/O 2011 set of events, just hit the [IO 2011] portal. You’ll have a generous look at Ice Cream Sandwich, a full guide for the new Music Beta environment from Google, and all the little bits about Android 3.1 for the Motorola XOOM. Also you can head to our newly minted Ice Cream Sandwich forum with its super new logo to discuss any and all questions and concerns you may have for this whole new world!

Also we’ve got a couple more helpers on board today so if and when any Android news does come through, you’ll know about it first, from every single perspective you can imagine! Meet or re-meet our animal assistants:

Susi and Millie you’ll remember from recent reviews of Android devices in videos and photos. Susi’s been in photos since back at the launch of T-Mobile’s G2, and Millie is a new player.

This is the first of many keynotes and announcements and talks we’ll be having with and on Google’s biggest event of the year for developers (aka their biggest event of the year period.) We’re expecting some huge Android news, some huge news on Google Chrome both as a browser and as an OS, and some new devices to be revealed here and there MAYBE. We’ll see.

To stay attuned, follow our twitter at @androids, see our Facebook page at http://www.facebook.com/AndroidCommunitycom, and follow the keywords right here starting with [IO 2011!] We’re pumped up – you get pumped up too – we’ll all freak out together! Also feel free to follow along right over here for a live stream of this first event.

The Keynotes themselves will be wall to wall about Android and Chrome, so there will be a lot to talk about. There’s a ton of buzz that we’ll hear more about the latest flavor of Android for handsets known as Ice Cream Sandwich. Google will likely also talk about the updates to the Android Market as well. Other topics will include Google TV and Chrome.

As a compliment to the coverage on AC, users can also download the official Google I/O app from the Android Marketplace. We did a detailed breakdown of its features here, and it’s sure to be a great way to follow speeches, official bulletins, and catch the official Google I/O twitter stream as it happens. Then, come back to AC for in depth analysis, a bevy of hands on reporting, and breaking news from inside the event! Don’t miss a minute!

Google I/O: countdown to the keynote kickoff

In less than 24 hours, we’ll be kicking off Google I/O 2011, our annual developer conference here in San Francisco. With more than 5,000 participants from 60 countries, including 110 sessions, 261 speakers and 152 Sandbox partners, this year’s I/O will be the biggest one yet.

This year’s keynote presentations will highlight the biggest opportunities for developers and feature two of our most popular and important developer platforms: Android and Chrome. Google engineers from Andy Rubin and Sundar Pichai’s teams will unveil new features, preview upcoming updates, and provide new insights into the growing momentum behind these platforms.

Plus, for the first time in Google I/O history, you’ll be able to join us throughout the two days at I/O Live. We’ll live stream the two keynote presentations, two full days of Android and Chrome technical sessions, and the After Hours party. Recorded videos from all sessions across eight product tracks will be available within 24 hours after the conference. Whether you’ll be joining us in San Francisco or from the farthest corner of the world, bookmark www.google.com/io and check back on May 10 at 9:00 a.m. PDT for a fun treat as we count down to 00:00:00:

If you’re attending the conference this year, we can’t wait to meet with you and share our vision for the future of web and mobile development. If you aren’t able to make it this year, you can continue to follow us on the Google Code Blog and on Twitter (#io2011) over the next two days as we share photos, videos, news, and recaps of the event. It’s going to be an exciting 48 hours!

Vic Gundotra, Senior Vice President of Engineering

A few short years ago, in 2009, the conference initially sold out in ninety days.  But the near instant sell out of the conference only underscores the wide reach that the Android platform has on developers who are itching to get an inside look on what’s on the horizon in mobile, web, and Google labs applications.   In addition to the keynotes and topics covered, there will be a wide range of developers showcasing applications based on Google technologies in the Developer’s Sandbox.

And although all tickets have been sold for the conference, Android Community readers can take comfort in the fact that we’ve successfully reserved our spot and will be there bringing you the news as fast as we get it!

The Google I/O 2011 will be held May 10-11, 2011 in San Francisco, CA.

[via @VicGundotra of Google I/O on Twitter]

Now although this is just a prediction, it brings up an interesting point. When Google noticed that Android was being used for tablets, they started development of a tablet optimized operating system (Honeycomb). They may just do the same, or something similar, and build an optimized version of Android to be used on notebooks if Chrome OS fails to launch successfully.

What do you think about the Chrome OS as a whole? Do you think it would be better replaced by an Android-based OS? And, if you’d like to test drive the operating system for yourself, remember that we are giving away two Google Chrome Cr-48s!

[Via ChromeSpot]

They say they’ll share some exciting news about Chrome – maybe something along the lines of an expansion the size of a whole OS? That’d be madness. Be over at SlashGear (and more than likely here at Android Community) during the time we’re there because we’ll surely be sending out the news as fast as we get it! Excitement!

UPDATE! A new message has been sent out adding info surrounding the event, including the URL where everyone can check out the live event:

On December 7, we will host an event in San Francisco where we plan to share some exciting news about Chrome.

The event will be webcast live on YouTube at: www.youtube.com/googlechrome. Mark your calendars for 10:30 a.m. PST and tune in.

Thanks!

[Via SlashGear]

Last night we saw the introduction of 4 Google-Android-Chrome equipped TVs. The end result: Flawless. Utilizing all of Google’s available technologies clearly worked and the end product was stunning both with it’s hardware and software. People are speculating that this integration of all of Google’s offerings truly makes the product. We may see this on products in the future, launching with the best features of Android and Chrome OS to make a unique netbook or tablet experience.

“We are very happy with the progress of Google Chrome OS and expect devices will be available later this year. We’ll have more details to share at launch.”

With Chrome finishing up in development, it has been confirmed that we will start seeing it on devices later this year and before January 1st 2011. What does this mean for Android Market Share? Well we do not know as of yet, it could be another way to boost brand recognition, or even take some market share away from the Android platform. But how could we complain about an operating system built for devices that it will run on? We will see how it all turns out later this year.

[Via Phandroid]

Speaking at a press conference this week, ostensibly to discuss the new netbook platform but which covered various points of Google’s business, Schmidt and company founders Sergey Brin and Larry Page discussed the open-nature of the new platform.  While in their initial blog post about Chrome OS they indicated that it and Android would remain separate, and that “choice will drive innovation for the benefit of everyone, including Google”, there now seems to be signs that the two will shift from parallel to integrated projects.

The trio also discussed the nature of open-source software and how they do not envisage Chrome OS as a direct competitor to Windows.  In fact, Schmidt said, “Microsoft is welcome to put Internet Explorer on our operating system,” but that “it’s highly unlikely they would do it.  They would have to port it and the port is not trivial … the ball is in their court.”  Referring to Google’s well-known “do no evil” pledge, he highlighted the fact that because Chrome is open-source “even if we had an evil moment [to block out Microsoft], we would be unsuccessful.”

The first netbooks running Google Chrome OS are expected in the second half of 2010.

Acer, Adobe, ASUS, Freescale, HP, Lenovo, Qualcomm, Texas Instruments and Toshiba are all named, though Google says these are “among others”.  Notable by their absence are Sony and Dell, as are Samsung; the latter has obviously invested in Android, as it is about to launch the I7500 Galaxy, and has a well-received netbook range.

The search giant has also re-confirmed that Google Chrome OS will be a free product for end-users, and made open-source later on in the year.  Actual shipping products based on the OS – which has been described as the Chrome browser sitting within a new windowing system on top of a Linux kernel – aren’t expected until the second-half of 2010.

Google Chrome OS will first appear on netbooks in the second-half of 2010, with the search giant apparently already in talks with manufacturers regarding distribution.  Prior to that, however, they will make Chrome OS open-source later on in 2009, allowing developers to get to grips with the platform.

Since most of the user experience will take place on the web, with users interacting with web-apps, developers will be able to use existing coding skills to create software that not only runs on Google Chrome OS but any standards-based cross-platform browser.  As for Android, that remains a going concern for Google, with the company suggesting that “choice will drive innovation for the benefit of everyone, including Google” in the areas where the two platforms overlap.

As both Android and Chrome near their 1.0 releases, it is expected the two will begin to work together, even though they were developed mostly on separate terms. “Probably a subsequent version of Android is going to pick up a lot of the Chrome stack,” said Brin and cited JavaScript improvements as an example.

And “Chrome-like” is an example of what the mobile version of Chrome would be called in order to indicate both its relation to the full blown PC version and its mobile status. The age of complete mobile browsing is upon us!

[via Webware at CNET]