The Android platform presents several unique challenges, and depending on what an enterprise plans to use them for, they will need some significant subset of the items you list, or maybe just one or two.

In most cases (at least those I encounter), security is a primary concern, as the platform is a bit to ‘open’

We find positive reaction to the Rover Apps platform which delivers answers to most of the items you list:
Security through totally encrypted payloads both in transit and at rest (this later one is key, as most Android hardware lacks encryption). No need for VPN with the option of a secure, intermediated connection. Strong policy enforcement for the App (vs the device), making it ideal for personal devices, and not interfering with personal user experience.

A ‘walled garden’ portal application with centralized control of who sees what on the mobile, supporting an “application catalog” concept for server side ‘apps’ that integrate with ERP, CRM, or legacy internal systems.

Simplified testing and development done completely on familiar server platforms using familiar tools.

All of these are ideal for organizations that want to support this platform, but have security, control and development life-cycle management concerns. Especially when they are looking at provisioning third-party resources (contractors, partners, etc.) with some controlled mobile access to existing enterprise workflows or data.

Again, it all depends on what problems organizations are trying to solve and how much effort they are willing to put towards mobile-enabling personally liable devices. We see a strong requirement for our ‘island of enterprise security and control’ approach with customers wanting to mobile-enable employees and partners on multiple mobile-OS’s.

@philippe agree on security & encryption. i do think shell or more concretely user experience and design is fast becoming higher priority than “nice to have.” net/net, poorly designed mobile enterprise apps, as with poorly designed consumer apps, will not get used.

part of reason i think dropbox and evernote are seen as two commonly sited “mobile enterprise” apps reinforces this need for strong end user design.

a company can build the most awesome user-enabling device/application/cloud (“i” or otherwise) in the universe and unless they can convince a CIO/CSO to adopt, it will never see the light of day.
In this time if continually decreasing IT budgets and increasing regulation of risk from data breaches, device security is everything.
The Android “platform” isn’t likely to get a major security overhaul anytime soon, if ever, so it’s up to individual companies to make the platform appealing and acceptable to enterprise customers. CTIA this spring had an entire herd of companies offering a dual-experience desktop for android phones. this was met with a collective yawn from both OEMs and the general public. (deservedly so in my not-at-all-humble opinion) Let’s secure the damn OS shall we? we don’t need to partition it and make the user jump through a bunch of hoops to keep stuff secure.
Alas, the OS itself is not going to get file-system level security soon, so we’ll do it the old fashioned way.

Build it ourselves.

What is “enterprise enabled” in your mind?

“enterprise enabled” is a a marketing buzzword, in my opinion. i think the term should *SHOULD* indicate some additional level of security and features that are required by most Enterprise customers, but apparently, it means that “we want to sell our regular application to fat checkbooks”.