Am I the only one who doesn't see what all the fuss is about Google Voice? Seems like it's been way overhyped. The theoretical ideal is fantastic, but I think many of the people raving over that have not actually tried it end-to-end. I was surprised with how poorly the Google Voice Android app is integrated with Android. Now that I got a Droid Eris I figured I'd finally switch over to my GV number since the experience should be top-notch on Android. Not so. Are there any Google engineers working on GV for Android that are reading this and can give us more info on whether you plan to release some much needed bug fixes soon and better feature integration? The GV blog has not really mentioned the GV for Android app since July 2009. FYI I am using GV on my Eris, but in Voicemail only mode. Here's a list of reasons I could not use GV for Android with my GV phone number as my primary and sole phone number: - Bug: GV for Android crashes upon bootup start sequence on Droid Eris. - Bug: GV for Android does not associate with your contacts unless you enter their phone numbers with +1 at the beginning. I can go through and do this on my 100+ contacts but GV should handle this scenario automatically. - Perf Bug: GV for Android loads generic contact picture first and then loads actual contact picture. Has noticeable lag. - Bug: GV for Android does not integrate with Messages app. SMS received to your GV number gets mirrored to Messages app with the Google 406 #'s. GV should auto-associate it with the corresponding contact info and contact photo. - Bug: GV app does not integrate with Contacts (People app). Received text messages do not get shown on the Messages tab of the corresponding contact. - Bug: requires a data connection to send or receive phone calls or SMS. For sending, GV should route over the cellular network by calling the GV access number when data connectivity is not available. - Feature: GV for Android should have real-time / push notification of new text messages. I heard the team is working on this. Can you give us any details on implementation and impact on battery usage? I don't care about this feature much if they fix Messages integration. -------- Then there are a few issues related to GV in general (not specific to the GV for Android app) that need to be resolved before I could use GV as a primary number: - Call quality and reliability issues. GV forums show people have been having problems with calls and reliability. Not worth sacrificing your basic phone functionality in order to get visual voicemail + backup. - Lose number portability privilege. This is a policy decision Google has made, and I doubt it will ever change. It's just something to keep in mind - with an MO (mobile operator) you have the right, granted by the FCC, to port your number. With a GV number you have no such right/privilege and if you ever become dissatisfied with GV you have no way to leave and still keep your existing number which all your friends and business associates have in their contact lists. - Adds an intermediary, additional failure point which can impact reliability. With an MO phone number your call routing is MO -> MO. With GV it is MO -> GV -> MO. I'd love to see some information from GV on how reliable/redundant their routing is, and an SLA (service level agreement) to a certain uptime. Anyway, sorry for the dissertation, but I haven't seen all of these topics brought up yet and I think it's valuable feedback to the GV team to know what areas could use improvement.