This post originated from an RSS feed registered with Java Buzz by Fred Grott. Original Post: AndCooper Frustrations Feed Title: ShareMe Technologies LLC-The Mobile Future Feed URL: http://www.jroller.com/shareme/feed/entries/rss Feed Description: A Weblog about Java programming and digital convergence on mobile devices in such areas as P2P and collaborative technology. Latest Java Buzz Posts Latest Java Buzz Posts by Fred Grott Latest Posts From ShareMe Technologies LLC-The Mobile Future

Basically, the whole idea of the AndCooper Android Java Application Build System Tool has been that you would pace this tool in your project folder and because you can point your IDE to use the build script as the java builder you would right away automatically have a somewhat automatic continous build tool setup that would generate code analysis reprots that than could be used as feedbackas you code.

Because the developer would have access to the analysis in a feedback loop code quality improves, Android Application stability improves and thus has a direct measurable improvement in user happiness and etc. The difficulty is not in trying out such things as Xradar, Sonar, or Qalabs to see which one would fit as the one to merge all the coe analysis reports into a resonable hub of reports but getting feedback from stakeholders.

Without direct feedback from some stakeholders in the OEM community I have had to guess which implementation decisions needed to be made and guess at how to make it flexible enough to satisfy all stakeholders from the one-person development shop up to the level of the OEM shop that is developing applications to  be pre-packed on the Android device.