Is it time for Mobile CMS?

If you want to make a mobile app for your business, the first option that comes to mind is to hire a team (internally or externally)  to design, develop and deploy your app. And it needs to be done on all platforms:

  • iOS and Android: definitely
  • Blackberry and Windows: maybe
  • HTML5 (Mobile Web Responsive): Nice to have

However, going through the above process is costly, time consuming and risky. Making follow up updates, bug fixes and adding features is not easy or fast to do. In response to the above challenges, other options have been introduced: One of them is Mobile Application Development Platforms (a.k.a MDAP). Those platforms help you to fast track the development by providing a set of tools and libraries. At least, in some areas, you won’t need to re-invent the wheel however it still needs development, making the app for each platform, etc.

The third option which can be appealing for some usecases is to use a Design Platform. A design platform, similar to Web Content Management Systems, allows a user to use a visual tool, and by using per-defiend templates, drag-n-drop and point-n-clicks.

The latest option can create the apps for various platforms with one click, however,  like any other platform, it comes with its own limitations.

The chart below summarizes the respective characteristics and rating for each scenario :

The above charts shows, for the usecases that trying new ideas with limited functionality in the shortest time matter, use of Design Platforms is a good option. If a very complex app, with a sophisticated User Experience is needed, a custom development is a better option. MDAP falls somewhere in between.

Above ratings are based on responsiveness to a new requirement including the time, effort and cost to deliver or change an App. The higher the rating and appeal of the other criteria, the better the solution.

Note: The criteria or ratings are NOT based on a specific scientific approach or methodology. It is a guideline on what parameters to consider when selecting on how to make a new mobile app. It also provides an estimation on each parameters and pros and cons for each approach per criteria.

Original document for this post can be found here.

BYOD-X-Curve

As adoption of mobile in the enterprise is growing, the question of who should be able to use their mobile phones at work, for what data and area remains a challenge for both business managers and IT departments.

Also the question of whether using a Mobile Device Management solutions is necessary or not, is another important question to be answered as it drives the cost, usage and how to integrate mobile into the business processes.

The BYOD-X-Curve is a framework which helps to understand the landscape of tuning devices into a corporate device, and come up with a series of questions to make a decision on how to adopt BYOD.

As seen in the below image, answering the Device Policy is a parameter of Security Policy in the organization:

 

Based on the data and the organization, data might fall under Security Compliance or not, when there is no concern over security of data (or it is low concern), usually there is no compliance to be applied to the data, therefore, concern for employees to bring their device to work remains low. If data is considered confidential or needs to be secured, adoption of BYOD becomes more important until at some point, the device that users use, needs to be considered a Corporate Liable Device (vs. personal or Corporate Open Device). The BYOD-X-Curve suggests that use of MDM is directly related to Security Compliance of the organization.

The examples in the framework also shows sensitivity of the data is independent from channel or platform that data is generated or used. For example, even though Facebook is considered an open social network, if a business uses it for advertisement, the information regarding ads, various campaigns, their performance, etc. might (or might not) falls under data security policy. If usually marketing department can decide on  who has access to such data, and such access doesn’t need to be tracked, monitored, etc., then probably managing such campaigns from a personal or open device is ok.

Disclaimer: BYOD-X-Curve is only a framework to provide a guideline on how to think about adoption of MDM solutions. In order to make a decision about it, based on content, use case, organization, data types, etc. the necessity of adopting a MDM solution or BYOD policy needs to be reviewed and analyzed  case-by-case.

The BYOD-X-Curve was presented at Ontario Centers of Excellence Conference, May 2013, Toronto

Licensed under Creative Commons, 2013, (c) Silverberry Group Inc.