Skip to Content

One of the hottest topics in IT is enterprise mobility.  How to make the most use of mobile devices.  How to achieve a good ROI.  How to leverage existing skills sets to build apps.

If you are building mobile apps, you need to accommodate for the wide variety of devices that employees are using or want to use.  Keeping track of those devices, and what applications are on them is also key.  But how do you prioritize all of the options and what are the top issues to consider?

One of the best ways to approach the question is to start with a corporate mobile approach. To be effective in the development of mobile applications, companies need to address the issue of a mobile strategy first, to be able to bring together all the available resources in a comprehensive approach.  Avoiding pitfalls such as not being able to offer a wide variety of devices, or not being able to secure those devices in the event of a lost or stolen device are important.

According to a recent whitepaper by Jorge Garcia of TEC, “A corporate approach to mobile application development makes it possible for organizations to… develop mobile applications using a single, uniform development platform, thereby establishing a single development process strategy (creation, testing, etc.) and a coherent set of best practices”.  You need to remember that data and content must be accessible from anywhere at any time. Applications need to be able to work cohesively with other mobile and non-mobile applications and need to be configurable based on the user’s role and responsibilities.  Deciding from the start what you are going to offer and how you are going to offer it, and setting out a roadmap to get there, will take many of the frustrations out of going mobile.

You can read more about key considerations that need to be taken into account, in this whitepaper; Moving Beyond the Basics: Key Considerations for Successful Adoption of a Mobile Platform. The whitepaper, commissioned by SAP, includes a great visual of what a complete mobile framework looks like and provides a checklist of key considerations for evaluating a mobile application development platform (MADP).

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply