Archive for the ‘Uncategorized’ Category

How to Map Business Needs to a Mobility Strategy

February 15, 2012 in Uncategorized | Comments (0)

There is something happening on the mobile application development front that is changing the way companies are rolling out their mobility strategies. New technologies are dramatically lowering the time and costs needed to build mobile applications. I’m not just talking about simple apps that display static information or perform highly specialized, and limited, functions.

New hybrid app technologies are making it possible to use simple programming languages like HTML5 to produce mobile applications that are visually and functionally as rich as complex native applications. This is accelerating a trend that many companies have been wrestling with over the past year: a rapid growth in the number of mobile applications being used in day-to-day operations. Why is this an issue? It’s an issue because every mobile application brings with it management and support requirements as well as business process dependencies. The potential for application proliferation is forcing companies to think carefully about how they build out their mobile capabilities.

I’d like to offer a couple of suggestions. Mobile applications are typically designed to address some aspect of mobility strategy, which is all about using mobility to pursue business objectives. Mobile apps are also designed to fulfill tactical needs, which are all about doing mobility in the right way.

With regard to mobility strategy, every mobile application should be justified in the context of its contribution to business objectives. For instance, a business objective might be to increase the productivity of sales people, or to reduce the time it takes to fill an order, or to improve a workflow process, or to reduce the error rate in a business process. Before investing in a mobile application, the business objective should be understood, and the expected business benefit should be weighed against the life cycle cost of the app, which includes development and support.

Once a mobile app is accepted as contributing value to a business objective, the next step is deciding tactically the best way to implement the application. This means evaluating the business process dependencies of the application. For example, will the app need to receive data from another app or IT system to work effectively, and will the app capture data that is important to another business process being driven by another application? This helps determine what level of data sharing and integration your new mobile app will need to support. Another tactical consideration would be deciding on the best application technology for building the app. Does it need to be native app, or would a hybrid application provide better life-cycle cost benefit while meeting the functional specification? Another tactical consideration is user ergonomics. Who will be using he app, and on what kind of mobile devices? What functionality do they need in the app for it to be a valuable tool for them? Will the app run on different devices, and how should it look on those devices? Other tactical considerations include security considerations, for instance if any data associated with the app needs to be encrypted.

As the number of mobile applications supporting business operations grows, enterprises will need to have an application management process that does a good job of mapping business needs to mobility strategy and tactics. Enterprises will also need a mobility infrastructure that enables them to act on their strategic and tactical objectives.

How to Get Execs and IT on the Same Mobility Page

February 8, 2012 in Uncategorized | Comments (0)

Is today’s business mobility driving a wedge between business executives and IT management? It’s a question worth asking because information technology infrastructure is the backbone of all business activity.

A recent article (“Expect conflict in 2012 as consumerisation raises security alarm bells for CIOs”, CSO, December 2011) illustrates one aspect of this issue. This article points out that many IT executives believe the BYOD (bring your own device) trend has gone so far that it puts the enterprise information assets at risk. The article cites a survey that shows “77 per cent of CIOs said consumerisation of IT is creating unacceptable business risk”, and that “67 per cent of business mobility projects are proceeding without the ‘full involvement’ of the IT organization.” It’s important to keep in mind that in many cases it was executives and line of business managers, as early adopters of the latest smartphones and tablets, who started the trend toward BYOD.

This is just one example of the rift between IT management and mobile business operations. With the declining cost of mobile applications and new tools for more easily visualizing corporate information assets on mobile devices, today’s business mobility makes it easy to bring new business applications into the workplace. Many business managers are enthusiastic supporters of apps that make their operations more efficient. Yet ad hoc mobile solutions that start out being quick, effective, and productive can become massive headaches for IT departments tasked with supporting all these apps, securing them, and integrating them so dependent business operations can share the data they produce. It is no wonder IT departments often feel under siege from the rest of the company that is demanding more expansive mobile operations. In many cases, business mobility moves ahead without them.

This is not a good situation, especially at a time when the advantages of mobility are obvious, and companies are moving rapidly to mobilize key business processes. There are, however, a few simple rules of the road that can quickly get IT and the rest of the company on the same mobility page. These include:

• An enterprise should standardize on one application development platform. This does necessarily mean purchasing and deploying such a platform. But it does mean all applications, whether they are purchased from third parties, developed internally, or custom developed by third parties, should be compatible with a platform standard. This will simplify application management, and it will ensure that data and functionality integrates between different mobile applications.
• An enterprise should adopt a robust device and application management platform that works with all mobile devices and is compatible with the application platform standard. When I say “robust”, I mean this platform has enterprise grade controls that support self-service application portals, application pre-configuration and deployment based on job roles and device types, automatic updates, rigorous security controls, automatic triggers and alerts based on usage parameters, and detailed device tracking and reporting. This platform should provide one set of controls for all devices and applications supported by the company.

