On Oct 27, 6:36 pm, jotobjects <[email protected]> wrote: > But sure there is the real world where apps are getting away with > things that are not supposed to work and where changes have side > effects not anticipated.
And isn't finding unanticipated side effects one of the major purposes to beta testing? It's axiomatic that your internal testing will never reveal everything that real users (or in this case, developers) are doing in the field. This isn't just about using undocumented APIs, or even "getting away with things that are not supposed to work." It's about good QA, finding edge-case bugs (regression and otherwise) that your alpha testing just won't. Not to mention improving buy-in from the developer community. My own leading app is seriously broken on 2.0, with at least two bugs in places where I'm NOT pushing the SDK. One is a clear regression bug, the other I haven't tracked down yet. A developer beta of eclair would have turned this kind of thing up. String --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
