As a IT Architect working for several fortune companies, I can very well appreciate the prioritization process that is required to manage defects.
My concerns here is that this was "low-hanging fruit" and should have only take one (1) developer about an hour or so to resolve. My clients concerns regarding this it affect their ability to manage customers with the same phone numbers. All they really wanted was an ETA on the resolution. They might have been fine if it was another 6-9 months, however, what was not acceptable to them was the Google's inability to provide basic communication on a defect that affected them. Again, don't get me wrong... I want Android to succeed. I think its got great potential, but someone has to pay attention to functional and usability aspects so something this dumb doesn't doesn't end up in release software again. -Derek On Jul 23, 1:04 pm, Romain Guy <[email protected]> wrote: > The Android team is responding and resolving basic usability issues, > and even non-basic ones, etc. Unfortunately, and believe me when I say > we're sorry about it, we *cannot* fix *every single* bug. Some bugs > are fixed right away, some take more time. > > > > > > On Thu, Jul 23, 2009 at 10:58 AM,dotclick<[email protected]> wrote: > > > Good point... and I probably deserve the criticism. > > > However, your comments only strengthen my original point of GOOGLE is > > not responding and resolving basic usability issues. This is one of > > the key reasons why a company I work with made the decision today to > > dump 100+ Android G1 phones that are only 9 months old and order non- > > Android phones. > > > -D > > > On Jul 15, 5:30 pm, Mark Murphy <[email protected]> wrote: > >> dotclickwrote: > >> > So the only response I am going to get from Google is from someone who > >> > didn't read the message or take the time to research it. > > >> No, the only responses you will get is from people other than Google > >> employees. As Romain Guy pointed out, if you read the response you were > >> lambasting, you would notice that it is from a T-Mobile employee. > > >> It seems curious that you seem to have made the same error that you are > >> complaining about -- not completely reading the email. It's almost as if > >> making mistakes were, like, human or something. > > >> Of course, it is also curious that you appear to think this is an > >> end-user tech support forum (which it is not) and that it is Google's > >> primary responsibility to respond to you here (which it is not). > > >> But I digress. > > >> > No status updates or responses on the bug report from 7+ months ago. > > >> Please point out the official public bug trackers for Windows Mobile, > >> Blackberry, iPhone, and Palm WebOS. I'm not even sure there's one up for > >> Symbian, and they're at least on the road to open source. > > >> Please point out where you get detailed, bug-level information months in > >> advance of product releases for Windows Mobile, Blackberry, iPhone, Palm > >> WebOS, and Symbian. > > >> Please point out how you -- whether via your own engineering efforts, or > >> by hiring somebody, or by collecting interested people to raise money to > >> hire somebody -- have a chance to fix bugs in Windows Mobile, > >> Blackberry, iPhone, or Palm WebOS, as you can with Android. I'll give > >> Symbian a mulligan here, since they're in progress on this issue. > > >> Had this same bug, or an equivalent one, affected you on one of these > >> other platforms, the best-case scenario is that, after sitting in > >> indefinite tech support queues, you would be told it is a bug and it may > >> get fixed someday. Here, not only were you able to file the bug report > >> without much effort (albeit with no better of a response), but you have > >> options for spearheading a fix, which you lack with any other > >> commercial-grade smartphone platform. > > >> Now, you may not elect to use any of those options to accelerate a fix, > >> but that's your decision, not Google's. Regardless, you are no worse off > >> than you would have been with any other platform with the same sort of bug. > > >> If you want to whine about how Android has bugs, be my guest, just don't > >> whine about the lack of response, since that's all you'll get from anyone. > > >> Note: once Symbian gets a-rollin' in earnest on the open source front, > >> the bar for Google and Android may get raised a fair bit, but we're not > >> there yet. > > >> -- > >> Mark Murphy (a Commons > >> Guy)http://commonsware.com|http://twitter.com/commonsguy > > >> Android App Developer Training:http://commonsware.com/training.html > > -- > Romain Guy > Android framework engineer > [email protected] > > Note: please don't send private questions to me, as I don't have time > to provide private support. All such questions should be posted on > public forums, where I and others can see and answer them --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
