Microsoft is now coming out with a Windows Surface Phone. I personally have mixed feelings about this. Microsoft has certainly got the money and interest in doing this and with Continuum, Microsoft is far and away the furthest in combining the power of the desktop into the form factor of a phone. But there are problems:
First, the Microsoft Surface Phone operating system is still Windows. Some people might balk at that just by itself, but I think the Windows Mobile OS is very easy to use. However, from a privacy perspective and with the latest backdoors that have been identified and opened up for anyone who wants access, this is definitely not a good investment if you worry about your security. Maybe Microsoft will come around on this issue, but for now I can’t in good conscious recommend any Windows OS in any form factor until they remove the backdoors.
Secondly, the app ecosystem is definitely not as good for the Windows Surface Phone if things stay as they are today. Not even close. I talked with one ex-Microsoft employee who said the strategy will be to integrate as closely as possible with the Android market place so that they can leverage Android apps. That’s smart, and by having Ubuntu under the hood and built into the OS that makes Android integration a lot easier, I’d imagine. But without a strong app ecosystem, I can’t see Microsoft doing well. This will have to be announced along side the Windows Surface Phone or I doubt their sales will be much better than any previous attempts at Windows Mobile devices.
It’s cool, it’s got a lot of promise, but with the backdoors and lack of apps, it’s not something I’d recommend for other Smartphone Execs out there. I bet a lot of this will change for the better, but there’s work to be done. It’s a shame though, because Microsoft does have so many advantages with it’s seamless environment switching due to Continuum. But they won’t be the last to pull that thread, I have no doubt!
Traveling really is awful for all kinds of reasons. But from a work perspective it’s even worse. Not only is it hard to do work on airplane because it’s cramped, you also have to worry about people looking over your shoulder.
Privacy screens are polarized film that go over your screen and act as both a protector against scratches but also make it hard to see what you’re looking at from an angle.
In these pictures you can see the image completely, but from the side it’s very difficult to tell what I’m looking at. If I were to dim the screen it would be almost impossible to tell I’m even looking at a lit phone except for the ambient light around the edges.
Now be warned, it doesn’t work in the vertical dimension, only the horizontal, so if you turn the phone into landscape mode it will still be visible. But as long as you know that and keep your phone in portrait mode, it becomes a lot harder for people to see what you’re doing unless they’re right behind you.
The new Apple headphone jack, or lack thereof is perhaps the most talked about gaffe of the cellphone area after maybe antenna gate or bend-gate. But for business travelers it is more than an inconvenience.
If for some reason you really did believe that Apple’s new headphone tech was the wave of the future I have several issues that still need to be discussed.
Bluetooth still isn’t perfectly safe. It broadcasts your MAC address and can be used by attackers to figure out who you are as you travel. It’s the main reason I disable it when I’m in airports or out on the town. It’s okay in a conference room or at home where everyone there already presumably knows you. But beyond that, it’s really not a great idea to keep turned on, and that is assuming there are no vulnerabilities left in it beyond that, which I would never assume. More attack surface is bad. Weary travelers have enough to worry about.
It’s not noise cancelling. For those of us who have to do international travel, the lack of noise canceling capabilities is not just a slight inconvenience, it’s the difference between getting a decent nap and hearing the annoying conversation behind you about conspiracy theories by two misinformed luddites for 8 hours straight.
The battery life on the headphones are 5 hours. That’s not even long enough to make it through one international flight and definitely not one with a layover. Please don’t talk to me about charging my equipment on layovers either, most of the time I’m running through airports – the very last thing I have time to do is sit and have a latte while my headohones recharge. And you can’t charge it while you use it, so you’re stuck pulling it out of your ears, charging it up for 15 minutes so you get another three hours. If you manage to make it through the entire flight only charging it once, it’s because you charged it immediately before the flight. I don’t know about you, but I have better things to do than manage my headphone battery while I’m traveling through foreign lands.
I understand there is a dongle adapter for the phone but that is yet one more thing to manage, and it fully takes up the same port that I need to charge the phone. Of the two my phone’s battery will always trump the headphones, so yet another reason I’ll be without headphones – while I charge my phone. There is apparently some dock that can be purchased that will allow for charging and listening at the same time, but that is yet one more thing to juggle and lose. Further increasing complexity and making it harder on business travelers.
If you want to do a presentation with the HDMI cable from your phone, you cannot have sound at the same time without aforementioned dock and HDMI adapter combo. That’s a lot of pieces to go wrong, get broken, get lost, or otherwise not work with any sort of protective case. This could be fixed by a bigger/more complex dongle, or an external Bluetooth to RCA jack device, but that has not been introduced yet.
I don’t care about the cost personally, or the ever present Apple obsession to reduce cluttered on the device, or the issues with Apple’s desire for DRM. But I do care about reduced convenience and worse travel conditions. This was a big miss, and until they fix it, I do not recommend switching away from the 6 series of iPhones. It’s not courageous – it’s poor user design.
I was recently turned onto the idea of using a ring-stent as a quick solution to the problem of reducing hand-fatigue and making it easier to work while I’m on the road without having a case that has a popup to hold it up.
The ring-stent is a 360 degree mobile ring that has enough tension to stay put in whatever position you leave it in. I’ve found it useful when I’m on the road or when I need to do longer projects and holding the phone just isn’t cutting it anymore.
The sticker is strong enough to hold up the phone as long as you aren’t pulling on it or adding extra weight. It’s also easy enough to pull off and re-position if need be without leaving any residue of any kind. I’m told that you can re-stick it dozens of times.
In the picture above you can see there are different versions – like the Rok Mobile branded one on the left or the Amazon off-brand Cell Phone Stent which comes with a holder.
It’s also great for flights where you can prop your phone up on a tray and watch a movie without having to jerry-rig something. Very clever design.
I was recently turned onto a different type of cable for a different type of application. Yesterday I talked about the Kenu 2 in 1 and it’s virtues, but one thing it gives up in being lightweight is rigidity. That brings us to the Fuse Chicken BOBINE.
The BOBINE is basically a flexible semi-rigid USB to lightning cable that allows you to work on your phone in a semi-upright position. For the most part I don’t think there’s a lot of value in this, except when you’re traveling.
Just as a test, I laid down on the ground and used the BOBINE to semi-connect it to my backpack. I’ve had to use my backpack as a back/headrest in airports on extremely long layovers when there is no open Admiral’s club in sight. I’m not proud of it, but sometimes a business traveler has to do what they have to do – even in a suit. And sometimes that’s laying on the ground with food poisoning and yes, that’s happened to me.
The nice part about the BOBINE is that you don’t have to use your arms to keep it in place and in view while you’re in strange positions – like on your back feeling like you stomach is on strike from the rest of your body. When you have your hands free you can use a bluetooth keyboard easier and get more work done, or you can simply watch videos and try to distract yourself from that feeling in your stomach.
Anyway, I think there are far less uses for this than other cable management systems because it requires me to remove my case to fit properly, but still an interesting one to have with you on International flights where you might end up having to deal with some extremely odd layovers. A little comfort can go a long ways.
And in case you were wondering, it was the oysters that did me in. Of course it was, I can hear you saying.
One of the problems I’ve regularly run into as a Smartphone Exec is that I regularly have the wrong cable for the occasion. I either have a microUSB cable or a lightning cable, but often the wrong one at the most inopportune times. On a flight I ran across an advertisement for Kenu Tripline (pronounced “Canoe”) that offers a pleasantly simple solution.
The nice part about it is that it has both cables in one. If I happen to need one to charge my headphones, I have that, if I need the other to charge my phone, I have that. All in a lightweight package. I also happen to like that they have 3′ and 6′ options. Often times I make the mistake of thinking shorter is better, but keep in mind how often you are using shared plugs in conference rooms and having an extra foot or two of distance is a life-saver.
That’s even more critical when you’re using your mobile phone during a presentation. Often times the plugs are on the floor and 3′ is barely long enough at the best of times. 6′ is just much more comfortable and I find it’s worth the added ounces. And it’s still less weight than two cables that get caught up with one another and misplaced. Reduce and simplify. That’s the mantra, right?
Multi Tenancy is a weird concept on mobile computing. Having two distinct users utilizing the same hardware is commonplace on the desktop. Yet on phones we somehow ignore this very useful attribute of modern operating system design.
Let me give you some examples of how it’s useful. First of all imagine a parent handing their child her cell phone and allowing them to play games without risking something bad happening to the data on the device. Second imagine handing your phone to somebody at a bar to allow them to watch a video but also not expose your device to anything malicious. Lastly imagine doing a presentation and not having other non-related apps interfering with that presentation on your phone.
With these examples in mind it’s easy to see why the virtues of multi tenancy would be useful on a mobile operating system. Thankfully while this does not exist exactly as described there is a feature on the iPhone that does solve some of these issues. This feature is called “guided access.”
Using Guided Access a user of the device can limit a third-party from accessing other apps or from Interacting with a part of the app by blocking certain parts of the screen. A six digit pin of your choosing protects users from escaping Guided Access.
It’s a very useful feature that virtually no one uses from what I can tell. But one can see how this could be a nice partial replacement for true multi tenancy. You still can’t have two users on the same device with separate contacts (as an example) or different email accounts that are separate from one another , and so on, but it’s still a very useful feature.
Hat tip to my friend Taylor for alerting me to the feature’s existence.
When it comes to security of the apps you use and the device you chose, I think it’s best to consider the Mud Puddle problem. That may not be a term you’ve heard but it’s very important to understanding how threat actors think about your device.
For instance, let’s say you drop your phone in a puddle of mud and it ceases working. You try everything you can to clean it up but it stops working. If you can take it to some store and some genius can recover your data off of the device, it has failed the mud puddle problem.
The basic concept is this. If there is a way that a stranger can take your device and resurrect the data out of it, it means an adversary can do it as well. That is why it is always best to ask vendors how your data is secured. Can they recover your information after you’ve deleted it? Can they recover it after your account has been erased? Can they recover it if your device has been crushed in an anvil? If the answer is yes, then probably many people have access to your data whether you or they realize that or not.
It’s something to consider as you consider which products and services to use.
Multi-tasking on a phone is a very different thing than multi-tasking on a desktop environment. There are some things that are similar and work well. Then there are also quite a few things that need a lot of work or just are currently not possible for a variety of reasons.
Let’s start with the good. You can do things like listen to music while you work. You can take a phone call while you work. You can run several apps at the same time, cutting and pasting between them or having them launch one another. You can download things in the background – like email for instance. Your system can be monitoring dozens of chat clients running with virtually no processing power and still push you a message as it arrives, and on and on.
The bad news is that you can’t do things like you might on a traditional computer – even when running on a full sized monitor through an HDMI dongle. For instance you can’t watch a movie and write an email. Quite often I used to watch a presentation in one window that lasted an hour and work in another, looking over only when I needed to see what the presentation was saying – that’s just not possible on the phone. You can’t have two apps open at the same time for transcribing purposes or for productivity reasons.
The issue comes down to a combination of problems. Its a mix of screen real-estate, the lack of a mouse and app handles to switch between apps to give focus to the active window, and the memory requirements.
What that means is that if you need to do that you end up doing context switching far far too often between apps. On the iPhone (as an example) this means taking the hands off the keyboard and double clicking the home button to switch contexts between windows. That’s a very slow and annoying context switching operation. Unlike the alt-tabs keyboard shortcuts of the world which context switch and are very fast, you’re really stuck doing a slow operation.
So there is a long ways to go to consider it an equivalent operating environment. But it is coming along. Not that many years ago, the iPhone couldn’t even run two apps concurrently. So we’ve come far enough that it’s a useful business tool. I still think Continuum is going to ultimately be the path forward for mobile operating systems though as a result – the phone should be context aware of switching into desktop mode. Memory issues may prevent it, but the screen real-estate and access to a mouse and keyboard are foregone conclusions in the business world. So it’s just a matter of giving the phone a little more memory, making context switching seamless and allowing Bluetooth mouse access. We’re so close I can taste it!
I’ve spent a lot of time with various types of mobile apps over the years and compiled a list of things to think about when developing a mobile app for business use. If this saves anyone a headache while using your app, that’s a big win. If you want to make your business customers happy, this is the hit-list I’ve come up with:
Make it work functionally. So many apps have drop downs or buttons that don’t do anything at all. It’s mind boggling how these apps make it through the QA process. But if something looks like a button and doesn’t work like one, you’ve created a usability nightmare.
Make it easy to use. A lot of apps have rich functionality buried underneath a complicated/convoluted multi-tier navigational structure, making it difficult to find the options necessary to interact with it in the way the user wants to. There’s been a lot of studies that the more you make someone click the less likely they are to find and click that option. So keep the interface clean, simple to use and easy to navigate. Don’t forget to pay attention to your workflows.
Make it stable. I regularly run into unstable apps that crash when you do something like navigate away and then navigate back. That’s a terrible user experience. Your apps should be memory efficient, fault tolerant and if they do crash they should do so in the most graceful way possible.
Make it save work if appropriate to do so. Some apps are safer to use because they save work as you go. Crashes are quite common on mobile, so this is a very useful feature if it’s appropriate to do so.
Make it work with an external keyboard. Things like tab and shift-tab should work as expected – getting you from one form field to the next. If you have to take your hand off they keyboard to use your application you should probably re-think it, unless it is core to the app’s functionality (like a drawing program or something). Business users intuitively feel like touching the phone and interacting with it directly slows them down. Lack of a mouse really hurts app developers, but that’s a separate issue.
Make it work equally well in landscape and portrait. So few apps do this well or even at all. Not even the settings app on iOS does this. Having to switch between the two just to use your app is annoying to say the least. You’re not a special snowflake and there’s almost never a reason to force the user into one mode over the other. Some apps like games need it to be in a certain orientation, fine, and no, I’m not talking about those. But your feature had better be worth it if you’re going to force the user to change the orientation of the device. Don’t play favorites though – just because you envision someone using the device in portrait mode, doesn’t mean that’s how they want to be using it. That’s especially true if they are using an external monitor.
Give your app the same functionality as the browser version of your website. This should be straight forward, but almost no apps get this right. They often have no signup system, no payment system or a bunch of missing features. Why bother building an app if you aren’t allowing your customers to give you money? The worst is when websites force you to download an app and then don’t have the feature on the app. Are you trying to drive the customer away?
Give an option to remove your ads, even if that means payment. It’s the most requested feature of most apps that have ads. Go ahead and do them a favor. Ads are not just annoying, they’re also a huge user of data, and mobile data plans aren’t cheap.
Allow selectable muting and selectable alerts. A lot of the alerts that you think are important a user will disagree with you on. Meanwhile a lot of the things you couldn’t care less about a user will kill for. Making your alerts as selectable and customizable as possible is very helpful. As an example, making alerts specific to certain senders in emails would be very useful because some people have very important things to say, and many people have way too much email to get alerts about every inbound email. Selectable alerts is a winner.
Keep push notifications to emergencies or important notifications only. Basically my rule of thumb when it comes to alerts is silence all of them unless they are warning of something involving a combination of the three I’s: impending, important and irreversible. If your alert is telling me about something I don’t care about you’ve made me that much closer to uninstalling your app or muting it permanently. Don’t waste the user’s time.
Give the option to disable access to the location when not in use. Not only is accessing my location a battery hog, and a data hog it’s also just plain creepy. Ask for only the permissions you need. This should be obvious, but most of the time it appears it’s not. If you really want to be nice to your user only ask for it when you need it, rather than upfront. That way they can selectively disable it and re-enable it. Not many people are this paranoid, but when they are, this little detail can go a long way.
Use SSL/TLS for everything possible. A lot of apps not only don’t use HTTPS but they don’t even tell the user that they aren’t. So there’s no way for them to even notice that something nefarious could be happening and is possible, unlike a web application with a browser where the protocol (http or https) is in the URI field.
Create layered authentication if the app’s access includes sensitive information. For example banking apps shouldn’t allow users to check details without authenticating each time. The rule of thumb here is that theft of an unlocked phone should not mean complete loss of whatever data the app has access to if you build your app well. This really only applies to sensitive data, but it’s amazing how many apps have sensitive data these days.
If you’ve discontinued the app in favor of another one, alert the user to that fact. I’ve run into a number of situations where the app appears to no longer work, but what really happened is that they stopped supporting that version and created a new version. Without telling the user, you’re really creating a terrible user experience.
These rules of thumb are primarily related to business apps but I can see situations where many of these issues could be useful for any sort of mobile application. Let me know if you think I’ve missed anything.