With these basic infrastructure building blocks, companies can use technology to define and enforce mobility policies that keep data secure without impinging on operational efficiencies. This will make management and IT happy, and it will make them natural allies in pursuing common business objectives.

How Top 3 Mobile OSs Will Keep Innovation Alive

January 25, 2012 in Uncategorized | Comments (0)

Tags: , , , , , , , , , , , , ,

Its always tempting, at the beginning of a calendar year, to cast a glace over the last twelve months and see what another trip around the sun has brought us. When I read this article about global smartphone adoption, I definitely got something that has been on my 2012 forecast: We are on the way to having a few strong players in mobile OS race.

The jury is in after Monday’s news. RIM has taken a tumble and is unlikely to regain market share or its formerly decisive position of leadership in smartphones. The company’s recent misadventure with their Playbook tablet device cost nearly half a billion in write downs. Even more seriously, RIM’s smartphone market share is off by two thirds over the last year, with Android eating most of their lunch. At the same time, Nokia and Intel have abandoned efforts to create a Linux-based mobile OS. Don’t misunderstand. I don’t dislike Linux and have owned several BlackBerrys (which were great devices in their time). I find no personal pleasure in RIM’s misfortunes. However, the enterprise mobile space desperately needed a shakeout in mobile OSs.

Together, Android and Apple’s iOS have amassed sufficient share to exercise a beneficial kind of dominance. As software developers and device innovators organize around these two OSs, de facto standards can emerge. This coalescence creates a rational, sustainable tech market landscape. Having a couple of strong mobile OS players will keep innovation alive, hold prices in check, and let consumer demands drive device development. By the same token, having only a couple of strong mobile OS players concentrates software development talent and allows skilled labor pools to grow. This will provide enterprise much greater opportunity to attract in-house mobile app development professionals. And building in-house enterprise app development resources allow a line-of-business manager or IT group can put forth mobile initiatives that cover 70% or more of the US smartphone installed base and can be accurately scheduled and costed. This may be a watershed moment for enterprise mobility.

Tips to Responding to Disruptive Change on Friday the 13th

January 13, 2012 in Uncategorized | Comments (0)

Tags: , , , , ,

I’m just guessing here, but for the average dinosaur, the year before the big asteroid hit the earth and wiped out most life forms, it probably didn’t seem like that big a deal that some of the stars in the night sky were steadily getting bigger. Then, yoicks. Hello disruptive change, goodbye brontosauri.

Enterprise IT is on the threshold of disruptive change, but in the present instance, there will be a lot more rearranging and a lot less extinction. This is not something that people haven’t been talking about. Mobile devices, and particularly employee supplied mobile devices, are rapidly wresting control of budget and decision making from monolithic Information Technology departments. Consider this:
• Today, more than half of all enterprise mail is received via web mail, often accessed by tablet or smartphone, as opposed to a desktop based email client.
• Enterprise Mobile app development is projected to outpace desktop targeting app development 4 to 1 by 2015.

We can already see enterprise IT realignment taking place. Highly centralized IT departments are losing staff, budget and Solomonic discretion over what software and hardware tools enterprise users adopt to do their jobs. Line of business managers and even individual employees are doing more independent decision making about sourcing technology. If you stop reading here, the story sounds bad. But it’s not. At least, not mostly.

Remember how the big, bad asteroid story actually ended? Pruning away a lot of enormous, sharp toothed, ravenous reptiles made it possible for bunnies and ponies and – hold onto your hairnet—people to emerge. Likewise, CIO-lead organizations and IT professionals will evolve, thrive, and endure. Here’s why: While the shift to mobile device based business processes certainly makes users’ lives better and can make businesses more competitive and adaptive, enterprise mobility can neither invent, manage, nor support itself.

At enterprise scale, the mere fact of mobility doesn’t make technology simpler to integrate, secure, or manage for returns on investment. Count on it: A year from now, we’ll be reading cautionary tales about what happened when some company simply turned out the lights in IT and let users fend for themselves, BYOD style. Chaos isn’t very accountable, but unfortunately, anarchy does scale pretty well.

