Google's Motorola Mobility buy could ease developer pain points
August 22, 2011 —
(Page 1 of 2)
Google’s planned acquisition of Motorola Mobility for about US$12.5 billion doesn’t change things for developers right away, but could have implications in the future, according to Carolina Milanesi, research vice president of consumer devices at Gartner.
The fragmentation issue – different development standards for different mobile devices using the Android operating system – should be one of the developer pain points eased with this acquisition, according to Milanesi, although she added it will not solve the problem all together.
“Motorola devices will set the bar for competitors in the Android space, but Google will still need to work with Samsung and HTC in Europe,” Milanesi said, adding that Motorola doesn’t have as large a presence globally as it does in the United States.
“Stock Android will always have the latest and greatest updates first,” Michael Gartenberg, research director of consumer technologies at Gartner, said, adding that after the acquisition, Motorola devices will likely be running the basic operating system without proprietary add-ons. This means that should HTC or Samsung or any other device manufacturer decide to put a layer over Google’s Android, they will have to worry about whether or not developers decide to support their version.
Tony Hillerson, software engineer at Effective UI, which develops applications for iOS and Android, predicts that the acquisition is really more immediately exciting for consumers.
“We know that the iPhone user experience benefits greatly from Apple's control of the hardware chain, and now Google is one step closer to that. That means [Google doesn’t] have to rely on handset makers as much to have their Android vision become real. [Google] can have a flagship line of devices that show everyone exactly how it means for the Android experience to be without other manufacturers wanting to taint the experience just to differentiate their handset from other manufacturer's handsets,” Hillerson explained in an email.
Developers, Hillerson said, will have more control over the Android experience as well, without the additional steps they take today to maintain a seamless experience over a variety of devices.
“Where it affects developers is that once Google can get more control over the Android experience, without any middlemen tweaking things on one line of devices at least, then it may become more likely that there are less differences in the experience within the same class of devices from one device to the next. These are differences that may affect how the developer's app looks, feels, or works, and is part of the problem of fragmentation,” Hillerson explained in an email.
Related Search Term(s): Google, Motorola, Android, Apple, iPhone, iOS, smartphone
Share this link: http://sdt.bz/35840
Most Read Latest News Blog Resources
Android is the focus of two new design tools
Anywhere Software and Xamarin provide ways for developers to create and test their applications on PCs
|
|
LEADTOOLS HTML5 add-on modules released
Including New HTML5 Zero Footprint Viewer, JavaScript Libraries and RESTful Web Services for Document and Medical SDKs
|
|
How to speed up your Cukes
Using a five-step process derived from Six Sigma, Cucumber tests can go much faster
|
|
WhiteSource offers open-source license management as a service
Software gives companies insight into the open-source components in products
|
SmartBear rolls out new quality solution: API Complete
Software gives organizations ability to write test scripts and monitor APIs by bridging the DevOps divide
|
|
Android is the focus of two new design tools
Anywhere Software and Xamarin provide ways for developers to create and test their applications on PCs
|
|
WhiteSource offers open-source license management as a service
Software gives companies insight into the open-source components in products
|
|
Top five devices you can integrate with your applications
A five-fingered list of common, household items with which you can talk to (via software, of course)
|
Slick...but who needs it?
compilr.com is a well-designed site and the folks behind it seem to have their heart in the right place. But...who needs it?
|
|
How to be a better software developer
Want to be a better developer? You won't get there by mastering an interesting language or learning a new set of APIs.
|
|
Wooing Galatea
Do yourself a favor and check out Galatea 2.2, a wonderful book by novelist Richard Powers.
|
|
The world as story
An artificial-intelligence system at Carnegie Mellon seeks to understand the world by making statements about it.
|
Five SCM Best Practices
Two-thirds of all software projects fail, according to the Standish Group’s CHAOS study. Improper usage of software configuration management...
|
|
|
Best Practices for Branching and Merging Patterns
Development teams often create a branching pattern, usually drawn out on a white board or in a Visio document, that is used as a model to...
|
|
Automated Error Reporting
We invite you to read a short e-zine that tells you all about automated error reporting for .NET applications. This 8-page e-zine is packed...
|
|
The End of Application Redeploys
Imagine that every time you wanted to write, send or receive an email, you needed to restart your computer. How much time would this take, a...
|