As smartphones become ever more sophisticated, they are opening up new opportunities for developers to create applications which provide users with greater convenience, more flexibility, and more choice. This new era of mobility is driving a fresh wave of innovation in application design and development, and while there are some limitations to the scope of data that can be accessed and delivered to a mobile, equally, there are a host of features, such as GPS or barcode scanning, that can open up new possibilities in terms of how mobiles can deliver a better user experience.  Here we consider some top tips on what you need to consider in order to successfully mobilise applications.

Look for ways to innovate processes
Compared to a desktop, CPU performance tends to be more limited on mobile phones but, for developers considering how to take applications to a mobile device, it’s not about  developing a ‘desktop-lite’ version of an application. Rather, they should consider how to work with the inherent advantages that the mobile device offers, to create more innovative processes.

Incorporating back office integration as part of the mobile technology is one of the most important considerations in going mobile. For example, on a desktop, we can easily tab through different screens to access data from different sources. On a mobile device, this all needs to be consolidated on to one screen, to make it workable. This means that it is essential to think about the processes involved in the background and look for ways to make these as efficient as possible and to try and ‘mash up’ all relevant data, regardless of the source application, into one simple screen.  

Work with the features of the phone
This may sound straightforward, but it’s one of the fundamental factors behind the most successful mobile applications. The combination of GPS, compass, gyroscope, camera and voice capabilities have unlocked a set of capabilities in applications that provide new value, such as knowing your location. Translating this into an enterprise application, one scenario could be a salesperson on the road who could use the GPS sensor on his mobile to trigger a process which presents him with data on everyone he could potentially visit within a half-hour drive. A good example in best practice of this concept for consumers is the Apple stores, which now take your name and credit card number, but also utilise capabilities such as barcode readers and the camera.

This concept can also help to overcome one of the central issues in developing mobile applications, which is to limit the amount of data entry required by the user. Despite huge leaps in processing power, mobile phones aren’t generally designed for heavy data input, and any processes which require this can not only be off-putting for the user, but also result in lack of adoption.

Keep process time down
Mobile users, by nature, tend to have a shorter attention span than users of desktop applications. When developing mobile applications, it is worth remembering that users tend to require access when they are in a hurry, and when time is of the essence. Whether accessing data in between meetings, or checking up on a customer account on the road, the mobile user needs to execute a process quickly. A general rule of thumb is that each process should be no longer than 30 – 40 seconds for mobile applications. Also, make sure screen displays aren’t overloaded with information, but presented only with data that is relevant for that task or process.

Go platform-independent
The mobile landscape is continuously evolving, and this creates challenges for developers that need to second guess which platforms will dominate. New, platform-agnostic development platforms  overcome this challenge of trying to anticipate where the mobile future lies. These engines use pre-compiled and pre-configured business logic that contains coding functionality and services. This allows developers to bypass the intensive code-writing stage, and means that they can work independently of the underlying platform. It’s an approach which can also automate and synchronise a mobile application with other diverse applications, without the need for manual by-line scripting. 

Access to real-time data extends the value of an application
In addition to the application providing a simpler interface on the front end, mobile applications need to provide access to data, from virtually anywhere, in near-real-time. Failure to enable adequate access to data could result in lack of adoption. An example of this is the Flight Tracker Pro app, whose value lies in its ability to connect to data in real time, providing a live flight itinerary status tracker which analyses a combination of FAA (Federal Aviation Administration), airline, departure and arrival airport data to predict and update your flight status.  

David Akka is UK MD at Magic Software