There has never been a better case to be made for adequate and intelligent mobile technology management. Going forward, I see enterprise IT departments being reformatted as consultative organizations with strong mobility biases. In-house mobile IT experts will:
• Help users make sourcing decisions for cloud services, mobile solutions and the like;
• Develop custom mobile solutions for tablets and phones;
• Assist in creating customer facing engagement and brand building experiences; create and manage enterprise app stores;
• Be tasked with myriad other very complex, mission critical functions.

There won’t be any time left over to lament all of the cumbersome centralized IT technology that passes into the cloud or the fossil record. However, nostalgia isn’t completely out of the question. Perhaps someday there will be a kid’s TV program starring a mainframe. It’s not impossible. Barney got his own show.

All I Want for Christmas is A Million Mobile Apps

December 19, 2011 in Uncategorized | Comments (0)

Tags: , , , , , , , , , , , , ,

According to India’s Financial Chronicle, somewhere about the end of December 2011, there will be over 1 million mobile apps available in the public marketplace. India’s largest mobile app store, Mobilewalla, says that currently about 15,000 mobile apps are released weekly. Just to put this in perspective, there are something like 3.2 million physical books in print as of today. If you use the beginning of Johann Gutenberg’s printing operation in the 1480’s as T=0, the weekly average for global print book publication over the intervening 530 years comes out to about 115 per week.

This is one case where no one is going to say “You do the math”. It’s a complete waste of time to do the math. There is very obviously a tsunami of mobile apps washing over the globe, literally the biggest worldwide personal empowerment movement in the history of life on earth.

If that assertion seemed a little bit breathless, fear not. I am about to take a step back from it. First, I will heartily acknowledge that, far and away, the largest app category is comprised of games and entertainment. Don’t be fooled by this. While it may not be of tremendous enterprise import that 15,000 apps a week are being released if 14, 550 of them are a variation on Angry Birds, here’s what is important. Mobile apps are occupying a place in popular culture that can’t be ignored or dismissed by IT professionals, because they represent a complete shift in people’s expectations about connection and engagement.

If you doubt this, remember that we have seen the same communication technology paradigm shift play out several times before: Recall once-novel capabilities like voice mail, fax machines, email and web presence. The tipping point for business occurred when similar technology became available to consumers. If people had access to a technology at home, it automatically became unthinkable to them that businesses wouldn’t provide voice mail, fax numbers, email and web portals to help speed business transactions. We are very rapidly approaching a frontier where both employees and customers will demand that businesses and institutions interact with them using mobile devices and special purpose apps. Failing to foresee and prepare for this is extraordinarily shortsighted, and could cost laggards dearly.

Demand for Mobile Coupon Support Will Hit Enterprise App Developers Soon

December 13, 2011 in Uncategorized | Comments (0)

Tags: , , , , , , , , , , ,

It’s always good to lift our eyes to the horizon and check out what is coming over it. For enterprise mobile app developers, this is it and it’s moving fast: Mobile coupon support. A recent study by Juniper Research forecasts that mobile coupon redemptions will top $43 billion within five years, which amounts to something like an eight fold increase over today’s numbers. This is a key development for brick-and-mortar retailers, and is the lifeline that may help drag them back across some of the ground they’ve lost to online competitors.

The simple fact of the matter is that people like to shop. They like to see and feel the things they buy before they make purchasing decisions. They like to do the ‘passeggiatta’ in the mall on a cold windy day. The intelligent use of mobile coupons is turning out to be a solid, reliable way of getting them back, particularly when coupled with advances in data science that make it possible to target specific tailored incentives and for merchants, restaurants and service providers to partner in deal making. In a way, retailers are coming a little late to this party. The travel industry figured it out a decade ago: People who buy airline tickets also book hotel rooms and rent cars. Likewise, people who shop on Saturday will probably eat lunch around noon, and by five may be entirely susceptible to a nice offer on a pedicure or a late matinee.

Given the documented success of location aware mobile couponing, enterprise mobile developers can expect to see it take up a strong position on executive wish lists soon. Here are a few talking points to have in hand when working to develop a strategy for using this marketing tool to best advantage:

• Juniper and analysts have found that it is very important to treat your mobile customers to coupons only on an opt-in basis. Sending unwanted promotional material to a customer’s mobile device can be very alienating and destructive to brand reputation.

• Make early evaluations of how data science can help target promotions, based on purchase history, demographics, behavior patterns and the like.

• Start small, but don’t postpone getting started. This is a real phenomenon and may well eclipse many other forms of customer engagement.

• Don’t forget the social media piece. Location aware coupons’ effectiveness can multiply when customers broadcast your deal to their social networks

Managing Android in the Enterprise

