Techaisle Blog

Data drawn from the Techaisle SMB mobility survey shows that SMBs will go from a current average of 7 types of mobility applications in use to 14 in about a year. This 100%-ish growth pattern is demonstrated across most employee size segments.

When we overlay business size with Techaisle’s attitudinally-defined segments of “Pre-IT,” “Basic IT,” “Advanced IT” and “Enterprise IT,” some differences in app adoption emerge. Businesses in the “Pre-IT” segment (found only in the small business group) are currently using only 3 types of mobile apps, versus 7 type of mobile apps in use in each of the “Basic IT: Small Business” and “Advanced IT: Small Business” segments.

This same trend is visible across the three attitudinally-defined midmarket segments. “Basic IT” firms in the midmarket segment are using only 4 types of mobile apps, and planning to add 5 more; both figures are below the adoption rates seen in Basic IT in the small business community.

The more sophisticated segments, though, are adopting mobile applications much more rapidly. The Advanced IT: Midmarket group uses an average of 8 different types of mobile applications today, and is planning to add 6 more in in the next one year, figures that tie very closely to Advanced IT users in the small business community. And the Enterprise IT segment found only within midmarket firms is even more aggressive in mobile app deployment; these firms already use mobile applications in an average of 11 types of apps, and are planning to deploy 9 more.

Mobile applications: scope for growth in core apps and in other categories

The Techaisle SMB mobility adoption survey tracks 20 types of mobile applications. Although there is always overlap between different feature sets and application types, its possible – and useful – to group these into four categories:

We all know that Tablet usage within small businesses (1-99 employees) has been on the rise. As per several Techaisle surveys the penetration rates of Tablet adoption varies from 12 percent to over 30 percent in some countries within small businesses. Techaisle surveys also definitely show that Tablets are largely being used as add-ons to traditional PCs, however there is some incidence of notebooks in particular being replaced by tablets in mobile scenarios. While most repeat tablet purchases are intended to be add-ons to existing PCs, larger Small Businesses have expressed a desire to replace existing notebooks with these devices. This is indicative of a desire but the actual decision will likely be driven by a more logical analysis of capabilities of both devices over the near term. The use of Tablets within small businesses has spread from corner offices and executive suites to a broader adoption within rank and file workers to support line of business and productivity applications. Although the Senior Management and the Sales Executive Personnel are the prime users of Tablets, it is found that among the larger size businesses IT Departments are increasingly using Tablets as they work towards application customization and management of tablets.

Techaisle’s surveys in Argentina, Australia, Brazil, Colombia, Germany, UK, and the US show there are two clear stages of application usage within small businesses.

• Discovery stage – where only basic applications are used. Initial adopters start with Emails, Internet Search, Social Media, and Productivity applications but quickly transition to Deployment stage.

• Deployment stage – in this stage small businesses guided by enhance productivity and motivated by Tablet’s mobility start deploying business related applications.

A comparison of applications being deployed by small businesses across different countries:

Looking at the above data it becomes quite obvious that sales, collaboration, and line of business applications come to the fore-front of most small businesses for Tablet deployments.

Small businesses are giving a clear signal to ISVs that developing for Tablets better be on their product road map. Over one-third of small business using Tablets are also planning to develop custom apps for Tablets, and over three-fourth say that it is very important for ISVs to develop enterprise level applications to support Tablets.

The scenarios change slightly for Smartphone application deployment where payment processing appears more often across most countries, but that is a topic of another discussion.

Detailed SMB Mobility Adoption & Trends reports are available for purchase for each country Argentina, Brazil, Colombia, Australia, Germany, UK, and the US. If interested please send an email to This email address is being protected from spambots. You need JavaScript enabled to view it.

As of March of this year, half of all US mobile phone subscribers had a Smartphone. This in my opinion is more than just a number. It is a tipping point for applications. It is safe to say that we are now in an app economy as far as mobile phones are concerned. But the number has significance beyond just being a tipping point because it is a tipping point for thinking about applications.

