Skip to main content
877.232.7903

Thinking about Building a Mobile App?

      Check out the infographic and read on for how to Avoid the Gotchas...


Nearly all of the Fortune 500 is using or testing tablets today, and 80% of all enterprise apps are expected to target smartphones and tablets by 2015. A big driver of mobility for many enterprises is the opportunity to improve customer and field service with instant data capture, access, and workflows.

App development using web-based forms for always-connected workers with PC browsers, for example, can be fairly straightforward. Challenges arise for teams needing fully customized apps that can be used while workers are online or offline. Despite general improvements in network coverage, many workers in the field don’t have reliable, snappy coverage when they need to capture or send data. A recent survey showed that more than 70% of all mobile apps users have suffered from connectivity issues which have gotten in the way of their ability to get the most out of their apps.

To get around connectivity issues, teams usually build local apps on tablets and smartphones, which can be expensive and time consuming. A typical enterprise iPad app with medium levels of integration has an average development cost of $100,000. The vast majority of those apps require 3-12 months of development time.

The challenge is compounding with nearly two-thirds of all mobile enterprises planning for at least 5 different mobile apps in the next 12 months.

There is good news, however. With the vast expansion of the mobile development ecosystem over the past few years, there is now a wide variety of different development tools and options for building apps. There is also a lot of accumulated wisdom for helping teams avoid the common pitfalls or “gotchas” of mobile app development.

Download this eBook to learn how to avoid the Top 3 Avoidable Gotchas of Mobile App Development:

1. Everyone likes the app, but the workers and they don’t use it.
2. Getting locked into proprietary solutions that IT doesn't like.
3. Not preparing for change