Like it or not, enterprise mobile apps should not be created equally.
Design and usage considerations aside, there may be many varying criteria for how enterprise mobility apps should be modeled, created, and perhaps licensed.
There are at least three emerging classes of enterprise mobility users: (1) industrial mobile users [industrial mobile devices within the four walls – with constantly working connections], (2) occasional mobile users [in-the-field or remote users on tablets or smart devices – dial-in or WiFi connections], and (3) casual mobile users [middle management or executive users on tablets or smart devices doing inquiries or approvals – dial-in or WiFi connections].
Major ERP vendors, like Oracle EBS and SAP, are in the development and roll-out process of extending the footprint of their ERP software to mobile devices. These ERP vendors contend that users of their software should be licensed regardless of how the information is accessed – from a desktop PC, a tablet, or a smart phone. Their licensing schemes to date for these new mobile ERP offerings seem to be gravitating towards a “transaction” specific license so that only the users with that specific mobile transaction need are licensed.
BYOD users have grown accustomed to downloading free or inexpensive apps with very cool interactive features. Imagine the sticker shock when downloaded ERP licensed apps cost hundreds or thousands of dollars for a single ERP transaction!
The jury is still out on how this per transaction licensing model will stand because this is an important economic consideration by IT departments as they try to manage, control, transfer, and contain the growing cost of Enterprise Mobility.