Uninstallers – Three for your consideration

I’ve never been great at reviewing software. I could argue that it’s because I’m highly focused and just use the features I need. Alternatively I could just admit that I lack the mental discipline to methodically check every feature to see how it stacks up. In any case, I made a bit more of an effort when it came to looking at uninstallers, primarily because I like trying out software on the Mac and with a good 75-80% of things I try getting trashed for whatever reason, I needed something that would do a thorough job.

AppZapper

AppZapper

So I plumped for three candidates. AppZapper was one of the first applications I bought for the Mac and has been a long time favourite. However, CleanApp caught my eye one day as being a bit more feature rich and I decided to give it a go with interesting results. Finally I thought I’d add AppCleaner to the mix, mainly because it’s a free alternative to the other two.

All three go about letting you choose apps to uninstall in a similar way. Either you drop your victim on to the application’s “pad” or you choose it from a list of apps the uninstaller knows about. This is where the first differences appear in that when you launch CleanApp it quickly builds a list of apps and presents it to you by default, while the other two open in ‘drag n drop’ mode and need to be asked to show a list of known apps. What is also interesting is that on my system, both CleanApp and AppCleaner built their lists in seconds, while hitting the ‘Genie’ button in AppZapper resulted in some furious disk activity for around ten minutes before I was shown the results. Now as you’d expect, each program gave a different figure for the total number of apps it thought I had installed, and this may be (in part) down to how each categorizes what it finds, but the program giving me the highest total of removeable items was CleanApp (269), then AppCleaner (236) and finally AppZapper (231).

Now I briefly mentioned categories and by that I mean the types of things you can install on your Mac. Obviously there’s the traditional apps that go in your

AppCleaner

AppCleaner

Applications folder (or wherever you choose), but there’s also Preference Panes, Screensavers, Plug-ins, Widgets, etc., and each uninstaller will let you get at these to varying degrees. AppCleaner shows me everything in the Applications folder (including subfolders like Utilities) under the heading of Applications. It also has a separate button for Widgets and finally a button labelled Other for everything else which listed plug-ins, contextual menu items and the like. CleanApp on the other hand considers everything as either an Application or a Preference Pane. In the case of applications it’s anything with the extension .app wherever it happens to reside on your system (although you can chose to exclude folders from the search). Under Preference Panes, CleanApp listed 3rd party preference panes as well as 3rd party widgets, 3rd party screensavers and 3rd party plug-ins like the Evernote web clipper, Flip4Mac etc. The fact that only 3rd party items are listed here is interesting because you’d think it means that standard Apple items are safe, however I found that Apple applications like iTunes, iPhoto and even Disk Utility are also listed as uninstallable applications by CleanApp. Whether or not that’s a good thing I’m not sure, but both AppZapper and AppCleaner offer some sanity checking by not displaying standard Apple applications by default (although you can change that setting in AppZapper), plus they both let you specify other (3rd party) applications to protect via their preferences settings.

CleanApp

CleanApp

Now it’s about time we got down to the main purpose of these three programs and that’s removing unwanted apps and extras from your system. My first test was to uninstall Thunderbird which I’d been trying out for a week. Both AppZapper and AppCleaner said they would delete two files – however CleanApp found a third Library file relating to Thunderbird that the other two didn’t spot. Ok, how about a bigger program like Aperture? CleanApp announced it had found 18 files and 3 folders that needed removing. AppCleaner found 6 files and 2 folders, while AppZapper flagged 6 files and 1 folder for removal. You’d think that for sheer thouroughness, CleanApp is the clear winner here. However, examining the list of items to delete revealed some very interesting results. I use Aperture in conjunction with iPhoto, so even though Aperture has it’s own separate library for storing photos, I can directly access my iPhoto library from within Aperture. What this means is that CleanApp listed my iPhoto library (all 14.1Gb of it!) as one of the files it could remove when uninstalling Aperture, which would of course have been disastrous! This happens because of a feature of CleanApp which is a background process tht watches how applications work – i.e. what files they interact with. So it correctly spotted that Aperture was indeed accessing my iPhoto library and thus offered it up as a candidate for removal. This is where a utility like CleanApp needs caution because in the right hands it’ll seek out the stuff that the other two miss, but in the wrong hands it can and will take away files you’d really rather keep and that may even be necessary for your system to run properly so care is needed.

