Showing posts with label enterprise mobile. Show all posts
Showing posts with label enterprise mobile. Show all posts

Tuesday, May 12, 2015

Mobile Device End of Life

Mostly when people think of enterprise mobile projects what springs to mind is the process of designing, building, and testing, a fancy new mobile application. When this new application goes live suddenly life is easier, the company makes more money, customers and employees are happier. (For a more comprehensive view read the benefits of enterprise mobility). So where's the "but" you ask? I'm sure you have guessed that not all enterprise mobility projects follow this same pattern. Equally as important as a new application is ensuring that an existing mobile business process continues to operate effectively.

Many companies with a long history of mobile applications have invested next-generation improvements to leverage the benefits of technological advances. Typically aspects of the end to end mobile solution may reach end of life. For example support may become less effective, skills in niche technology become scarce, devices and operating systems change. Additionally user expectations increase along with consumer technology.

In the traditional enterprise mobile space many organisations opted for rugged or military specification devices (and plenty still do). One of the benefits of these devices is that they tend to be supported by their hardware manufacturer for many years. Eventually though this many years does run out. At that point there is usually a scramble to think about new devices and then the doors open to options, alternate vendors, and solutions.

What should you do if you are tasked with taking on an end of device life scenario? Before we get started let's set the scene a little more. Consider Company X has a mobile solution that includes integration to a business system, offline capabilities along with some peripheral integration such as printing and/or scanning, and is leveraging a rugged mobile device that will shortly become unavailable and out of support. This maybe somewhat more complex than users of web applications moving from iPhone 6 to iPhone 7. However in concept the steps are similar, just greatly accelerated in the simpler example.

So now we have some context let's firstly consider the three "environments" of relevance. The legacy, the current, and the future. With all three it's good practice to do due diligence to ensure that you have cost effectively mitigated the risks.

For the existing legacy solution a great starting place is the solution documentation. Anything you can dig up on the existing business case, processes, technology stack, products, application, devices, support and integration will help prepare you for more detailed discussions. Consider for example that the standard operating environment or build of this kind of solution can be quite complex. Prepare a simple one or two page summary of your findings. Once you have the background it's a good time to talk with the stakeholders, users, and support staff to understand the requirements. Again ensure to take notes and prepare a summary.

Next the current environment phase is about understanding what is available in the market and how this will fit with the existing solution. It's time to begin the device evaluation process. For full details of this process check out the following article that covers how to select a device for enterprise mobility. A good process is to shortlist devices and then bring the hardware manufacturers and/or demo devices to the stakeholders to show the relative pros and cons. Don't forget that in our scenario it's not just the mobile device that is important but associated peripherals like printers and scanners.

Once a subset or limited number of devices have been established then it's time to do some testing. Determine the appropriate level of testing by evaluating the delta between your existing and target devices. For a full run down check out this article Testing Enterprise Mobility. A key consideration is to ensure that the software build can be completed. This can be greatly impacted by operating system and hardware changes and may require cycling back with the software providers. Once technically working it's worth field testing with end-users to ensure that any negative and positive aspects of the new device are understood. Ensure that all the testing results have been documented.

Finally consider the future. Change is rapid in the digital space. Is the solution sustainable? Are aspects of the technology now past a point of no return? Is replacing the device the best method to continue to get value from the solution. Perhaps it's more cost effective to replace certain parts of (or the entire) solution based on new software and hardware solutions.  To wrap up prepare a summary of findings along with a recommendation based on the facts.

Friday, March 6, 2015

Mobile World Congress 2015 Roundup

Mobile World Congress 2015 was the largest gathering of mobile marketers, mobile manufacturers, mobile communications, and mobile tech-heads in the world. This is a place where Apple is not represented but was often kicked enthusiastically by their rivals. While Apple does not make product announcements at the conference just about every other company in industry use the platform to showcase their latest and greatest. Each had their presentations honed to perfection and took the opportunity to dazzle the audience with videos, devices, and vision statements.

