That's what I'm talking about ! We do not know, where problems are, when software works on "clean Android" and do not works on some devices.
For example: Hero's UI's is BUGGY as hell (for example, keyboard events are not fired correctly). Another example: why Samsung's GPS is working not the same as in SDK, G1, Magic and Hero ? Why it does not fires all GPS events properly ? These small differences often make our apps unusable. Besides, (Dianne), just look at Market ! Read comments of users of Google Maps or other Google apps. There ARE a lot of users reporting FORCE CLOSE for some Google Apps. It is not just a "my" app problem. It is a whole Android platform problem. I do not know, maybe some bad design, or just maybe platform is "too open" for every stupid mutha.. sorry, phone manufacturer. I know, they are not interested in creating really nice working, 100% Android compatbile device. They just want to grab our money. So, if Google's applications are force closing.. how the hell, my app could be better ? It could not. Programming Android is funny, but testing your code, making it run on every device available, is going to be MISSION IMPOSSIBLE, especially for small developers. Waste of time. On 19 Sty, 09:32, String <sterling.ud...@googlemail.com> wrote: > Problem is, half the time we don't know. Users post 1* Market comments > saying "Force closes on Droid" or "Doesn't work on Samsung Moment", > and unless you have that specific handset to test on, you're SOL. You > "sanity check" on an emulator instance of the same resolution and OS > version, and nothing is obviously broken, so where do you go?
-- 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 android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
