As I said, I thought about it. For an individual developer trying to introduce something like this I see the following problems:
1. It won't help the average user if the results of said engine cannot be integrated into the market application itself. Publishing them on a web page is not good enough. 2. How to I get copies of paid apps? I surely wouldn't have the financial resources to buy all apps on the market. If I ask the manufacturers of the apps to give me a free version, how do I make sure, that the version I received for testing is the same as the one in the market? While this wouldn't be too much of a problem for speed, battery, and exceptions, it would be a problem if said engine would also analyze to which servers an app is sending data to. 3. While some force closes are reproducible using something like the monkey tool, some situations are surely harder to test. Google does have information about what exceptions occurred within each application (if the user chose to report them). Stats about these are supplied to developers in the developer's console of the android market. These are all things that I - as opposed to Google - do not have access to. So, why should I invest time and effort into something that Google could (and hopefully will) do in a way more effective way? -- You received this message because you are subscribed to the Google Groups "Android Developers" 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-developers?hl=en
