Google I/O, a conference dedicated entirely to Google technologies and hosted in San Francisco's Moscone Center, is fast approaching, and Google today opened up early registration to key developer partners and 2010 I/O attendees. Early reg, available to the first 1500 people who complete it, costs $450 ($100 more than last year). Don't worry though - when it goes public next week, the price is going to stay the same until April 17th, at which point it will go up another $100 to $550 (thanks for the correction, Philip!).
Although, the Android Market has exploded recently, it is no secret that apps on the iOS platform consistently look and perform better. With revenues from mobile apps set to triple this year, Google is going on a mass hiring spree to find developers to create quality apps for the Android Market, reports the Wall Street Journal.
Google, like Apple, takes a 30% cut for every app sold in the Market. However, with paid app sales failing to live up to expectations, Google is hoping to increase its revenue stream by improving the overall quality of the apps available in the Market.
Just a few weeks after Android became the number one smartphone platform in the US, Canalys is reporting that strong sales of Android devices in Q4 2010 has helped it overtake Nokia's Symbian OS to became the world's best selling mobile platform.
33.3 million Android-based devices were sold globally in Q4 2010, compared with 31.0 million Symbian-based phones and 16.2 million iPhones.
Android's growth is astonishing. In Q4 2009 it sold a mere 4.7 million units, a year later shipments have jumped by over 600%.
A new report from eWeek came out today stating that another researcher, Xuxian Jiang, this time from North Carolina State University, stepped forward with a tweak to the very same vulnerability Google reportedly patched.
Next Wednesday, Google will be holding a press event to showcase Honeycomb and discuss Android at large. Team Android is going to give attendees an "in-depth look" at Honeycomb, news regarding the Android ecosystem, and a number of hands-on opportunities while at Google headquarters in Mountain View.
The presentation will be streamed live at www.youtube.com/android starting at 10AM next Wednesday, so everyone will get a chance to tune in for the latest and greatest in the world of Android and Honeycomb.
Ah, the power of open. A team of people (mainly developers) has come together to develop a new communication method for times when existing infrastructure just doesn't work. They've come up with two systems:
The Serval Project consists of two systems.
The first is a temporary, self-organising, self-powered mobile network for disaster areas, formed with small phone towers dropped in by air.
The second is a permanent system for remote areas that requires no infrastructure and creates a mesh-based phone network between Wi-Fi enabled mobile phones, and eventually specially designed mobile phones that can operate on other unlicensed frequencies, called Batphone.
Honeycomb is one of the biggest updates in Android history, so naturally, I jumped at the chance to try it out via the newly released Android 3.0 "preview SDK." What I found certainly wasn't disappointing - though it's important to remember that this is just a preview, meaning that not everything is in working order (for example, the emulator is so slow it made me want to tear my hair out at times, not to mention the frequent force close messages).
Buried deep in the depths of the Honeycomb SDK that was released yesterday, this Tron-inspired Honeycomb logo, which, as we later found out, was actually part of the Honeycomb Easter egg. Whether this logo is THE Honeycomb logo or not remains to be proven, but it is definitely official, as it came straight from the SDK. Judging by my reddit submission, many of you liked it quite a bit but had ideas of your own of how it could be modified to be more in tune with the Android theme.
The Honeycomb SDK preview, allowing everyone to take a peek and play around with Honeycomb using the Android emulator, was launched yesterday, but after we got past the initial excitement, we found that the emulator itself was dog slow and pretty much unusable. In fact, it was so frustrating to use it that I wanted to punch walls and rip out my hair after 5 minutes with it. And I'm not even going to talk about orientation problems - how the Android team managed to ship the SDK with orientation broken by default (there is a fix for it in the Settings > Display) is beyond me and beyond the scope of this article.