Android: Motorola's next adventure

OEMs face very special challenges with Android.  A set of challenges relates. Let me explain.

If you are browsing users and Android device consumer reports you see some models because there are reported issues that are directly attributed to the quality of the code and using the code metircs in an agile way qa feedback loop. Although Goolge and OHA have worked hard on the set of Eclipse ADT tools plugin, ADT is not to the point where you have clicked through qa metrics of the code, but with easy access for developers of Android applications.

So with the first season of Christmas with 8 million Android devices in the hands of consumers that threat we need a stop-gap tool that helps application developers Android easy access to these loops qa code application code quality metrics os changes to reflect the device and the stability of the OS. Part of the reasoning for starting a build system project AndCooper Android, it's that I've seen the need for OEMs to lead this charge to the developer code easily accessible QA metrics to improve the stability of the application.

That renewed emphasis on the stability of the application and has direct effects on the impression of stability of the Android operating system with the OEM customers. I really believe that Motorola could lead this set of challenges. The question is how to convince an OEM that they should lead in this way? Challenge an interesting, certainly.

View the original article here