In days gone recently by, there was a gulf between the folks who developed an application and the end users. Between these two constituencies were all kinds of IT specialists who supported the end users and managed devices.
But in the world of mobile computing, the relationship between the end user and the developer is becoming more intimate. To that end, WorkLight, a provider of tools for developing mobile applications, recently released version 4.0 of the WorkLight Mobile Platform to give developers the ability to control applications on mobile computing devices, including deleting applications that become outdated or are deemed a security risk. Via WorkLight 4.0, developers can also deliver notifications to multiple Apple iPhone and iPad devices and Google Android mobile computing platforms via a single console.
In addition, WorkLight COO Kurt Daniel says one of the most important attributes of WorkLight 4.0 is that developers can work with a mix of Web and native application code to build Web applications, which helps mitigate one of the hidden costs of mobile application development and management. This is one of the primary reasons that Fiserv, a provider of financial services, announced that it is going to use WorkLight to build and manage mobile computing applications.
As enterprise IT organizations rush to embrace mobile computing devices, many are finding that supporting the native environments of each mobile computing device may prove to be cost prohibitive. They are also discovering that HTML 5 may not be mature enough just yet to support all their requirements. As a result, Daniel says we should expect that for the foreseeable future developers will be building applications with a mix of native and Web components.
With the rise of mobile applications, IT organizations are going to discover that the numerous updates that these applications require are going to put an additional burden on their internal IT support operations that they may not be able to handle. So before that happens, maybe the time has comes to narrow the divide between the developers and the end users as part of a bid to help preserve the sanity of the overall organization.