What would be nice is if CleanApp had a ‘Protect this application’ feature (like the other two do). That way I could tell CleanApp that I want to protect iPhoto, then if I go to uninstall Aperture, CleanApp would alert me to the fact that certain files used by Aperture are also used by iPhoto to help prevent me from mistakenly removing files that iPhoto needs. Sure you can un-check what files to delete once CleanApp has done its assessment, but often files can have obscure names you might not spot as needed by other apps and a helping hand to prevent human error wouldn’t go amiss. CleanApp does go some way to mitigate the problem by offering an Archive facility, so rather than deleting files (which can be done via the Trash to offer a small degree of protection) for apps you want to uninstall, it can archive them to a bespoke CleanApp archive file (with the .caa extension). The selected files are then taken out of service so to speak, but can then be reinstated later via the Archive function. It’s not ideal because it still leaves you to find out the hard way if you’ve removed something needed by another app, but it is better than nothing. I tried this out by going to uninstall Plex (which doesn’t share files from any other application from what I can tell) and then using the Archive option rather than the delete option. A day later and after powering off my Mac over night for good measure, I fired up CleanApp and recovered Plex from its Archive (CleanApp recovers the files to their original locations). I then launched Plex and while I didn’t test every single aspect of the program, what features I did try worked just fine.

A trio of uninstallers

A trio of uninstallers

There are other differences too. I installed six 3rd party screensavers and then had a look to see what my uninstallers made of them. CleanApp only found two of them, because by default it only looked in my Users/<username>/Library/Screen Savers/ folder, whereas four of the screensavers just happened to have installed themselves into the system /Library/Screen Savers/ folder where any user could use them. Yes you can change this behaviour in the CleanApp preferences by adding the relevant paths to search under the Paths tab, but it again emphasizes the fact that you need a bit of knowledge to get the best out of this utility. Both AppZapper and CleanApp found all six by default, and that’s pretty much the theme for uninstalling things using these three tools – AppZapper and AppCleaner will do a lot by default while CleanApp gives you more power but you need to exercise more control.

The final thing is logging or history, and all three will keep a history of what you’ve removed whether you access the logs via a menu item or directly within the application itself. Unfortunately neither AppZapper nor AppCleaner offers an undo facility, although CleanApp does provide this by way of its Archive facility as I mentioned earlier. There’s another app out there that will ‘archive’ applications for you and let you reinstate them later on, although the name of it escapes me at the moment.

As far as features go, that’s about where it ends for AppZapper and AppCleaner, but CleanApp offers a few more things, namely – Old Files, Archives, Languages and Cache Files. Old Files will list files under your home folder (Users/<username>/) that haven’t been accessed for over a month and is a handy way to see what junk you may have forgotten about that you can then delete directly from the list. The list is helpful in that it tells you where the file is, when you last accessed it and how much space it’s taking up.

As I mentioned above, Archives lets you reinstate uninstalled apps that you chose to archive rather than delete. You can also permanently delete archive files from here if you’re sure you no longer want the app and your system is running fine, or you can burn the archives to CD/DVD from within CleanApp itself. I’m not sure if there’s an option to re-import CleanApp archives into the program, but if there is then it’s escaped me for now. Languages looks like it lets you search for language localization files, e.g. for languages you’ll never use so that you can delete them and recover space, but it’s not something I’ve needed to do. Finally the CacheFiles feature lists everything in your Users/<username>/Library/Caches folder giving you a handy way to look for cache files to clear out, for example from apps you uninstalled before you had CleanApp.