December 7, 2011 in Uncategorized | Comments (0)

Tags: , , , , , , , ,

Android devices are coming on strong with consumers. In Q3, it claimed a remarkable 27% of tablet device sales worldwide, which is a stunning result, given that all of the buzz was in the iPad camp. Even more impressive, AT&T, original home of the iPhone, reportedly doubled its Android phone sales in the same quarter. Despite fears that Google would spook its partners by jumping into the Android hardware space, consumers seem to be beating a path to their collective doorways. Given this, it is worth getting ahead of the impacts of a likely population explosion of enterprise user supplied devices of the Android persuasion.

It is for this very reason that a recent article in Network World about Android’s potential issues for the enterprise mobile device management caught my eye. If you are responsible for managing mobile IT infrastructure, chances are you already appreciate that Android isn’t just one thing, or even a closely related series of individual things. Rather, it is a basic mobile OS framework upon which device vendors can build, allowing full customization and ample opportunities for the device vendor to differentiate and position products. A lot of popular, relatively low cost Android consumer devices are very light on security features. This stands to reason, because for most consumers, beyond a certain fairly fundamental level, security is just inconvenient. Device manufacturers would far rather build in features that attract customers

In terms of managing and securing Android device access to enterprise assets and infrastructure, relying on well hardened perimeters is probably going to be less successful and efficient than prioritizing and addressing critical threat scenarios. If I had to choose one threat scenario as a place to start fortifying Android device defenses, it would be creating strong privacy and security for mobile messaging streams. Here’s why:

Recently, I’ve been hearing more and more about a mobile hacking technique known as ‘spearphishing’. Unlike older phishing techniques which broadcast malware-laden spam in hopes of snaring the naïve, spearphishers use sophisticated mechanisms to steal personal information, accrete enough of it to concoct highly authentic looking bait, and then approach a specific target impersonating a highly trusted source. Some documented spearphishing incidents have achieved large scale, effectively infiltrating entire institutions’ IT infrastructure. Moreover, they can go undetected for long periods of time if their activities are not aimed at causing disruption, but instead at harvesting valuable data. Before a facing management of a significant crowd of weakly protected BYOD Android devices, have some built in precautions that keep enterprise messaging streams from becoming a playground for spearphishers.

What If the Product Isn’t the App, But the API That Powers It?

November 29, 2011 in Uncategorized | Comments (0)

I just came across this post on the Programmable Web, entitled The Private API Iceberg, in which Adam DuVander reports that there are now over 4000 APIs publicly disclosed on the Programmable Web directory. These allow any mobile app developer to tie into existing apps and backends to leverage services and create mashups. Inarguably, 4000 is a whole lot of APIs, but the point of DuVander’s post is that a huge majority of APIs are undisclosed . His forecast: Some of these will remain private, some will transition to partial disclosure, and some will aggressively pursue developer mindshare by disclosing and documenting APIs.

What seems obvious to me, however, is that the trend toward openness is accelerating and can only continue to do so. The reason for this is tied up with the evolution of data science. Think of it this way: If I have a really clever idea, implement it in an API, and ultimately create an app or service, I have a time-limited opportunity to profit from my innovation. After that window, imitators will crowd my space and other cool ideas will eclipse mine. If, however, I have my idea, act to reap the initial harvest of my creativity, and then publish my API, I may ultimately gain something much more valuable than profits from a cool app. I can collect data about the people who use apps that include my API. Long after my app innovation is stale I can still be generating revenue with a data harvesting business. All I have to do is gain a community for my API by releasing it while it still offers others an opportunity to build upon it.

Just scanning through recently published APIs on Programmable Web, I get a sense of how valuable this kind of data stream could be to targeted marketing efforts. Here are a couple of examples

The Peachnote API powers an app that helps consumers search for classical music. Great data source for targeting concert advertising and Holiday recordings.
The Urban Airship API is sort of a location aware “situational awareness” engine—think sports scores, weather, traffic reports and the like. Great data source for mobile coupon distros.
CurrencyBot API provides up to the minute currency exchange rates. Great way to identify customers who need tourism and travel services.

My point here is that it’s possible that the mobile enterprise apps we produce might eventually be a mere side effect of the real work we do–creating publishable APIs that accrete data assets. Imagine it: IT as a profit center.

Is BYOD spreading to the desktop?

November 8, 2011 in Uncategorized | Comments (0)

Tags: , , , , , , ,

