In fact it's very hard for an indie developper to check and test his code on every existing device types (almost 1000), the only way to have some crash feebacks (apart from the nice user that take time to post it ;) ) is to integrate a tool in your app that reports those errors when they occur.
Here's an extract of ACRA doc presenting the features :
- developer configurable user interaction : silent reports, Toast notification, status bar notification + dialog
- usable with ALL versions of android (compiled with 1.5, not tested on 1.0/1.1 but might work... but who does really care ?)
- more detailed crash reports about the device running the app than what is displayed in the Android Market developer console error reports
- you can add your own variables content or debug traces to the reports
- you can send error reports even if the application doesn't crash
- works for any application even if not delivered through Google's Android Market => great for devices/regions where the Android Market is not available, beta releases or for enterprise private apps
- can be used with your own self-hosted report receiver script
- google doc reports can be shared with a whole development team. Other benefits from the Google Docs platform are still to be investigated (stats, macros...)
I've integrated ACRA on my last game , Android jumper, and it gives some very usefull informations like stacktrace, last and initial configurations, device setup ...
I've found several bugs using it, like the issue occurring only on Android 1.5 (sad crash at the launch), and reproduced using the android emulator.