There you have it, my potted view of three application uninstallers. So the first question is – are they really necessary? Well that all depends on your point of view and how you use your Mac. If like me you are constantly experimenting with new bits of software, then these are a great way to keep your Mac free of junk files that would otherwise take up space and potentially slow your Mac down. If however you are like some people I know who have only ever installed iWork or Microsoft Office (oh and of course World of Goo!) since getting their Mac, then I guess you probably don’t have the need. That then leads me on to – which one is best?

Well if you’re reasonably non-technical and want to just keep things a little tidier then there’s not much to separate AppZapper and AppCleaner other than the price. AppCleaner is free and will do a reasonably good job so I guess that edges it over AppZapper, but then there’s nothing like the “ZAP!” sound-effect you get when you use AppZapper to purge that useless app with attitude. However for the power user I’d say CleanApp wins for it’s range of features and more ‘thorough’ cleaning, although as I’ve mentioned it can be a double-edged sword and you really need to exercise some caution when using it. Also, I have seen mention of some users complaining that the background scanning process in AppCleaner can slow your Mac down and/or prevent it from sleeping. This isn’t something I’ve noticed, but then it’s only fair to mention it.

Which one shall I keep on my system? Well I’ve paid for both CleanApp and AppZapper so I’ll keep both for now and will compare results when I next come to uninstall apps over the coming months. If it wasn’t for AppZapper there would be a space for AppCleaner on my system too, but if you’re after a free and capable uninstaller then AppCleaner is vastly superior to just dragging your app to the Trash bin. The other thing is that these aren’t the only Mac uninstallers out there. Hazel springs to mind as a program that not only helps you organize files, but also includes an app uninstall feature. There are more and if you have a favourite then mention it in the comments. It’ll keep us all busy until Apple decides to include an uninstaller in a future version of OS X, and even if that happens (you can’t predict anything with Apple), there will be companies offering alternatives.

Finally I would add that although AppCleaner is a handy little app that’s free to download and use, you can make a donation to the author and if you do decide to keep and use it, then I’m sure he’d love it if you sent a few dollars his way!

Advertisements

iPhoto ’09 – Worth the upgrade?

iLife 09As a long time Windows PC user I had become acustomed to managing my data myself. So photos were all organized chronologically by event, backed up both locally and offline (in Flickr), and I was happy that if anything were to ever go pear-shaped, I could recover the situation. This meant that when I switched to using a Mac in February 2008 I was loathed to go anywhere near iPhoto ’08 which came pre-installed. As far as I could see, iPhoto offered me nothing but a fancy front-end for browsing photos and would wrestle control from me such that if I somehow lost my data to a hard disk crash or some other mishap, that would be it… bye bye photos!

Almost a year on and I must say my position has changed somewhat. Now whenever I connect the camera to my Mac I’m happy to let iPhoto import and organize my pictures, and my only caution is that after importing I copy the photos out to the old folder structure I’ve always used, from where I upload them to Flickr as well as backing them up. It’s fair to say here that I really haven’t explored the editing capabilities of iPhoto ’08, nor have I used it’s other features like web galleries and creating books. I’ve done a bit of red-eye removal and the odd exposure tweak but that’s about it. Maybe iPhoto ’09 would change that?

Happily on January 27th a padded envelope arrived on my doormat and within half an hour the new iLife ’09 suite was installed. On launching iPhoto ’09 the first thing I noticed is that it performed an ‘upgrade’ of my iPhoto library. Presumably this is to support the new features, which suggests that going back to iPhoto ’08 is not an option. iPhoto ’09 looks pretty much like its predecessor, the only obvious difference being two new entries under the Library section, namely Faces and Places. I won’t go in to how you set these up as Apple has it’s own very good video tutorials, plus there are doubtless many other reviews that will go into a lot more detail on this aspect of it. I was more interested in how these features performed and how it might change my use of iPhoto.

