The Shifting Mobile Strategy of Enterprise Devices
Eleven years ago, Steve Jobs stood on the stage and boldly introduced the iPhone, sending a shockwave through the technology community and ushering in a new era for mobile devices. A year later, the Android platform was launched – the Darth Vader to the Jedi iPhone. Instead of being told what you need, Android provided openness and experimentation. Unlocking the potential of a mobile device and providing a counterbalance to Apple’s closed (these are not the Droids you seek) operating system. This new wave of devices opened the door to numerous possibilities in enterprise mobile strategy. These devices also required new types of enterprise administration through mobile device management tools. Some companies are testing and investing heavily in replacing rugged, Windows CE legacy devices with cheaper and sleeker consumer mobile devices.
Target’s Shot Across the Bow
For the uninitiated, acquiring rugged mobile devices (especially at scale) is an intensive exercise. It involves negotiations with value-added resellers for the actual devices, device insurance, repair services and sometimes even storing a pool of spare devices. These devices are not cheap either, often costing more than $1000 per device.
With the availability of consumer devices at a fraction of the cost of rugged devices, many enterprises invested millions of dollars in deploying consumer-grade devices. From a numbers standpoint as a business use-case, this was a slam dunk to sell to leadership. You can imagine the pitch went something like this:
CIO/CTO: “We are going to deploy Apple devices, which are 1/5th of the price of our legacy devices. Even if we replace every device twice, we are still spending less money. Also, everyone is familiar with iOS devices, and Apple has spent millions on user experience that we can leverage for our applications.”
Many retailers like Target, Lowes, JCPenney, and others took this fateful leap of deploying consumer devices replacing rugged legacy devices. However, these retailers have since moved back to rugged devices like the Zebra TC70 & TC51. Here is what their leadership missed by not having the appropriate context for what makes enterprise rugged devices unique and worth the investment:
- Drop Specs: Can the device handle hundreds of drops from 4-6 feet and continue to function normally?
- Battery Cycles: In some environments, devices will run 24 hours a day, every day. What is the charge cycle for the battery, and can it be replaced easily?
- Missing Devices: Consumer devices seem to get lost and end up on eBay at a higher rate than their rugged counterparts.
- Mobile Device Management: Some consumer devices are harder to manage than others. Apple devices, for example, have a narrow set of features for mobile device management and the enterprise administration. Conversely, Samsung devices with support from Knox can support almost any enterprise scenario.
- Analytics: Some devices will not allow for granular data to be captured. This goes hand-in-hand with mobile device management. Take time to understand the analytics requirements and experiment to validate that the information can be captured.
- Harsh Environments: Most consumer devices are not specced for harsh environments and rely on expensive cases/sleeves to meet certain rugged requirements.
If your organization is dealing with any of the above scenarios when replacing legacy devices, then save yourself the pain of trying to make the impossible possible.
Companies Need Different Devices for Different Purposes
Companies like Delta Air Lines have a well planned and effective enterprise mobile strategy. Delta leverages different devices based on the role, environment and required tasks. The employees loading airplanes on the ramp need mobile devices as rugged as Thor’s Hammer and for everyone else (e.g. flight attendants, pilots, gate agents), there are consumer devices.
When evaluating your enterprise strategy for the next 5-10 years, there are a number of aspects to take into consideration, including:
Will the devices be carried by a single person and used for personal use?
Consumer devices are great when supporting a Bring Your Own Device (BYOD) strategy and even a BYOD strategy using company-issued mobile devices. Mobile Device Management (MDM) platforms like AirWatch, Soti and Playbook MDM allow organizations to provide secure access to enterprise applications and company data. Employees should be able to utilize amazing applications that leverage the Android / iOS devices they are already using.
This can start to go wrong if your organization makes it a free-for-all when supporting devices. Even if the enterprise mobile strategy is to go with Android supporting Nexus, Samsung or LG, the slight differences in each manufacturer’s hardware can make it cumbersome for Help Desk and business mobility dev teams to support and account for. Selecting one device platform or even one manufacturer can make the world of a difference when executing a consumer device strategy.
Will you need to support larger displays for customer interaction?
Let’s not forget about tablets. There are two instances when leveraging a tablet should be considered:
- Display information on a larger screen format: Often there is a need for a larger display to showcase specific information. For example, designers sharing work with clients, construction workers that need access to CAD drawings and pilots who need to access to flight maps.
- Device hand-off: There are scenarios that call for the device to be used by a 3rd party (i.e. patient or customer) for data collection. A nurse gathering information from a patient to pre-sales resources capturing leads in the field. These are just the tip of the iceberg for leveraging tablets.
Do we have documented requirements for how the business will use the devices?
Are these devices being used for a task that requires a small format device or leveraging the hardware? For example, capturing form data in the field with text and/or media with the ability to immediately submit to a backend system or store & forward. Tracking assets or proximity to assets leveraging BLE and leveraging the mobile device as a gateway for IoT sensors. Lastly, capturing video, audio and voice transcription in the field with the ability to add geolocation metadata.
How will you determine which software technology to use on your devices?
When converting applications for consumer devices, developer tooling and technology selection becomes increasingly important. The easy choice is to pick one platform and support the native stack as part of your enterprise mobile strategy. However, most organizations fear being tied to a single platform with high switching costs or critical dependencies in case they need to switch platforms or introduce a new platform type in the future. Below are some of the hybrid language options:
- Pros: Lots of community support, availability of component libraries, developed and used by Facebook.
- Cons: It’s not a true framework so there is not one right way to implement.
- Pros: Dart is a promising language, included widgets reduce the need for design and the output is a native iOS and/or Android application.
- Cons: Based on Dart which is a language developed by Google and still new to the market.
- Pros: Deployment flexibility, lots of community support & example and many framework options to choose from.
- Cons: Lack of native UI and experience but the gap is ever shrinking.
- Pros: If you fancy your organization a Microsoft shop you can continue to say that and write applications in C#.
- Cons: The development workflow is slower than the native platforms and other hybrid options.
What are the hidden costs involved in our mobile strategy?
Time is money! The points below are areas where huge chunks of time could be sunk upgrading business mobility.
- Sourcing replacement devices – The deployment of the 2018 insert consumer device here has been deployed. What happens 18 or 24 months from now when devices need to be sourced for breakage replacement? This will add to the research and testing now that a 2020 device needs to be vetted and most likely a newer OS as well.
- Staying ahead of OS Updates – Consumer devices are provided OS updates as they are made available by the manufacturer. Also, there is a lack of features for preventing or allowing the updates to be controlled so be prepared for a device fleet with a range of OS versions.
- QA Testing across multiple devices – Testing is easily overlooked and marginalized when developing. The same is true when estimating the amount of time it takes to validate a deployment across multiple devices and multiple versions of the same OS.
- Finding workarounds for lack of device access – Zebra has their EMDK and Samsung has Knox which makes controlling any of their devices possible. When you lack these tools, your developers spend an extraordinary about of time finding workarounds that are mostly dead ends.
- Choose the right device for the right environment – If the device is not appropriate for the environment then this blog post will not save you. Allow your requirements to drive device selection and do not lead the device selection process with a price.
- Narrow the device focus – Having a diverse device mix increases the complexity of your technology organization. Reducing fragmentation reduces the development, testing and support cost. Everything that can be done to reduce the number of devices supported will reduce the risk of a bad experience.
- Pick the correct technology stack – Making the correct selection can make or break an organization. Choose wisely and you’ll be rewarded with a team that can move at the speed of light to fix issues in the field and delivers new features/applications to the business.
Overall, consumer devices do have a place in the enterprise. However, without a comprehensive strategy and understanding of how to properly leverage consumer technology, history will continue to repeat itself.
If you need help with your mobile strategy or want feedback on your technology selection, feel free to reach out for a free consult.