We are on the show floor at SapphireNOW Madrid and there are many companies and mobile devices here for an exciting week. Many companies are moving toward a “bring your own device” (BYOD) approach to mobility management. There are a number of reasons for this. One is the fact that it’s happening anyway. Workers bring their own devices into the work place because they prefer using their own devices, and they work more efficiently on them. Another reason is that managed properly, BYOD can save companies money.

Many companies are finding that an enterprise grade device and application management platform simplifies the challenge of managing a diversity of mobile devices. These platforms are specifically designed to be mobile device agnostic. This gives companies greater flexibility in the mobile technologies they can use in their business operations. However it also raises an interesting question. Will a robust, device agnostic, application and device management platform create an IT infrastructure that offers more flexibility in the kinds of desktop devices workers can use?

A recent article in CNET reported on some interesting findings by a Forrester study. The article said this:
“Even though the vast majority of companies around the globe are still using Windows PCs, Macs are starting to find their way into offices–just not through the traditional means, a new study from Forrester Research has found.

According to the firm, 22 percent of the 590 enterprise IT executives Forrester surveyed say that they’re seeing an increase in the number of employees bringing their personal Macs into the office. Further inspection reveals that 3 percent of respondents saw Mac use jump by more than 20 percent in the last year, while 5 percent of respondents said that the increase was in the range of 10 percent to 20 percent. Forrester said 14 percent of respondents have seen Mac usage by employees increase by 5 percent to 10 percent.”

The article goes on to point out that many companies do not allow workers brining their own Macs into the office to have email access or run other business applications on them. However the Forrester study questions whether companies will stick to this policy over time. Given the advantages some companies find in supporting a BYOD mobile device environment, and given that companies are building infrastructures that support a diversity of devices, it’s worth asking if mobility is leading the way to an entirely different attitude in the enterprise about how to manage client systems.

Application Interoperability and the Mobile Enterprise

October 31, 2011 in Uncategorized | Comments (0)

Tags: , , , , ,

Recently I happened upon an interesting blog that was posted several months ago by a developer commenting on the use of specialized mobile apps. In his post, called The App Interoperability Conundrum, he makes the following observation about using his iPhone:

“It is without question that mobile devices will continue to proliferate in the consumer market with improvements in mobile infrastructure, device affordability and cultural acceptance. However I see an uneasy trend in mobile applications, that is, mobile applications are becoming increasingly focused but less interoperability.

To illustrate this point, consider the following hypothetical example. I am in downtown Los Angeles, I’m hungry and need nourishment from a reputable establishment. On my iPhone I can use:
1. Google Maps to find a nearby restaurant,
2. MapQuest to get voice guided routing directions,
3. Built-in camera to record my memorable meal,
4. FourSquare to “check-in” and recommend this restaurant to my friends, and
5. Yelp to post a review (and snapshot) of my dining experience.

In this workflow, the only interoperable elements were the street address I copied from (1) to (2) and the photo created in (3) and shared with (5).

Obviously this workflow could be optimized by using one app to perform two or more tasks like using Google Map to a find a restaurant and driving directions. But these five apps, in my hypothetical opinion, were the best in each task.

My criticism is not targeted at the number of app used during my lunch break but the lack of interoperability between them. For example:
1. From Google Map, why is it not possible to send the restaurant address directly to my favorite routing apps?
2. From the camera app, why is it not possible to share a photo directly with Yelp.
3. From MapQuest, can I send the “route” to my friends so that they know where I am driving from?
4. To rate (or “check-in” at) the restaurant with FourSquare and Yelp why did I have to locate the restaurant in each app?

Why not just click the “get current establishment” button in each app?

These comments may seem like iPhone-bashing, but they are not. I am just bringing your attention the unintentional ‘stovepiping’ caused by increasingly focused mobile apps.”
For a consumer, this lack of interoperability between applications is an inconvenience. However when it comes to enterprise mobility, the interoperability conundrum can become a serious impediment to efficient business operations. People make decisions based on the information that is available to them. Sales data informs business planning. Marketing and sales information combined with supply chain data impacts production. An intelligent organization’s operations depend on shared information.

That ability to collaborate and share information in real time is a major reason why mobility has become essential to business operations. Yet what happens if mobility is pursued in a non-strategic way? What happens if every work group adopts its own mobile applications without regard to other operational dependencies? The result will be “stovepiping” of business operations caused by a lack of application interoperability.

As you build a mobility strategy, it is critically important that you do so in a way that enables application interoperability. You may not know how tomorrow’s applications will depend on today’s or yesterday’s data, but you need to have a mobility infrastructure that gives you the flexibility to share information between applications. This is what a mobile application platform like Sybase Unwired Platform does.