Faces is a neat idea, the idea being that you teach it a few faces and off it goes, building up a view of your photos organized by who people are. Well that’s the theory anyway because in practice it has been hit & miss and a lot less hit than miss in my case. I have approaching 7,000 photos most of which are decent shots taken with a reasonable quality compact camera. Having taught iPhoto between 10-20 examples of each person in many cases, I sat back and expected wonderful things… only wonderful things didn’t happen. Having left iPhoto open and ‘running’ for 8 hours on my 2008 Mac Pro I was dismayed to find that iPhoto had only managed to come up with suggestions for a further ten or so examples of about five people, and many of them were wrong. I therefore went through the confirmation process following which I started to go through events and manually identify people in them.

Face? What face?

Face? What face?

In ‘naming’ mode, iPhoto ’09 did a pretty poor job of recognizing faces, spotting a fairly obvious two eyes, nose and a mouth in around only 50%-60% of cases. All too often I would see a box drawn around a car headlamp, a brick wall, a fence post, some foliage, a piece of a table or some other inanimate object that looked nothing like a face, with the words ‘unknown face’ underneath it. Assuming this to mean it needed more training I tagged peoples faces in around another 1,500 photos, but this didn’t seem to improve the accuracy of iPhoto’s face recognition at all. Whenever I go into the Faces feature and chose someone for whom I know there are loads of photos, underneath the line that says ‘So and so may also be in the photos below’, it’s empty… there are no suggestions!

So, my overall impression of the Faces feature is that while it must be cool when it works, for some reason I can’t fathom it doesn’t work well for me and that I’ll have to manually add around 80% of the data by using the ‘Add missing face’ function – which is actually quite time consuming. And so on to Places

Not exactly a globetrotter!

Not exactly a globetrotter!

Now while I have an iPhone 3G that sports a GPS enabled camera, I take very few photos with it, preferring to stick with my non-GPS enabled Canon Powershot A720 IS. In light of that I was prepared for the fact that I’ll have to add the location data manually. Assigning a location to an entire event is beautifully simple, simply hover the mouse over an event, click on the ‘i’ that appears and type in the location. Ok for many of the towns and villages around the UK you don’t get a hit in the picklist, but it’s a simple step to choose ‘New place…’ then let Google Maps do the hard work for you. Having assigned a location to a whole event, you can then select individual photos within each event and be more specific, so having tagged an event as being in Paris for example, you can then tag individual photos as the Eiffel Tower, the Champs Elysees, etc. The more effort you put in to this, the better will be your maps of the world, covered in pushpins to show you where you’ve been. The one thing I would say is that when browsing through all the photos in an event in thumbnail view, there’s no way to tell which photos have been tagged with location data and which ones haven’t. You have to click on the ‘i’ on each photo before iPhoto will reveal the location data, if it’s present. So, you need to be organized and keep track of where you’ve got to when you’re adding location data in thumbnail view. Maybe that’s something they’ll address in iPhoto ’10?

The feature I’m actually looking forward to the most is being able to order up photo albums that show my chosen photos intermingled with routes and maps of where they were taken – a sort of ‘Road Trip’ book. The ideal gift as the Apple marketing men would say.

From iPhoto to Flickr

From iPhoto to Flickr

Finally I wanted to look at the Flickr integration that’s been added to this latest version of iPhoto. Well, when I say integration it’s more just a built in way to upload photos to Flickr and keep track of what you’ve uploaded. The process is fairly intuitive – select some photos and click on the Flickr button. First time through you’re asked to provide your Flickr credentials, then authorize iPhoto to use the Flickr API for your account. Then you specify who is allowed to see the photo using the standard Flickr choices (Only you, Family, Friends, etc.) and choose a size for the upload (web, optimized or actual size). Your photos are then queued and uploaded, with any such photos then being added to a Flickr category in the iPhoto sidebar. Disappointingly you can’t seem specify an existing Flickr set or a new set for photos to be added to, it defaults to creating a new Flickr set with the same name as the iPhoto event you’re uploading from, so this feature seems to be a ‘nice-to-have’ rather than a decent replacement for Flickr’s own Uploader tool, or rather it’s better suited to someone just starting out with Flickr rather than someone who already has a large collection of Flickr photos that are all organized separately.

