I think I'll rather live with some bugs in the SDK than do without it. Overall I think its very good and productive. I also appreciate the fact that it includes features that might be seen as prototypes; I'm a developer I can deal with it, I can decide myself what I want to use.
I never worked with iPhone, so I don't know how it compares. But if their SDK is (perceived as) higher quality , to me that can only mean that they rather hold back on features, than risk getting bad press for quality issues. They may also hold back on features for other reasons, of course. For normal (and closed) software, it's probably a good strategy to be a bit feature conservative. But for me, I'd say if it's useful, then release it. If it's buggy/prototype, then warn me about it, but let me choose. Don't hold back just cause you think i'm not able to handle it. I know all software has bugs, and I can decide myself if something is worth using or not, thank you very much. But again, I don't think the Android SDK has any quality issues worth moaning about. Some minor bugs here and there, nothing major. My $0.02. -- 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
