Outlook for iPad

Last month Microsoft released Outlook for iPad (based on Acompli, an app it has previously purchased). Since the company I work for uses Exchange 2013, I was able to take advantage of this and try it out. The interface is a breath of fresh air for anyone, like me who is stuck using Outlook 2013’s confusing and dated interface. My favourite feature is the ‘Focused’ inbox with automatically shows you a view of messages deemed important. Newsletters, alerts and other noise are quietly hidden away so you only get to see emails from real people. The ‘other’ inbox is only a swipe away, and the focused view is only that, a view; so it won’t have any effect on your desktop email view. This is surprisingly accurate and didn’t require much training. Replying and managing email is pleasant, with the ability to swipe to archive or flag email quickly.

Outside of the corporate word, the app supports Outlook.com, Gmail and other well-known email providers. I like to keep work and personal email separate, so I haven’t tried these.

 

Attachments

Another surprising feature of Outlook for iPad is the ability to connect to cloud services such as Dropbox and Google Drive 1. A lot of network administrators will loose sleep over this, but ultimately it’s a step forward – especially for users of Office 365 who will be able to access all of their ‘OneDrive for Business’ files and attach them to emails wherever they happen to be.

A week point however is the lack of a system extension, so it’s not possible to share a link from Safari to Outlook, or send and document directly from Word for iPad. I’m sure this is on the way, but I do think it should have been included in the initial version.

 

Calendar

The calendar seems quite basic. It doesn’t seem to do a great job of letting me see other invitees ‘free/busy’ information (the main benefit of using the desktop version of Outlook), but it’s serviceable for a version 1.0 release. It’s quite buggy, for example, I tried to update an appointment start and end date, but it just didn’t work. No crash, no error message, it just didn’t do anything. I’m sure Microsoft’s latest purchase, Sunrise indicates Microsoft is putting some thought into its calendaring strategy, and so major improvements should be on the way. I’m not sure about the unified app approach – I’ve always wished Outlook on the PC were separate applications instead of one big conglomerate (especially since it’s still full of model dialog boxes! I digress…) – separate apps seems especially fitting for iOS, and I can only think it’s a branding decision to go with one big ‘Outlook’ app on iOS.

 

Security Concerns?

The first release had no security requirements at all, so if your system administrator had mandated users have a passcode on their device, Outlook would ignore it. This has been resolved, though unfortunately it requires you set a PIN at a system level on the device, rather than just for the app (as had been the case with the pervious OWA app). I liked the fact I could have more lax security on my personal device (e.g. ‘Ask me for a PIN after 1 hour’) while the app could be much more strict (‘ask me for a pin after 5 minutes’) – this worked in the old OWA app, but not anymore; which is a major disappointment. Some system administrators might lament the fact the then app will store your emails on Amazon’s AWS servers (soon to be Azure, I have to believe), but it does allow the app to do lots of cloud processing that ultimately benefits users. The fact that Microsoft just released the app without any warning and a way to block the app is probably the bigger concern in my views, as I can understand organisations who have various security practises (ISO et al) not being very happy about being caught off-guard like this.

 

Conclusion

Overall, Outlook for iPad solidifies the iPad as a tool for business and makes me think that one day, many users will be able to use an iPad (or similar device) exclusively at work.

It’s missing some key features at the moment (you can’t set your ‘Out of Office’), but I’m certain they will come in time. The bigger question is whether tablet-devices will ever replace traditional PCs in the workplace. This is probably the subject of a future blog post, but with Outlook, Office and the cloud it’s becoming an increasing possibility. I personally use Outlook for iPad as more of a sidekick device than a laptop replacement, but then my job does involve using a lot of traditional desktop software such as Visual Studio, or macro-enabled spreadsheets. That said, for many enterprise users, an iPad with a decent hardware keyboard is now a viable alternative, if not for the small screen size.

 

 

 

1. Great to see Microsoft embracing interoperability, in contrast to Google, who refuse to support Windows Phone.

Apple Upgrade Regret

As someone who owns an iPhone, Mac, iPad and an Apple TV, I can safely say I’m deeply embedded into the Apple ecosystem. I got my first Mac, a white iMac n 2001 at the dawn of the OS X revolution and loved it. I had switch back to a Windows PC for university as back then a lot of the software development tools I needed were PC-only or required I keep upgrading my OS on the iMac to install them (the poor G3 processor struggled from the offset with OS X).

I came back into the Apple ecosystem with an iPhone in 2009, and later an iPod Touch (now retired), iPad and more recently and Apple TV. They all work well together, and the hardware design and quality is second to none.

So I was excited when Apple announced as WWDC that iOS 8 and Mac OS X 10.10 Yosemite would further deepen that integration. About a month ago I finally upgraded my phone (a trusty 2-year old iPhone 5) and iPad to iOS 8., and two weeks later my MacBook Air to Yosemite. My Apple TV also got upgraded (after weeks of nagging me) to iOS version 7.0.2 (oddly it seems to be on a different versioning system).

In short, I have regrets.

Yosemite on the desktop is the polar opposite of 10.9 Mavericks. While Mavericks was all about optimisation, whether it was battery life or memory consumption, Yosemite is a lavish excursion into a world of translucency and bright colours and unfortunately, some bugs.

Take for example listening to music over headphones. No longer possible if you have an Apple TV on the same network. You either need to unplug the Apple TV, or turn off Wi-Fi. Animations are choppy, and the new looks resembles the much derided Windows Vista. There are a few useful new features; Safari now feels much more streamlined and being able to send and receive SMS messages from the Mac is brilliant. I’d rather have a fast, bug free system running Mavericks and sacrifice these small but useful features, however.

On the Apple TV side things are even worse. It used to be that from a Mac or iOS device you could start beaming audio or visual content while the Apple TV was in deep sleep mode (“off”). This no longer works. Now I need to hunt around for the infrared remote and switch on the Apple TV first. This also rules out using the iPhone Remote app, as it uses the same mechanism and cannot wake the Apple TV. Often I try and beam a video to the Apple TV an get sound coming out of the TV but no audio. Frustrated, I reboot my iPhone or Mac and it still happens. In the end I learnt that I actually need to reboot the Apple TV to get my videos to play.

Nothing major on its own, and yes the very definition of a 1st world problem – my frustration is that this stuff used to work so brilliantly, and now it doesn’t.

On the iOS 8 side things have been surprisingly non-eventful. After the upgrade that was iOS 7 it might just be it seems that way in comparison,  but it seems to work pretty well. I love being able to use LastPass in Safari. Occasionally I find Safari will show me a white page, only to show the content when I try and scroll. No big issues though.

Writing bug free software isn’t easy, I know that all too well, so I don’t feel like its fair to call out Apple as being any different to say, Microsoft (one word: Excel). However Apple could make the lives of its users easier by letting them downgrade! There’s nothing wrong with trying something, deciding it’s not for you right now, and going back. Software should be running on a device because the user wants it, not because they have no way of removing it.