What do I mean by that? Applications designed for the desktop or enterprise environments typically exist in a sandbox. That sandbox can be as small as a user’s desk or the entire enterprise but nonetheless a sandbox. Their function and focus is to provide the tools needed to complete a task within the confines of that sandbox. But these apps for the most part ignore user contexts. For example, a CRM application typically does not take into consideration a user’s location nor does an app like MS Office (other than language localization). But mobile apps need to be different because mobile is different. A mobile phone is not just another device. It is a beacon in your pocket that is constantly aware of where you are, what’s around you. It is also aware of your preferences and social network and what transactions you prefer. And one more thing – mobile identifies the user uniquely, not just from a device standpoint but as an aggregate of all the factors mentioned above. So it follows then that Context must define Content. But what are these contexts that app developers should consider? There are fundamentally three.

• Location

• Contacts/social network

• Calendar/time

Not all apps can take advantage of all three but should take advantage of at least one. It is hard to say that one of the above mentioned contexts is more powerful or more important than the others. Each can be powerful depending upon the app or the content. For example, ecommerce applications benefit significantly from taking advantage of location while for a CRM app, contacts and calendar are more critical than other contexts.

Context = Creative Destruction

The use of contexts in app development is not just about driving new user experience and value for users; it is about driving new business models as well. The use of contexts increases the app’s value to the point where in many instances a new revenue model can be implemented. For example, wireless phone companies that by design are able to capture user locations can monetize this “data” in a variety of ways, advertising being one of them. Similarly apps that used to be sold on a per license basis can shift their revenue models to leveraging contextual data as opposed to per user charges. In that respect, context is not only valuable, it is disruptive. The first wave of context aware apps we see have typically been those that would anyway have been free - Apps such as Instagram, Pinterest and Zoomingo (local shopping application).

Increasingly, I predict that we will see whole industries that shift their business models to take advantage of contexts. Newspapers and media are a prime example. While many newspapers are experimenting with paywalls, I believe that a larger opportunity exists for them to exploit user contexts. News publishing today uses what could be termed as an “in-out” model, that is publishers and editors decide what content should be created, publish it and hope that readers will find it interesting. It is the traditional content first driven approach. But what is relevant to me as a reader depends upon my current context. And what is relevant for me today may not be relevant tomorrow. It calls for a more dynamic approach to presenting content, where content to be presented is selected based on a combination of contexts. In other words, an “out-in” model. Doing so improves their ability to deliver advertising thereby potentially increasing revenue.

The same is true for retail. Most mobile retail websites are mere reproductions of online properties but should they be? Online retail websites suffer from the same contextual ignorance as other apps. For example, a mobile retail app would be much more powerful if it could detect a person’s physical proximity to a store. Imagine how small business retailers could benefit from such capabilities. Think about applications like Endomondo that track your physical fitness activities. Well over 5 million users have downloaded and use Endomondo. Consider how useful that data would be to an outfit like REI for targeting and creating customized offers. Here’s another example and a personal one. I am an avid photographer, but not a very good one. I try to learn about photography but that typically happens before or after I am out taking photographs. But the most appropriate context for me to quickly learn tips is when I am taking photographs. Cameras already track locations and embed them in pictures. They already sense light conditions. But this data is not used to educate the photographer! Could it be used to provide tips at the time the photo was being taken? Or could suggestions be given as to how to improve the photograph with examples of the best possible settings? Would it make amateurs like me to more likely to buy a particular camera brand? Would it facilitate brand loyalty? I believe the answers to all of the above are a resounding yes!

Context = Engagement

Indeed, most websites retail or not suffer from the same issue. Even corporate, customer facing websites are mere one-way information dispensing media rather than a context aware, interactive medium that facilitates two way engagements. In fact the very term “engagement” needs to be redefined in the mobile age.  Engagement was largely defined in terms of giving users the content they want/need. But in the mobile age, I believe that engagement should be about the interaction users want and need. It follows then that if context defines interaction then adding contexts fuels a more powerful engagement that can impact costs and revenue.

In Conclusion

Successful mobile applications need to score high on relevance. Relevance is a function that takes into consideration not just content but also all the factors that surround and influence the appeal of that content. This means that app developers have to re-think their applications for the mobile age. And not just re-think but they have to get mobile DNA into the entire organization.