iPass Connect on the Mac; great service, appallingly designed app

I find myself travelling a lot for work these days and that means a roaming service for wifi hotspots and hotel internet connections really makes life simpler. I could maintain subscriptions to The Cloud, T-Mobile Hotspots, BT OpenZone and so on and so on, but fortunately Yahoo! provides me with an iPass subscription.

iPass is great; it allows me to connect to pretty much every hotspot and hotel internet service there is. I’ve been using it for over 4 years now and can only think of a single time when I haven’t been able to get a connection. I’m using it right now, sitting in the departures lounge at Berlin’s Tegel airport waiting for my flight back to London.

So far, so great, but the current, Snow Leopard supporting, version of the iPassConnect app, v3.1, seems to have been designed by someone with scant regard for anything approaching consistency and usability. Let me count the ways in which this app frustrates.

1. Quit iPassConnect? I see no Quit menu option.

From the Mac OS X GUI you can’t stop iPass running. The app lives in your menu bar and scans and rescans for wireless networks (which I’m sure reduces battery life) even when it’s connected to a wireless network. If I’m connected to a wireless network why would I want to look for another network, all the time, constantly? There’s a red and white animation going on in the menu bar which I’m sure someone thought was cute but which is incredibly distracting. But let’s overlook that for a moment. To quit an app, you simply select the menu bar and select Quit or press Cmd-Q.

Not that I’ve ever been able to find the mythical Quit command for iPassConnect. The only way to kill the damn thing is from within Activity Monitor or by the killall command from the shell within Terminal.

Simple resolution: Let the user choose when they want to run your app and when they don’t. Add a Quit command.

2. Install as a Login Item? Every single time?

It’s a simple, plain fact that the more apps you have in your account’s Login Items, the slower your login time will be. Like most people, I keep the number of Login Items down to a bare minimum and then start apps up as I need them. If I don’t use something all day, every day, it’s very unlikely that I want to make it a Login Item. Most apps are well behaved and ask your permission before inserting themselves as a Login Item but not iPassConnect. Run the app and hey presto you get a Login Item. Mildly annoying but at least you can remove it from your list of Login Items. Run the app again though and hey presto you get a Login Item. Each and every single time. It’s frustrating the first time it happens and induces psychosis after the hundredth such occurrence.

This is uncontrollable, un-configurable, totally unacceptable and verging on downright insulting. It’s an app designer’s way of saying to the user “I don’t care what your preferences are, I know better than you”.

Simple resolution: Act in a well behaved manner, ask the user for their preference, act on it and remember it.

3. Update? What update?

Most apps these days have a way of calling home and checking for an update. For those apps that run within a window there’s usually an Updates option in the application’s menu. For those apps that don’t run in a window there’s usually an option in their preferences pane. Note the word usually and let’s have a look at the iPassConnect preference pane.

There’s an Updates tab which is a good start. There’s an Enable automatic updates option which is also a good thing. But it only controls the hotspot dictionary that the app maintains. Want to update the app or know whether there’s an update available? Not with this app (and the iPass website is remarkably update free as well).

Simple resolution: Add an update option and ask the user if they want to check for updates.

4. Snow Leopard support. In 32-bits.

Snow Leopard continues Apple’s march towards a pure 64-bit operating system. A cursory glance at Activity Monitor shows that most apps running are Intel (64-bit) and this includes the System Preferences app. So let’s try to set some preferences for iPassConnect.

Ah yes, the iPassConnect preferences pane is 32-bit which means that you have to restart System Preferences in 32-bit mode and there it stays, running in 32-bit mode, until you manually restart System Preferences in the default 64-bit mode.

Simple resolution: If you say your app has Snow Leopard support then fully support Snow Leopard. That means 64-bitness across the board.

iPass is a great service, it deserves a great app; version 3.1 is not that app.

Written by

A self-professed map addict, Gary has worked in the mapping and location space for over 20 years through a combination of luck and occasional good judgement. Gary is co-founder of Malstow Geospatial, which provides handmade, professional geospatial consulting. A Fellow of the RGS, he tweets about maps, writes about them and even makes them.

Published 27 Feb 2014

Administrivia

Tom D'Arezzo said ...

Hi Gary -
I'm the product manager for the iPass Connect client for Mac. I wanted to thank you for the feedback and let you know that your post has been read with keen interest on our side. I agree with many of your comments; we need to create a more Mac-like experience for our users.
We do have plans to address many of your points in a future release that will likely not attempt to maintain compatibility with 32 bit versions of Mac OS X.
I'd like to contact you as an early beta user when we have the new version ready later this year. Would you be game?
Regards,
Tom

Gary said ...

Hi Tom,
Thanks for the comments and for the offer. I'd be only too happy to be a beta tester; just let me know how and when and I'll be there. My email address and other contact details are over at http://www.garygale.com/#contacthead ...
Thanks for getting in touch; I'm looking forward to seeing what iPass comes up with.