SPECIAL REPORT: Interop   See more>>

Does Your Enterprise Need An App Store?

Employees increasingly are expecting to have access to business tools that are as easy to use on mobile devices as anything they can download from Apple or Google.

10 Companies Driving Mobile Security
10 Companies Driving Mobile Security
(click image for larger view and for slideshow)
With the consumerization of IT becoming a well-established phenomenon, enterprises are weighing whether they need to develop and distribute smartphone and tablet-style versions of their business applications to employees who, more and more, are bringing their own mobile devices to work.

"If it's not officially BYOD (Bring Your Own Device), it is anyway," said Cimarron Buser, VP for product marketing at Apperian, during a panel discussion Thursday at the Interop technology conference and expo in New York City, a UBM TechWeb event.


More Insights

Webcasts

More >>

White Papers

More >>

Reports

More >>

For the most part, the panelists agreed that corporate IT departments need to start thinking about how to consumerize their company's business applications, or end users will simply bypass them and find their own ways to get the data they need onto their mobile devices.

"An app-centric strategy is essential to get around the whole problem of the consumerization of IT," said panelist Scott Olson, mobile architect at ITR Mobility. "It's throwing enterprise IT into a tailspin."

[ Dealing with mobile apps? Be careful because Mobile Security Exploits Expected To Double. ]

The time, expense, and effort that will inevitably go into building an enterprise app store will be justified by a more satisfied, productive workforce, said Michael Dortch, research director at Focus. "There's an opportunity for IT to redefine itself as an enabler of success."

Dortch said enterprise application developers can learn a lot from their counterparts on the consumer side. "Why aren't business applications as easy to use as Facebook?"

Not that "consumerizing" business applications by porting them to mobile-friendly environments and simplifying their interfaces is easy. "There are complexities in CRM that means it's never going to be as easy as buying something on Amazon," said Jay Mellman, chief marketing officer at Rhomobile.

The good news is that there is a plentiful supply of young programmers who are adept at working with HTML5 and native device platforms like iOS and Android. "Often you'll find them embedded in sales; they haven't talked to their boss in IT six months," said Buser.

Deploying business apps to mobile devices raises a number of security issues. If protections are insufficient, crucial company data could be exposed. But if security measures are too stringent or complicated, employees may take a pass. "When users are forced into that kind of approach they just don't use the apps," said Olson.

"You have a series of questions you have to answer for every app you want to deploy," said Buser. "The policy questions can be gnarlier than the technology issues."

But app mobility is an issue that enterprises are going to need to deal with for their own good, he said. "If you make enterprise apps that don't suck you will have a much more productive workforce," he said.

Attend Enterprise 2.0 Santa Clara, Nov. 14-17, 2011, and learn how to drive business value with collaboration, with an emphasis on how real customers are using social software to enable more productive workforces and to be more responsive and engaged with customers and business partners. Register today and save 30% off conference passes, or get a free expo pass with priority code CPHCES02. Find out more and register.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
Subscribe to RSS

Resource Links