Matt Buchanan shared this video of the new Android build to coincide with the HTC Hero (new Android handset).  It is incredible.  Check it out:

According to TBG the second version of the G1 will be called Bigfoot and replace the existing hardware provided by HTC.  Lots of users like the slideout keyboard of the G1, but they wanted a little sexier hardware – Bigfoot provides that hardware:

The driving force behind Big in Japan is largely due to the success of ShopSavvy (our barcode scanning/price comparison application for Android).  In turn the success of ShopSavvy is due in large part to our relationship with Google.  We hope that we have played a small part in the success of Android – Google’s mobile phone operating system.  I was surprised, and humbled, when I noticed that Sergey Brin wrote about ShopSavvy in the latest Founders Letter published today.  Each year Larry and Sergey take turns writing an annual letter – this is the first time one of our projects has ever been mentioned!  Check out the full letter here.  I just wanted to take a minute to thank Larry, Sergey, Eric and Dan for supporting Android and our development efforts – we really appreciate everything you have done!  Keep up the great work.

Wow. Who knew. Via.

Everyday there is another report of yet another Android handset headed to the market.  Today is no different.  Check out the leaked image of the latest Android phone from HTC (via our friends in Singapore):

Our first release compatible with Cupcake is available for beta testing.  If you agree to beta test, find and report a bug first and send us your address we will send you a Big in Japan t-shirt for your trouble.  Download the APK for ShopSavvy here: http://tinyurl.com/sscupcake.  Send bugs to support@biggu.com.  Thanks for your help!

UPDATE: To be clear, we are Android-fanboys here at Big in Japan.  We love Android and the Open Handset Alliance.  We are NOT bashing Google or the OHA.  Also, we have been asked to clarify two points: a) an early look Cupcake SDK was released two weeks ago and b) the Magic with Cupcake has not been released to endusers (only reporters have the new handset).

Now I will respond:  The early look SDK wasn’t a release candidate like the 1.5 SDK release pushed last night.  Most developers do not port existing applications to a pre-release SDK.  I believe two days between release of the current and final SDK to public release is not enough time.  Second, we are talking to reporters in Europe who have the Magic with Cupcake and who are writing reviews as we speak.  They are trying to use ShopSavvy, but are frustrated by its incompatibility.  We got up this morning to find emails from these ‘users’ only to read that we had two days to port ShopSavvy.

Well, that is my assessment this week – next week everything should be great (I hope).  Yesterday Google FINALLY released the latest version of Android – Cupcake 1.5 to developers.  ShopSavvy, like many other applications, won’t work with Cupcake automatically.  We began porting ShopSavvy almost immediately.  This new version of Android breaks most applications including ShopSavvy requiring an extensive port.  This wouldn’t be so bad if it weren’t for three issues:

• Cupcake will be pushed OTA to users two days from now (according to cnet UK)
• Cupcake is already live in Spain? WTF?
• Android Market does NOT let you target specific build to different versions of applications.

Let me address each issue in order.  First, two days to port applications to a new operating system?  Really?  Does that make sense?  Third-party developers like us must BUILD and TEST within two days?  I would recommend NOT making a fundamental change to your operating system without giving developers a little time to build and test – how about a week or two?  Of course Vodafone decided to go live with Cupcake in Spain at the exact same time developers got Cupcake – I won’t bother making any further comments about that genius idea.  Finally, some of our users won’t upgrade to cupcake and as we learned today, the Market won’t support targeting specific builds with specific versions of applications.  As a result we must make ShopSavvy backwards compatible with older versions of Android.  This might not sound difficult, but porting to cupcake is a task that would take a week or two of development and at least a week of beta testing.  Add in the requirement that it must be backwards compatible adds another week of development.  But alas, we must do all of this work in two days.

The good news is that we will release our new version whenever Cupcake is pushed OTA to users.  The bad news it will be untested.  It will have bugs, bugs that we will fix.  Please bear with us and realize that we don’t have much choice in the matter.  My biggest concern is that we are better prepared than most.  How many applications will go unupdated or tested?  Will new Android users assume Android sucks when all of the applications force close?  Perception of the market is key to Androids success – it seems like in a rush to be first Vodafone is risking tarnishing the Android brand.  Google?  Can you save Android?