I for myself found the help given in this forum quite ample. For most of the questions I came across there were already useful answers in the forum. I tried not to work against Android, but tried to see what is possible and implement features based on that. (for example, I would not have tried to fix the key mode / touch mode issue creating workarounds for the m5 behavior, as this is really something the Android team has to clean up. And if they finally change this behavior, all workarounds are useless anyway.)
I profited a lot from the samples that were given, for example on the media player. What I do not understand is that certain features that worked in m3 and broke in m5 have not been fixed earlier, like sound recording. I understand that Android itself is probably still undergoing massive refactoring. But it may not have been too much effort to keep a separate branch of m5 where the most critical bugs could be fixed in parallel to the work going on for future releases. In this sense, the Android team sticked to the Google code hosting motto ( http://code.google.com/hosting/ ) "release early, release often" on the first part - they indeed released a pre-alpha SDK - but I personally think they could have done better on the "release often" part. After all, fixing some bugs may help to uncover others that are still hidden. So to make most use of the "challenge" period where many programmers work with the SDK, even a weekly bugfix update of the SDK would not have been too often. I don't know whether another update would be released before the challenge deadline. Given that it less than 2 1/2 weeks from now, I'd say it is rather unlikely that many developers will risk having to debug their programs from scratch again - so another round of potentially valuable feedback got lost here. It is quite predictable that the interest will decrease after the end of the first deadline - but there is still challenge II. So let's see how things develop. Peli On Mar 27, 3:51 pm, Anil <[EMAIL PROTECTED]> wrote: > Please post your opinion: > For me, I am disappointed. There must be scores of Google-Android > employees dedicated to this project, but only a handful help out in > the forums (digit, hackbod, megha, romain) in their free time. > Sometimes I am stuck for days and have to create application > workarounds. > > Most of the people helping are ordinary developers like us helping > each other out. > Sometimes I wonder if Google is exploiting us in this whole Android > project. > Google, please don't exploit us, instead help us! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] Announcing the new M5 SDK! http://android-developers.blogspot.com/2008/02/android-sdk-m5-rc14-now-available.html For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
