3 ms·

I don't think it's out of date - it was started in July 2009 but seems to be decently updated. Agreed, though, hardware fragmentation is a chore, but the assum

• ydant 16y ago
  I stand corrected. I didn't see the Droid X on there and misread the chart as if the devices were grouped by manufacturer. On closer examination I see it has been updated more recently. How much of the hardware compatibility can be accurately tested in the emulator. I haven't run into hardware issues on my applications, but I don't have the wide device exposure I'd like to have. So I don't really have experience in having something slip by the emulator. I think it depends largely on your type of app. Business/utility applications are less likely to be affected than games. Anything that uses a service is going to run into issues, and anything directly controlling hardware (camera, sensors). The quirks are definitely there, but I think they impact a much smaller group than people like to claim. A service for testing would be good - $x/hr to load on X devices and click certain buttons. It'd have to be cheap, though, or most developers would probably simply opt for market-based testing. You'd probably have to offshore it to get a decent cost. I wonder if you could get a decent response farming this out on the Turk or similar.