This post originated from an RSS feed registered with Java Buzz
by Fred Grott.
Original Post: Motorola's Next Android Adventure
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.
OEMs face some very particular challenges with Android. A particular set of challenges is community related. Let me explain.
If you peruse reports from Android Device consumers and users you see some patterns in that there are problems reported that are directly attributed to code quality and using the qa code metircs feedback loop in an agile way. Although Goolge and OHA have worked hard on he Eclipse ADT plugin set of tools, ADT is not to the point where you have a click through to qa code metrics yet with easy access for Android application developers.
Thus with the first X-mas season with 8 million Android devices in consumer hands looming we need a stop-gap tool that allows Android application developers easy access to those qa code metrics loops os that application code quality changes in order to reflect device and OS stability. Part of the reasoning for starting AndCooper Android Build System project is that I saw the need for OEMs to lead this charge towards developer easy accessible qa code metrics to improve application stability.
That renewed focus on application stability than has some direct effects on the impression of Android OS stability among OEM clients. I really believe that Motorola could lead that set of challenges. The question is how do you convince an OEM that they should lead in this manner? An intersting challenge, certainly.
Previous Topic