This year the majority of press focused on phone hardware, wearables, and virtual reality. While the big announcements (especially Samsung) got most of the press it’s interesting to see that different countries had a local flavour to their news focus. The following is a few examples of how each country reported MWC 2015:
  • Australia: the big story from Mobile World Congress concerns a Telco, Optus, releasing a mobile payment watch. I’m sure this will stir up a few financial institutions in Australia.
  • China has plenty of articles on the Chinese manufacturers such as Huawei, ZTE, and Lenovo.
  • India: certainly covered the Samsung and HTC announcements however there has been more focus on the mid-price handsets by Gionee, Sony, and Microsoft.
  • Ireland: is excited about partnership announcements including Brite:Bill Sprint as well as Asavie Zvelo.
  • Japan: along with the generic news on the latest handset announcements, Fujitsu’s Iris technology rated plenty of mentions.
  • Spain: The land of the conference! The news focused on the Samsung announcements, the endorsement of the conference by King Philip VI, and the attendance.
  • UK, USA, Germany: plenty of focus on the latest handsets and watches that were announced. Especially the Samsung and HTC devices.
Of course new phones and gadgets got the most focus so let’s quickly run through some of the key announcements and products that have been of interest around the world (in alphabetical order):
  • Fujitsu’s Iris technology
  • Google’s Android Pay API
  • HTC’s One and Vive
  • Huawei’s smart watch
  • LG’s Urbane watches
  • Microsoft’s Lumia 640 & Windows Mobile 10
  • Samsung’s new Galaxy 6 & Edge, VR &, MST
  • SanDisk 200GB microSD card
MWC is not all gadgets; a number of large organisations announced or reiterated their professional technology partnerships, these included (by far not exhaustive):
  • Apple & IBM for enterprise mobile applications
  • HTC & Valve for VR
  • SAP & Jasper for IOT
  • Qualcomm & Cyanogen for OS on QRD
  • Samsung & Cheetah for Junk Cleaning
  • Mozilla and Orange for Kilf Firefox
Being that MWC is a conference not surprisingly there were plenty of discussions, presentations, marketing and deep-diving on the agenda. Most notably was Zuckerberg’s keynote where he discussed the” Internet for All”, Internet.org program. Mark highlighted the good progress that has been made with partner companies in half a dozen countries. The model focuses on introducing free services that then lead to an uptake of paid data services. Additionally there were plenty of other great speakers and topics on the MWC agenda including:
  • Mobile Advertising and Marketing
  • Internet of Things
  • Mobile Money
  • Mobile Gaming
  • Future of Mobile
  • Mobile Apps
  • Net Neutrality
Finally to wrap up I’d like to leave you with some inspiration. The following quotes have no doubt been tested and sweated over by marketing geniuses before being let loose on the unsuspecting conference attendees. With these terms the speaker’s reinforced company and product visions and they make for a nice comfy feeling the next time your mobile phone rings. In no particular order here are some of my favorites:
  • HTC: “Relentless pursuit of brilliance” & “Utopia in progress”
  • Samsung: “crafted”, “mystical”, “you are covered”
  • Sony: “the wow”
  • Huawei: “Dream makers”, “dreams inspire creativity”

Tuesday, January 27, 2015

Mobile Perspectives

Japan is renowned for its novelty phone covers!  
Opinions are based on experience and perspective. Often statistics about mobility are rolled up and based on a particular geography or demographic. Getting some perspective from a variety of geographies can be a breath of fresh air and allows alternative ideas to be considered. They say travel broadens your horizons, so on recent trips to Japan and Thailand I couldn't help but have a little look at mobile and see if I could learn a few things. 


As soon as you land in Japan turn on your phone and you are met with a plethora of available wireless connection options. While this is nothing unusual for an international airport, what is unusual is that you can get great wireless coverage over most of Tokyo and for that matter Japan. This is greatly different to many other cities and countries. With its dense population it makes a lot of sense to offer this service and it sure makes life easy for tourists! The leading Japanese Telco NTT DoCoMo is partially government owned and therefore reminds me somewhat of Australia’s own Telstra. Likewise the ubiquitous use of mobile phones is common across Japan, Australia, and Thailand. While Japan is famous for its mobile phone culture and holds many firsts in terms of technology surprisingly Japan’s mobile phone penetration is somewhat lower than that of Australia and Thailand (thanks Wikipedia). Not that you notice much difference if anything the greater populations mean you see more phones along with more people, and to be clear, all 3 countries have more phone subscriptions than people. 

In Japan you do notice a lot of different phone models and manufacturers than I have seen in other countries. Having previously worked for a Japanese hardware manufacturer I was familiar with some of these alternative handsets. In the Japanese market for example you will see handsets designed for the elderly. In contrast I predominantly saw Apple and Samsung devices in both Australia and Thailand. Over the years of visiting Thailand I have seen a trend that seems to follow more closely to the US. Not that long ago Blackberries and BBM was all the rage, now it’s Line and Instagram. 

