ARCHIVE FOR THE ‘cathal-mcgloin’ CATEGORY

Cathal McGloin, CEO of mobile enterprise app developer FeedHenry takes on the role of myth buster as he debunks a few false beliefs regarding mobile development across the enterprise.

This is following the mobile app platform provider analysed customer data and industry RFPs from organisations with more than 1,000 employees.

Myth #1:  Enterprise apps take at least six months to develop and deploy

Industry received wisdom dictates that apps, especially those designed for enterprise, can take at least half a year to build and launch. With some organisations requiring anywhere from 10-100 apps to serve different business units, the time required to build apps can appear prohibitive. However, the right mobile platform can halve app development time to just 60-90 days. The key is to reuse code and backend services where possible in order to speed integration.

Myth #2:  Data is king, but it's too complicated for apps to access legacy systems

Enterprise organisations that have already made large investments in systems, such as ERP, are hesitant to develop mobile apps that cannot seamlessly plug into existing mission-critical technologies. On average, a suite of enterprise apps connects to between 2 and 6 backend systems and APIs, including Sharepoint, Oracle, MySQL and SAP. Because 2 in 3 of these backend systems do not have accessible APIs, this can slow down the development process or make mobile apps unusable. Using an enterprise-grade mobile backend as a service (MBaaS) with an API infrastructure solves this issue by enabling legacy systems to be easily accessed by mobile devices.

Myth #3: Mobile app developers must keep up with a myriad of coding languages and frameworks – it's impossible

Learning new development languages in order to build individual apps for each device platform can be tedious, and for some enterprises entails constantly hiring fresh developers with different skill sets. According to Forrester, when creating hybrid cross-platform apps, developers often employ as many as 10 different coding languages for enterprise app development projects. Common coding languages required include HTML5, JavaScript, Objective C, C#, Sencha Touch and Node.js. and these don't even include languages proprietary to traditional MEAP platforms. To simplify development, developers can use mobile app platforms using a "Bring Your Own Toolkit" approach that allows them to use the languages and toolkits they are most comfortable with.

Myth #4: Enterprise apps are always data-heavy, placing high loads on handsets and backend systems

The best mobile app platforms take large amounts of data from the backend and transmit a small filtered set of data to the handset: reducing overall demands. For each enterprise app session, the size of data transferred for each app should be less than 1MB.

Myth #5: Having a "Chief of Mobility" is the best way to handle company-wide app development

This myth assumes that one central figure will successfully oversee app development and deployment across the enterprise. In reality, the average enterprise mobile app development project requires at least 20 personnel, including business heads, developers, project managers, IT and employees. By collaborating and using the same technology standards and requirements, a Mobile Centre of Excellence or Mobile Steering Committee can guide mobile projects across multiple business units without creating new silos.

Today's technology allows for the swift creation of apps without vendor lock-in should take advantage of the new technologies at their disposal. Agile, open, collaborative and powerful cloud-based mobile application platforms now render obsolete long-held notions around lengthy and complex app development and deployment.

Check out FeedHenry's infographic that outlines these 5 myths here!

When the Spice Girls arrived on the scene some 18 years ago (has it really been that long?) they predicted that what we wanted, what we really, really wanted was a Zigazgaarrr (whatever the hell that is). To be frank, that prediction hasn't come to much fruition. However, Feed Henry CEO Cathal McGloin's assertion that multiple OS and a choice of devices is what we really, really want (in field service at least) carries a bit more weight and may 'spice' up field workers' mobile experience...

In the beginning

Traditionally, field service teams have been equipped with rugged mobile devices, running some flavour of Microsoft's compact operating systems (generally either Windows CE or Windows Mobile), to allow engineers to tick off work orders and update inventory. Defacto wireless devices have been rugged, heavy notebooks or tablets, with limited functions and based on proprietary or embedded technologies.

Greater expectations

As field service employees have enjoyed their own consumer smartphones and tablets, their expectations of workplace mobility have changed.  Industrial handhelds appear archaic next to the latest Android or iOS smart devices. This is driving a shift towards acceptance of consumer mobile devices as the new rugged industrial mobile handheld. Attendees at the Field Service Europe Conference held in Amsterdam last October, were polled on their investment plans for workforce management and mobility. In the resulting 2014 European Services & Trends report, 43 per cent of decision makers reported that they were allocating budget to providing tablets to their field service teams, while 33 per cent reported that they were investing in smartphones.

It’s a hard knocks life

