Need for MobileUI in ECM Systems

Standard

Recently I faced an interesting problem therefore thought to share it here, our ECM system is the single source of truth for standards and policy related documents. Also it’s easy to share the link of the document rather than attaching the whole document while sharing information.

Since most of the users check their emails using mobile devices, therefore now they are facing a new issue. Whenever they try to opens a document link shared using email, it tries to open the document in mobile browser using the same layout as if it was being opened on a desktop. This makes it very hard to open and edit the documents.

This issue has created a demand for a mobile compatible interface for our ECM system so that they can at least browse and read content using mobile devices.

It’s interesting to see, how just moving one application (emails) to mobiles, has created a demand for mobile compatible version of another system (ECM).

Most of the ECM technologies needs add on modules (with extra licensing cost) to support mobile devices. Or a mobile app needs to be developed using SOAP or RESTfull APIs.

We are using one of the product from Leaders Quadrant of Gartner Magic Quadrant for ECM and we have two options 1) either pay to buy a new product for mobile compatibility or 2) develop our own app using APIs.

This is one of the areas where new vendors like Box.net have an advantage over established players, as it is built for cloud and mobile. It works smoothly on all kind of devices (desktop, tablet and mobiles) without any need of customization or add-on software.

A piece of advice to ECM vendors, don’t just design a system which works on desktops only, design a adoptive UI so that default it can be accessed from any kind of devices.