Japan is a very mature mobile phone market, I first visited Japan in around 2001 and can recall sitting in hotel lobby jealously watching people surf the net from their phones. Japan of course has a beautiful somewhat unique culture. Even phone usage has its own term “keitai”. You notice that phone etiquette in Japan is much more mature than in the West. For example people are very conscious of talking on phones on public transport. In contrast while in Thailand I was in a car doing 150km/hour while the driver talked on his handset. 

Along with phones mobile gaming is huge in Japan, much more so than in the West where gaming tends to be dominated by consoles or PCs. Therefore when you are out and about you see a lot more mobile computing devices or game consoles than you would do in the West. Shopping for phones and accessories is quite different across Japan, Australia, and Thailand. In many ways Australian shopping is like a somewhat smaller version of Thailand’s. Both Australia and Thailand have large shopping malls and each mall will have a collection of shops belonging to Telco’s and handset manufacturers. In Bangkok it seems each mall may have an entire floor devoted to mobile. Here you will see all the manufacturers with their own shops often side by side along with an abundant sea of smaller independent accessory and repair shops. Bangkok also has famous phone shopping locations such as MBK or China Town where you can literally get any kind of handset, cover, accessory, or repair work. In contrast Tokyo’s greatest shopping is outside of the malls and different parts of the city are renowned for different items, Akihabara being most famous for electronics. 

In Bangkok each mall seems to have a mobile phone floor with each manufacturer and Telco represented.  
For many years Japan led the way when it came to mobile payments, wallets and the like. Japan’s love of gadgets, vending machines, and automation drove much continuous innovation. The use of mobile technology for payments has grown somewhat recently in Australia with Banks now allowing phones to replace cards in many instances. In Thailand the amount of services offered by Telco companies was more mature than we have here in Australia. For example walk into a True shop in Thailand and you will see banking style services in full swing. 
Shopping in China town you can get any kind of mobile phone accessory, cable, repair job, phone cover, you name it they have it or will make you one. 


If you get the opportunity when traveling to have a quick look at the mobile industry and compare it to your home country we would love to hear from you. Sharing ideas within the community makes us all grow collectively.

Friday, November 8, 2013

The Top 10 Enterprise Mobility Top Tens

A quick little blog to share a collection of information relating to Enterprise Mobility. Everyone likes top ten lists so here is my list of the Top 10 lists covering Enterprise Mobility!:
No reason that this has to remain the ten top 10. If you are aware of any other great resources please let me know and I will add them to the list :)

Sunday, May 19, 2013

An Enterprise Mobility Journey

Enterprise Mobility is more than just software or hardware it's a journey undertaken by business to realise the benefits of a mobile workforce. There is a beginning to the journey but more often than not no end. As with the introduction of other initiatives this journey tends to be circular. If you start from identifying a need, work through realisation, and move into support eventually new needs will arise. Of course that's why it's important to underpin all of this with a view to ongoing change management. Here is one way of categorising the key aspects of an Enterprise Mobility Journey:
  • Business Case
  • Product Selection
  • Realisation
  • Support
Enterprise Mobile Business Case
To stay in business it’s important to consider how funds are spent. Organisations of different sizes and types go through a business case process with more or less rigour. Some organisations may be capital heavy and invest in large equipment or plants. In these cases IT spending may be seen as a small insignificant part of the overall investment plan. For others money spent on IT is core to their DNA. Regardless of the company type there are always competing initiatives for funds. As well as getting a place in the investment hierarchy a business case has a number of benefits:
  • Socialises concepts and aligns vision (Needs)
  • Sets scope and boundaries (Requirements)
  • Defines the costs and benefits (ROI)
  • Acts as a reference for future stages of the mobile journey
While a business case for a mobility project can be treated in a similar fashion to any other business case. Here are a few tricks and traps to look out for:
  • New technology is not well understood
  • Replacing paper processes may have greater benefits than replacing an existing system
  • A mobile application could form part of marketing / advertising spend
  • Mobility investments often establish the basis of multiple projects
For further reading refer to these articles:

Enterprise Mobile Product Selection
At the outset it's worth mentioning that no one has a working crystal ball and it's clear to most that mobility is an area of rapid change. Often people ask me how can they trust product Z when last week product X was the leader. This is the same argument many people have when they are looking to buy a new personal mobile device or other technology. "Should I buy model X now knowing that in a few months perhaps a new model will be better?" My response is to harp back to the business case and requirements. If you know that the delivered features will enable you to achieve your business goals then you can feel comfortable. Consider when NASA built the Mars rovers they didn't look for the most recent or powerful mobile device, they used a clear list of requirements.

Of course there are a number of technical solutions to mobilising an enterprise so if the technology is new to you consider some of the following:
  • Industry events (get some insight, network, and talk to experts)
  • Similar non-competitive companies (perhaps another geography)
  • Web & Social (plenty of people willing to help)
  • Existing partner network (your solutions partners may have expertise)
  • Research firms (such as Gartner or the newer crowd sourcing alternatives)
  • Back end connectivity (ensure your technology integrates)
  • In house talents (mobility is an exciting area for many people)
  • Platform or point solution (does your case allow for future expansion)
For further reading refer to these articles:

Enterprise Mobile Realisation
The realisation phase of a mobile journey is where the rubber hits the road. The scope of this phase can vary widely depending on the business case, the product selected, and the implementation approach. Ensure that before too much rubber has hit the road all involved parties agree on the way forward. There maybe a big difference between leveraging an existing cloud solution and a more traditional waterfall driven software project. Regardless of how agile (or not) the project is each will (or should) have a a degree of:
  • Design/Confirmation
  • Build/Implement
  • Test/Train
  • Pilot/Deploy

During realisation is of course a key time to be referring back to that business case and most specifically the requirements. Oh and if you're looking for a great result never forget the importance of business and IT change management.
For further reading refer to these articles:

Enterprise Mobile Support
One of the easiest traps to fall into is to leave support to the end of the journey. It's important that support and supportability requirements are baked into the business case. Supporting mobile applications and hardware has a couple of added complexities that traditional desktop support may not have to contend with:
  • Unreliable communications
  • Bleeding edge technology
  • Frequent change
  • BYOD
  • Many layered fault determination
If you have considered support up front then hopefully you have a solution that includes tools to empower your users and the support team. Finally a couple of points on the importance of baking Change Management into the entire journey. From an IT sense consider how to handle software/hardware updates and the impact of change to other systems. From a business perspective consider the people, the process, and how mobility changes the game.

Monday, May 6, 2013

Apps Tech News

A quick blog to mention the team over at www.appstechnews.com. As well as publishing some of my blogs they post a variety of news and articles from much better authors. Topics include:
  • Analytics
  • BYOD
  • Cloud
  • Data
  • Enterprise
  • MDM
  • Development
  • App Stores
  • Device
Not just a syndicating service, Apps Tech News also formulate opinion pieces and collate information into great articles on current topics. For example the "Is Blackberry CEO right to question long term tablet future" piece by James Bourne included quotes from Jim Hemmer (along with yours truly!) as well as analysing and reporting on industry sentiment.

I'd recommend adding App Tech News to your bookmarks (along with this blog of course). Keep up the good work !

Monday, April 15, 2013

Facebook Home, Skins, and Future Social Mobility

Facebook home released and is officially available for a variety of Android devices. Like with most Android applications it is unofficially available for any device with a compatible Android OS. Leading up to the announcement there where plenty of rumors about a forthcoming Facebook phone along with speculation that Facebook was moving into hardware. In such a dynamic space I would never rule anything out but it does seem sensible for Facebook to "Play" (pardon the pun) to their strengths.

A couple of things I find interesting:
  • Facebook a serious player in the skin game?
  • Who else will jump on board?
  • What's next with this social stuff?
Facebook is the most popular social networking site in the world used by a very wide audience. If anyone has the reach and software skills to make a skin successful it is Facebook. However the skin game has never had a huge degree of success in the past. Hardware manufacturers and telcos have traditionally provided skins to phone Operating Systems for branding, user information, loyalty, lock-ins, etc. The tech community would always cry foul and try to find a way around the skins and this noise (citing poor performance, lack of flexibility) would often filter down to the general user community.

Similarly in the desktop space the concept of a skin sitting above the Operating System has never had wide success. Unlike iOS most desktop operating systems allow quite a degree of easy access for users to change the look and feel. Many in the tech community would argue that what makes Android great is its flexibility. The Android OS for mobile phones defiantly allows a wide degree of user customization compared say to iOS. However how many users really change more than the background picture and layout of the icons? With more focus on user devices in enterprise the ability to tinker is of course a mixed blessing. Don't get me wrong the quest for better user experience is important and experimenting with skins, overlays, and changes to operating systems are to be commended. After all you could argue that the Windows GUI was a skin on top of DOS.

