Not to take this off topic too far. I get the impression that the variances are mostly driven by differing hardware. Which event is fired when at what sensor value, stuff like that... I've seen this on the DROID, Behold and the LG 2. They all have a variety of detail issues with elements such as the camera preview or differences in the way sensor events fire. I am also under the impression that carriers are messing with the Android internals. Example: On the HTC Hero, one of my apps runs just fine when distributed by a carrier in Slovakia, while Portugal and Sprint are a no-go. Force Close! One Star! I assume some carriers mess with the formula more than others. I've already written off that one app for now, except as a test bed where I push the envelope and make users try out stuff ahead of the main app, the one that I'm still interested in sustaining... Not ideal, but in the face of the different carriers ROMs and various devices, this is just slipping away and I just won't stress over this, not in light of the earnings potential of the whole app development affair. Looking at the big picture, so to speak.
On Nov 17, 11:50 am, Brian Conrad <[email protected]> wrote: > Quite an article over on Wired about the frustration of developers with > the exploding number of Android > devices:http://www.wired.com/gadgetlab/2009/11/android-fragmentation/ > > My guess that my Eris seems to function okay is because HTC has the most > experience in implementing Android. Question for some of you who have > played around with implementing the OS on a device, is it really that > difficult? -- You received this message because you are subscribed to the Google Groups "Android Discuss" 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-discuss?hl=.