Despite being more expensive, Windows ruggedised devices had the edge over smart devices from Nokia, BlackBerry, Samsung and Apple, because their operating systems could not support field service apps such as Cognito and SAP. In addition, Microsoft devices were well-supported by an array of peripherals such as handheld printers, scanners and bar code readers. However, Microsoft failed to gain traction with Windows Phone, its successor to Windows Mobile, opening the door to Android, iOS and Blackberry to step in to the market. In terms of app development for smart devices, cross-platform solutions and toolkits have made app development faster, more affordable and easier, while also enabling apps that run on multiple OS platforms. While the newer smartphones and tablets provide attractive user interfaces and much richer functionality, some level of ruggedness is necessary to avoid downtime caused by battery life and the harsh working environments that field service employees operate in. Some organisations have addressed this by using rugged covers for consumer devices. VDC Research analyst, David Krebs, has highlighted problems with the ruggedisation of smartphones and tablets using simple covers. He points to their lack of robustness when field service employees are working in damp and dusty environments; problems when employees try to operate swipe screens while wearing protective gloves; poor battery life and device failures caused by vibration, knocks and temperature extremes. Conversely, ABI research found that the total cost of ownership (TCO) of a smartphone-based mobile field service strategy was up to 85% less than alternative rugged device deployments. These savings come from the smartphones' lower hardware costs, as well as increases in efficiency, owing to their connectivity, usability and portability, not to mention the lower cost and greater flexibility of app development.

Best of both worlds

When asked, most field service employees want the appearance and ease of use of consumer devices, combined with the robustness, stability and battery life of a traditional field service device, running apps that help them to work more efficiently. What we have to remember is that not every field service employee is working in a damp, dusty tunnel. Different roles demand different devices. In the same report 66 per cent of respondents stated that their organisations now view field service as a profit centre rather than a cost centre. As a result, we are starting to see enterprise demand for apps that can work across different devices and multiple operating systems, so that field service employees can select the devices that make them most productive.

Enterprisation of consumer devices in field service

We have worked with logistics, rail infrastructure and construction companies, that are starting to adopt new robust devices from Panasonic, CAT, Samsung, powered by Android. Even Apple devices are starting to make an appearance. These Android and iOS devices have a much larger pool of app developers and ISVs to feed them, as well as the availability of more modern software toolkits to accelerate the app development, deployment and update cycles. Legacy Windows apps appear very limited when compared to the latest field service apps being written for these smart devices. Typically, these enterprises have field service departments employing hundreds or thousands of skilled people, performing a variety of roles. Working with an enterprise mobile application platform provider like FeedHenry, these organisations are able to rapidly develop, deploy and maintain a range of sophisticated apps, tailored to a range of job roles within their field service departments. These apps can be managed on premise, or cloud-side, regardless of the devices selected by their engineers, quantity surveyors, foremen, crane drivers, radio and radar specialists and electricians.

Ask field service employees what they really want

From speaking to our own customers, the critical considerations for a sound field service mobile strategy are: 

• Seek input from actual end users before specifying device type and app functionality. The trend is towards a multiple OS environment, so plan for this in terms of sustainability and portability.
• Select open standards so as to increase the available pool of developers, access to developer toolkits, code re-use,while avoiding vendor lock-in
• It’s not just about creating an app. Consider the whole app lifecycle and how this is managed. Apps, by their nature, require frequent updates and upgrades so choosing an infrastructure that supports this will quickly pay off.
• Evaluate your enterprise data capture and backend system integration requirements The ability to unleash data efficiently, securely and seamlessly to the device is critical.
• Consider the durability and environmental conditions that the devices will have to withstand. Protective cases help but do not always address the full spectrum of device durability issues such as exposure to extreme temperatures, dust and vibration. However, expect that innovations will give consumer devices a better fit for these harsh environments.

ABI Research has found that the primary benefits that drove lower TCO for ruggedised smartphones were improved worker productivity and lower device costs. Productivity benefits were achieved through the longer battery life of smartphones, integrated mobile voice and data connectivity and the ability to push application updates over the air. Smartphone device costs are as much as eight times less than rugged devices. Even considering the higher replacement rate for smartphones, ABI has found that lower lifetime hardware costs are a key driver for companies choosing smartphones over rugged handhelds for their mobile field force applications.

Back to the Future

According to a recent report into mobile workers’ device preferences, undertaken by Aruba networks, 45 per cent reported that they want to be able to connect and communicate with the business from their cars. A fifth of the survey sample stated that they want their employers’ to provide them with wearable technology within the next five years. When organisations use an end-to-end mobile application platform (MAP), field service employees can gain the freedom to select the right device for their job, without sacrificing any app functionality. This is because MAPs securely link enterprise back end systems with mobile apps that can support multiple OS and various device form factors, so employees can select the device that is most appropriate to their working environment. Meanwhile, enterprises gain the ability to plan their mobile app strategies to support current and future devices, without having to redevelop code for every new batch of devices.