Phones built with Google’s Android operating system may suffer from a lack of interoperability, and enterprise IT executives will probably be wary about supporting multiple devices built with the much-hyped software platform, says Ken Dulaney, a Gartner analyst.

Read our FAQ on Android.

Android, a software stack complete with an operating system, middleware, user-friendly interface and applications, was announced Monday and will be released as an open source software development kit next week. Phones based on Android are expected to hit the market in the second half of 2008.

But the openness of the platform – which Google and its partners consider a key to collaborative development – will make it difficult to achieve interoperability across phones, Dulaney says.

T-Mobile and HTC have already said they will develop mobile devices with Android, and it’s likely numerous other vendors will do the same. The downside to this, Dulaney says, is that creativity will breed differentiation, and Web applications designed for one phone may not work well on another.

Applications “will probably run. The question is will they run well,” Dulaney says. “That’s the biggest concern about this effort. There’s not enough control exerted by Google to force this to be consistent across the board.”

Dulaney previously warned enterprises against supporting the iPhone en masse, and says that device still lacks the security necessary to qualify as an enterprise-class supported device.

Dulaney’s not issuing any similar warnings this time, saying the Google phone platform “doesn’t affect enterprises at all. It’s really a consumer play. What enterprises want more than anything is connectivity to the back end, stability and interoperability, and this doesn’t address that.”

If there’s enough employee demand, enterprises will support Google-powered phones, says CTO Dave Leonard of Infocrossing, an IT outsourcing provider in New Jersey.

“If it’s successful and people have it, it will come into businesses and we’ll adapt to it,” he says.

It’s hard for IT departments to decide whether to support Google’s Android, because it’s a platform for developing phones, rather than a phone itself, Dulaney notes. Each IT department is likely to pick one type of Android-powered phone to support and not support others, because they don’t want to risk lack of interoperability, he says.

Whitepapers

• Selecting Effective Virtual Directories
• Best Practices for HP Servers and HP Enterprise Virtual Array in a Microsoft Exchange
• Compliance, Protection, Recovery: A Layered Approach to Laptop Security
• Endpoint Security: Data Protection for IT, Freedom for Laptop Users
• IT Departments on Data Security: A Research Concepts Survey
• Laptop Security Tool Helps Allina Hospitals Track 97% of IT Assets

View more SOFTWARE whitepapers

Webcasts

• Managing the End User Experience-A Real World Example of Success
• Lowering the Cost of Email Archives
• Google Webcast: Why archive email? Top challenges and best practices
• High Availability for SQL Server 2005 Using Array-Based Replication and Host-Based Mirroring Technologies
• Technical Overview of Exchange Server 2007 with HP Servers and Storage
• Bringing Order and Security to your Mobile Workforce: Corporate Mobility Policy and Device Management On-Demand

View more SOFTWARE webcasts

Special Reports

• Application Performance Management Executive Guide
• Executive Guide: Building a Service Oriented Architecture
• IT Buyers Guide To: Collaboration

View more SOFTWARE special reports