I have several types of mobile devices, both low-cost Android tablets and iPads and smartphones of all types and vendors. Maybe you've discovered problems similar to these I list?
Not sure how it starts: an organization's start down the road to mobile assimilation. Most stories I've heard detailed how different top managers at different organizations of different sizes nonchalantly opened a leather cover during a big meeting. hey revealed an iPad or Nexus or some other tablet and began checking their email. And by checking email, I've confirmed that that means reading and navigating through email. Soon, everyone wants that look, that look of mobile productivity. But let's take a closer look at those devices.
The first thing I notice about many devices is the lack of storage. I'm an information worker. I review, transform, enhance, and refine information from raw data. My storage is HOW LITTLE??? Of course, we're all assured that the applications are a lot smaller, requiring less storage. Good thing, too. Many devices have no flash storage ports? Huh?
So you start the journey by cabling your mobile device to your PC and determine which music, which pictures, which other slivers of your Digital Life you can store on your mobile replacement for the PC? What??? Fail One: Too many mobile devices have a dependency on PCs for re-powering, for file exchanges, for repository storage. Instead of being a replacement, your mobile needs a PC Sync-Buddy, a Repository with benefits. How's that for lowering your IT spend? Don't believe me? Check on sales of companion Mac sales happening alongside iPad sales.
Also, do you want to do more than play games or music? Let's check on the claims, "there's an App". I need to review a lot of complex data, often in complex, proprietary formats. How much does an office suite cost? Can it open and output data formats I use at work? Consider the dearth of software until Office was available on iPad. Most software was limited to utilities, games, and the like. Attempting to open a file received through email was difficult. The file was large; the storage was not. The translation of complex formatting was broken; the re-encoding from off-brand "awfist" suite to Office suite was also often broken. Nightmare Fail Two: Business software tough to find and use.
And if you wanted specialized software for your profession? Niche software is often nonexistent or requires home coding. And speaking of niche coding, what's your take on coding languages for mobile development? Which language has an adequate IDE, ready set of libraries and classes, and an easy-to-use yet powerful syntax?
I think a massive fail, for me at least, is mobile data input. After paying $700 for a name brand device, just to be limited to its pseudo keyboard obscuring an already small display, you want something bluetooth. And that's how much? And how big is it? Fail Three: Cost of peripherals. Get a cheap keyboard, and it feels like pressing some lumpy oatmeal. Get one with a better leather case, and you press keys the size of tic-tacs. This is not conducive to making progress. You look essentially, slow and dull-witted as you peck out an email with all the dexterity of a new student using, "The Big Crayons".
I could go on and on. Weird charger cables that require a multiple purchases to keep the battery charged because capacity never lasts as long as advertised once you enable the Wi-Fi and blue-tooth radios. Oops! And who can help when off-brand, lithium batteries refuse to charge, and it's a sealed device? And let's explore the fun we all have when it's time to buy another device because these computers are more like disposable lighters. Switch phone platforms, and it's another round of car charger updates in many cases. But what's the most hidden, most epic fail?
Epic Fail Four: Security Flaws and Slow Updates. StageFright? A big Fail in Android. Google Hangouts accepting any and all input from unknown senders? Naive! So what if Google issues a patch for StageFright today? Does that mean my phone vendor will make it available for my phone today? And what about patching my older Android tablets that never went beyond older versions of Android, possibly with a vendor that went out of business?
Hey out there! You mobile vendors! I'm supposed to base my work on tools that have uncertain patching technologies and policies, on a platform that just this year adopted monthly patching?
No, for these and other reasons, I'm sticking with PCs, but I'm moving to today's PCs and today's OS. And I'm not settling for just Internet surfing or music playing. I want the real computing experience.