UX

Because mobility is starting to impact so many parts of the enterprise for some time now we have been considering how enterprises should be thinking with regards to mobile applications for their customers, employees and partners and have been formulating relevant investment theses. Based on input we have received from several senior IT and business unit executives we tried to determine when to use mobile-first as an application development strategy and when to focus on a mobile-only strategy. Through these executive interactions we have also come to realize that, the mobilization of existing applications is a high corporate priority because many of these applications automate proprietary logic about a specific business process that allow an enterprise to differentiate itself from its competitors. As such, the majority of these applications are bespoke, having either been developed internally or under the specification of the enterprise. For this reason we have focused our initial efforts on understanding the growing startup ecosystem that provide solutions to address the mobilization of existing applications. (At the end of the post I provide our thinking of this ecosystem). In this post I want to focus on third-party mobile applications which are starting to play an important role in the enterprise.

Enterprises must pay attention to 3rd party mobile applications for two reasons. First, in order to determine which of the 3rd party desktop, including browser-based, applications they have previously adopted will need to be mobilized. Second, in order to consider such applications as viable alternatives to internally developed applications whose mobilization is proving unfeasible.

With regards to the horizontal and vertical desktop applications they have already licensed, enterprises face an interesting dilemma. In some cases they may be able to license an adopted application’s mobile version. Because enterprises are increasing the use of mobile devices, many vendors have already developed, or are developing, mobile extensions to their flagship products, e.g., Salesforce, SAP, Microstrategy. In many instances this is the preferred approach because the enterprise is already familiar with the application vendor, has the appropriate license agreements in place, and the relevant data and application integration (and configuration) tasks have already been performed. However, because mobile application development talent is in short supply, many of these mobile application extensions tend to have several issues such as incompatible and even clunky User Experience (UX), security flaws, web-only implementation while a native application would have been a better fit, and poor functionality compared to their desktop counterparts. In many cases the software vendor is not able to incorporate in the mobile app key pieces of functionality that the enterprise had previously configured for the desktop app. For these reasons alone, corporations may want to consider licensing a mobile-only enterprise application from one of the new vendors that are quickly emerging to fill the void (for a partial list of such vendors see here). For example, RoamBI provides a mobile-only application for business intelligence that competes with Microstrategy’s.

Corporations must consider mobile-only third-party applications for four additional reasons.

In order to rapidly automate a mobile-centric business process that hasn’t been previously automated. Even if the corporation has an application development group, depending on the group’s priorities and talent, it may be easier to adopt the third-party application instead of developing it internally. Applications like Dudamobile’s that is used for automatic creation of mobile websites and Digby for e-commerce provide good examples for this case.

In order to leverage other third-party software through APIs. Mobile payment applications provide a good example of this. Several companies are tackling this space because it is difficult for banks and other organizations to develop their own solutions. Mobile payments have been growing rapidly, e.g., during 2013 Starbucks drove $1B through mobile payments, and for many enterprises they are starting to represent one of the most important monetization channels.

Allowing enterprises to cost-effectively mobilize an internally developed application. Cost is measured along a variety of dimensions:

Cost to hire the appropriate talent (as many companies are quickly finding out a strong internal application development organization doesn’t automatically imply that it will have strong mobile application development skills; see Yahoo’s recent mobile talent acquisitions in this area).

Cost to create the right User Experience (UX). UX is one of the most important factors to a mobile application’s success. For example a customer-facing application has different UX requirements than an employee facing one, as banks and insurance companies are coming to realize through the adoption, or lack of, of their mobile banking applications. This talent can also often be difficult to find.

Cost to develop, test, deploy and maintain each application, even if the talent is available. As in all application areas, oftentimes it is more than adequate to provide 80% of the necessary functionality quickly rather than wait for a long time to provide more than this level of functionality.

Cost of being late to market because of the previous 3 issues.

Each corporation has developed many different applications, in several cases thousands of them. Mobilizing them in a timely manner often becomes impossible. As a result adopting a third party application represents the fastest path to mobilization. Alternatively they can try virtualizing their desktop applications and in this way make them available through a mobile browser. Companies like PowWow, Capriza, StarMobile, Citrix, included in the ecosystem at the end of this post provide solutions in this space).

While mobile consumer applications continue to dominate investment and M&A discussions these days, mobile enterprise applications present, internally developed or third-party, present an interesting set of issues that we consider as we determine in which parts of these ecosystems to continue investing.

I have broadly organized the custom mobile application ecosystem into six categories depending on whether the companies provide application: