Having an enterprise app is no longer optional

The business world has recently seen a dramatic increase in the usage of mobile apps in the workplace. The percentage of survey respondents reporting full mobile app implementation rose from 7 percent in 2013 to 52 percent in 2015,  according to Red Hat’s Mobile Maturity Survey 2015. This is indicative of a strong trend towards using apps as tools for corporate growth. This means corporations will have to invest in developing an enterprise app in order to remain competitive. However, managing the development of enterprise apps is not easy and requires many considerations.

Consider the client

It is always important to include the end-user (or the client) in the development process. This is especially important during the planning and testing phases. So it would be wise to create a team of users and then consult them throughout development. By speaking with with them, you can get a good sense of what would make their working experience easier and more efficient. Consequently, this will be very comforting for your users because it will feel like the app was tailored to their needs. It will also ensure that all –if not most– of the required features are included in the app.

Including the clients will also help in preventing premature optimization and poor reachability (each will be discussed later in this post). Avoiding those two pitfalls is necessary when creating an optimal user experience.


The concept of reachability is important when trying to create a great user experience. One handed and two handed users must be able to easily reach all input buttons on the screen, regardless of screen size. A reachable app should also have a menu system that doesn’t have too many sub menus, making the features of the app easy to reach. These are just a few of the many principles for developing a “reachable” app.

Premature optimization

Another important factor to consider is hardware optimization. The app must be able to process data and display it quickly within a small margin of time.  Not doing so would be detrimental to the user experience . However, some developers take this too far by spending too much time needlessly optimizing  every little part of their program, leading to a phenomenon known as premature optimization. On one hand, people argue that you shouldn’t worry about optimizing until later on in the development cycle. This is when the performance bottlenecks become apparent. On the other hand, people believe that you should consider the standard practices and plan ahead before you even start to work on the app. This would then eliminate future bottlenecks in the first place. Resorting to either extreme will either waste time immediately or in the future. Finding a balance between optimizing the app as it is being developed and optimizing it near the end of development. Once you’ve found the sweet spot, you can then confidently develop the app without having to worry about misusing time.


Leave a Reply