When you set out to map the entire Earth, if you do it right, you're going to end up with a lot of data. Google Maps has a constant stream of information coming in from a ton of sources - its own Street View cars, satellite imagery, governments, and users all over the world. Once you have all of that information, how do you deal with it? What happens when the government map doesn't perfectly match the satellite image?
Google I/O is coming! We'll know about all of Google's new projects in just 2
short agonizingly long weeks. While we desperately count the days until May 15th, we thought it would be a great idea to take stock all of the things we've caught wind of lately.
Calling this an "I/O Preview," sounds a little too certain. I'm not predicting everything here will come out at I/O, this is just a list of everything we know Google is working on - their "To-Do" list.
A few months ago I wrote "Stock Android Isn't Perfect," an article where I turned my usual harsh UX critique on stock Android, instead of just picking on TouchWiz and Sense all the time in my reviews. The article went over pretty well, and even got a few responses from Googlers! I didn't cover everything that was wrong with Android, though, and there have been a bunch of updates since the original article, so it's about time I wrote a sequel.
If you've ever found yourself lost in Singapore or Hong Kong, then I'm sorry. I hear that if you run into the wrong part of town things can get... bad. It's a shame you didn't have Google Navigation to save you the trouble of ending up somewhere you shouldn't be. The good news, though: future wanderers won't have to suffer your potential strife, because Google Nav should now be available in the aforementioned places.