It's been reported that after Facebook, Linked-In is the next most popular social networking service. In my experience Linked-In tends to have a more business focus. Will Linked-In build a corporate friendly Android skin? If they can bundle features that both corporate and social net-workers want together they could get some real focus. For example they could combine separation of work/personal space, added security layer, and social networking.

Other players that everyone will look to for a similar concept are of course Google+ and companies like Line. One feature that both of these offer is the groups or circles concept that allows controlled sharing of information to specific audiences. While I really like this concept I don't think many enterprises will risk an employee accidentally sharing a proposal or costing with the wrong group. This degree of control needs to be built into the core of social networking.

So in future Social Networking for Enterprise I would like to see secure sharing of information socially with low risk. Allow me to share documents and chat with my colleagues from my work-space/phone/internet device without the ability to accidentally share content with non-approved contacts. A system of this kind would encourage participation by using familiar tools and enable merging the consumer and enterprise social aspects. A secure social framework would be a good launch pad for collaboration ideas such as Gamification.

To enable this vision there probably needs to be a social networking standard or protocol for ubiquitous sharing of contacts/messages/content/likes (and the like). Upon this kind of foundation plugs-ins could then easily merge say Microsoft communicator with Facebook, Google+, and Linked-In. Contacts could be common across different platforms and the user would be empowered to chose a context specific interface depending on their circumstances or needs.



Monday, March 25, 2013

Enterprise Mobile Prototyping

Projects involving technology that is emerging, changing rapidly, or where the stakeholders are not experts will benefit greatly from prototyping. In these conditions it's difficult to get the best value out of a traditional 'blueprint everything up front' approach. Of course I'm talking about enterprise mobile projects here.

As well as not understanding potential pitfalls it would be easy to miss out on leveraging all the possibilities of the new technology. On projects I have worked on in the past I've attempted to leverage the build tools for prototyping (or just mocked up things and discussed them over a projector.) Of course depending on the tool being used this can be problematic. Sometimes just getting the tools installed and setup can take quite a while. Often the build tools are not suited to quickly producing useful prototypes.

With a mobility related project some of the true "right once deploy many" MEAP options will let you pull off a prototyping approach. However depending on the specifics of the project you may not have the luxury to pick the tools or the timeframe. Even when all the stars align how do you effectively gather feedback from your audience?

Along comes a product like Intuito which enables rapid prototyping on device along with useful feedback mechanisms from a cloud solution. I'd previously written a brief article about intuitive prototyping and have since had the opportunity to try the product for myself.

How does it work?
Intuito let me import screen mock-ups and quickly set hot-spots to simulate swipes, clicks, and other user interactions. I took a Power-point mock-up I had from a previous project and exported each slide as an image. In a few minutes I created a working screen flow. To test it a shortened URL was generated and I opened it on my iPhone. I made a few tweaks, retested and within 30 minutes I was happy with my flow and felt comfortable using the Intuito tool.

I should mention that while you can pass around some variables and simulate a number of different interactions Intuito doesn't pretend to be a full blown application builder. You cannot "code" screens and build logic or complex navigation. To be honest for rapid prototyping you probably don't want to. To simulate some user interactions I duplicated a couple of the Power-point slides and changed some data in the mock-ups.

Ok so that's pretty good, but wait there's more. Once happy with my screen flow I was able to create survey style questions for each screen. This allows testers to immediately respond to what they have seen. Intuito also gathers a heat map of where and what users are interacting with. Since it's a simple link you can easily distribute the prototype to a testing group. As the audience use the prototype the feedback is gathered and displayed in a dashboard for analysis.

Incorporate into a Mobile Application Project
The inputs for Intuito are a screen flow concept and screen design mock-ups. To get the best results the inputs require skills like UX/UI/Graphic design and depending on your application may require business and technical specialists. Of course it's worthwhile to temper the design with the technical feasibility of the development tools, device platform, data, etc. The beauty of the prototyping approach of course is that you can rapidly (and cheaply) produce, test, change, and repeat.

When to use
The adage about spending more time on design and less on build rings true. With prototyping tools the focus can be on design without needing to spend so much time. These types of tools can be leveraged in various project phases for example:
  • Part of RFP/RFQ process to build a mock-up that can be quoted on.
  • During the design/blueprint phase to finalise an agreed functional design.
  • Throughout the build phase to prototype traditional blueprint/designs.
  • Ongoing in support/run phases to formalise change requests.