Flickr sets in iPhoto

Flickr sets in iPhoto

So has the upgrade been worthwhile for me? Well I could argue ‘no’ as far as iPhoto is concerned. The face recognition feature has been a bit of a disappointment, and I’m seeing lots of comments on discussion boards from people who are having a similar experience. If only they could improve the accuracy then it would be a really cool feature, so if you have a large collection of photos you could be in for a lot of hard work if my experiences are anything to go by. The places feature is nice and I can see myself using it a lot, and as for Flickr integration, well I’ll stick with the Flickr Uploader until they make iPhoto a bit more flexible. £69 well spent? Well despite my mixed feelings about how iPhoto has fared, I’m sure there are other improvements I’ve yet to discover, in addition to which all the other products in the suite have also been given new features. So it’s a ‘yes‘ from me. £69 for all this software is a bargain!

Now I’m off to see what wonders the new image stabilization feature in iMovie ’09 can do for my footage of the local air show…

iLife ’09 is on it’s way!

region-capture-3Having watched the demo of iLife ’09 I didn’t need much persuasion to take the plunge and so ordered it back on January 6th. Well, I checked the order status today (25th Jan) and it’s been shipped!

The new features in iPhoto and iMovie look like they’ll be good fun, the idea of being able to make photo albums with route maps etc., in them is quite appealing as something I can give as a gift.

Can’t wait!

Stop iPhoto loading when your iPhone is connected

I have a Canon digital camera and an iPhone 3G, and while the iPhone can take reasonable pictures (that look best when they stay on the iPhone), I tend not to use it much for photography. So every once in a while I connect my camera to my Mac Pro and up pops iPhoto ready to transfer my new images. Great, that’s just the way I want it. However, every day I connect my iPhone to the Mac, usually just to charge it or sync some application or music… up pops iPhoto and I have to wait for it to scan whatever images are on the phone before I can dismiss it, and I have to say it bugs me somewhat.

Automator

Automator

Now if you Google for a solution to this little irritation you’ll find slick scripts that, if you find out what name your Mac recognizes your camera by, can automatically launch (or not launch) iPhoto as required. I went for the easier option which was to create a simple Automator Action to take some of the frustration away. It’s not a complete solution, but it does save you having to wait for iPhoto to do its thing every time you plug in your iPhone.

So, open Automator from your Applications folder and choose to create a Custom workflow. From the Library list choose Utilities then drag the Ask for Confirmation action across to your workflow. Give the action a suitable title, then enter some text for the prompt that will appear – in my case I simply entered “Do you wish to open iPhoto for this device?”. Finally, give the two prompt buttons a description – I labelled the button on the left “No thanks!” and the button on the right “Launch iPhoto”.

The next step is to select the Launch Application action and drag that to your workflow underneath the Ask for Confirmation action. Use the picklist on the Launch Application action to choose iPhoto. That’s it, all you have to do now is to save your actions as an Application, so just choose File – Save As then give it a meaningful name like ‘iPhone_iPhoto’, choose the format ‘Application’ (rather than Workflow) and save it. I have an Automator Actions folder in my Documents folder where I save all my workflows.

The final thing is to attach your new ‘iPhone_iPhoto’ application to the Image Capture utility that detects cameras attached to your Mac.

Image Capture

Image Capture

So, open up your Applications folder and launch the Image Capture utility. Go to the preferences for Image Capture and for the application to be launched when a camera is detected use the picklist to choose your new application.

That’s it. Next time you connect your iPhone you’ll just see a prompt asking if you want to launch iPhoto and you can quickly dismiss it if you don’t want to, saving a few precious seconds to waste on something else!

It’s not the perfect solution, but it takes just a couple of minutes to set up and gives you a really good idea of just how useful Automator Actions can be.

So, do you wanna?

So, do you wanna?