November 25th, 2003 • 7:44 am
I was going to give good marks to Adobe for having provided a fairly easy to install package of software titles with its “Adobe Creative Suite”. But then the installer recommended that I quit all applications first before installing the software. I can understand having to quit existing Adobe applications if they are running, but all running applications? Might as well log out and log back in holding the Shift key down (which is what I did, in fact).
You’d think that by now, Adobe would have jumped on the Mac OS X bandwagon and embraced a simpler approach for application installation. These are just regular applications, for crying out loud. They are not system-modifying utilities! I guess user-friendliness is just too much to ask.
The installation went fairly smoothly after that, even though it was quite long with little indication of progress at times. Then I quit the installer and set about resuming work. Of course, I had to log out and log back in again in order to launch all the applications that I normally have running while I am working.
Then I decided to apply the recently released Acrobat 6.0.1 update before actually trying to use the product. (Based on the many complaints with the products, I thought that was the sensible thing to do.)
The download is a disk image (.dmg) that expands into a volume entitled “AcrobatProPackage_all”. Not exactly a user-friendly name either, but what can you do? Then when you would expect a double-clickable application right inside that mounted volume, all you get is… a folder called “AcrobatProPatch Package”. Mmm. So now the update is a “patch”. OK, fine… Inside that folder, you’ll find… a single item that bears the name ‘”AcrobatProPatch Package” and has a generic Mac OS X application icon. They didn’t even bother to use their own icon for the update/patch/package/whatever!
I don’t know about you, but it seems to me that things are getting worse rather than better when it comes to user-friendly at Adobe.
You double-click on that generic-looking application and what do you get? This:
As far as I remember, previous versions of Adobe software updates used to be able to locate the software to update themselves and not require that extra step. Again, a great sign of progress on Adobe’s part.
In fact, the updater does appear to be able to locate the software to update, since it automatically switches to that particular folder containing Acrobat 6.0. So why doesn’t it go all the way, select the item, and apply the update without user intervention? Beats me.
If this continues, we are going to end up having a parallel industry of “Adobe Annoyances” experts. When it comes to user-friendliness, except for a few bright spots, most of them on the Mac platform, it seems to be that the industry as a whole is regressing. Adobe seems to be confirming that trend.