On the night before Google I/O 2011, I posted an open call for any questions you might have had for Google core developers. And you delivered - within a few hours, we had over 50 questions of varying complexities, and I realized I was in trouble. Office hours are meant for developers asking dev questions, whereas most of the ones you've asked were about policies and availability. Still, I proceeded to ask away at office hours and at the end of each session, fearing being shunned forever.
We've all griped about Facebook for Android before, and rightly so. The app still trails the functionality of its iOS counterpart, and has had a string of compatibility issues. Just last week, Joe Hewitt - one of the developers of Facebook for Android - left the company. It appears that things are already being shaken up; the Facebook for Android team has taken to Andreddit to ask how they can make the app better.
Motorola has had a dark past when it comes to bootloaders. Apart from a couple exceptions (most notably, the XOOM), all of the major Motorola devices have had locked bootloaders, and thus, Android customization enthusiasts have been shut out from such tweaks as custom kernels.
I love Reddit. Like, alot. I also love Android. So naturally, I get pretty excited about new Reddit apps for Android. There are quite a few of them out there to choose from, ranging from full-on Reddit readers like Reddit is Fun, to purpose specific apps, like RedditTV or Reddit Pics. The holy grail of Reddit apps is a browsing app that has all of the functionalities of the web Reddit experience, while being easy to use and good looking.
Among all the awesome (or really bad, depending on your mood) April Fool's jokes today, Google's web form for submitting Android Market copyright infringements towers above all, especially considering it's not a joke, at all. We really doubt that it's intentional because this behavior was present before April 1st arrived to California, and it is mind boggling that something like this would fall through the cracks and get past Google's Quality Assurance.
On March 22nd, the long awaited Amazon Appstore was released, bringing a whole new way to find, install, and share apps on Android. After its initial debut, we decided that this new Appstore was the real deal. In this post, we'll break down what Amazon's done right, and what it still needs to improve on.
1. Better descriptions and more in-depth comments
Most users will tell you that finding good Android apps is not an easy task.
February 2nd was an exciting day for Android fans - we were given an in-depth preview of Honeycomb, laid our eyes on some stunning 3D tablet games, and were even treated to a much-anticipated online version of the Android Market. But 2/2/2011 was also the fateful day that spelled "doom" for lite / demo versions of Android apps, as Google unveiled their new in-app billing system.
Today, Google made another announcement regarding in-app purchases: the feature will launch publicly next week.
Conspiracy theorists would have you believe that the ThunderBolt's signed (and locked) bootloader was all Verizon's doing, but it appears that isn't quite the case - the Incredible S, one of HTC's unlocked GSM phones, is shipping with a similar failsafe system. That basically means no custom ROMs for you (at least until a viable workaround is discovered).
Proof? Look no further than the contents of this Incredible S RUU:
From what our friends at AndIRC can tell (note that they don't have a device in hand), the Incredible S includes a signature check much like the one on the ThunderBolt.
Amazon's upcoming Android Market competitor, the Amazon Appstore, is in hot water for its namesake. On Monday, Apple filed a lawsuit in a California federal court claiming Amazon had infringed on its trademark of the phrase "App Store." Apple applied for a trademark to this name way back in 2008, but it wasn't approved until January of 2010. Since then, Microsoft has filed a dispute with the trademark office alleging that the grant was improper.
When you think of Android's openness, what comes to mind first? Is it the open source code of AOSP? Or maybe nearly 200 devices that run the Android now? Perhaps tethering, built right into the OS? How about the GPLv2 license requirement for manufacturers to publish all changes to the Linux kernel simultaneously with each phone's release?
If you are a custom ROM developer or even user, that last bit there probably occupies one of the top positions, and rightfully so - without it, proprietary changes to the kernel would remain hidden and would need to be reverse engineered.