4 ms·
I seem to read really mixed reports about the Android fragmentation problem. For every report like Joe's, I see others that say developing for Android is fine.
by JunkDNA 16y ago
I seem to read really mixed reports about the Android fragmentation problem. For every report like Joe's, I see others that say developing for Android is fine. I can't get a good read on where the actual truth is.
I work in a group that does research on mobile healthcare applications. We're not a software company, so we can't afford to have a whole pile of devices here for testing. With the iOS platform, at least I can be confident things work if I can test on my iPhone and our iPod touch test units. That said, Android is going to eventually be too big to ignore sometime soon. I'd be curious what other devs around here have experienced. Maybe we should be using PhoneGap to avoid those sorts of problems?
- briancooley 16y agoI haven't had any device-specific error reports for the few Android apps that I have worked on, but they are pretty vanilla. There are occasionally comments in the android-developers group about issues specific to particular phones. Seems like the Droid is often mentioned, and the thread I recall was with the camera. I imagine it would be frustrating to get a crash report, not be able to duplicate it, and have your app work fine on the dev phone in your possession. edit: here's the thread: http://groups.google.com/group/android-developers/browse_thread/thread/a6de0a8d755915c/417af37a54d4f669?lnk=gst&q=droid#417af37a54d4f669 http://groups.google.com/group/android-developers/browse_thr...
- carlrice 16y agoIn 2.2 and higher there is an integrated crash reporter into the system. For 2.1 and lower I have a crude catch all error handler that sends the cause of the crash, app and os versions, handset model and carrier, etc. Using this method, some custom ROMs and two phones I can fix roughly 95% of the errors without actually having the device or user with me to debug.