James Dempsey on Life Without WWDC

One key was thinking about what WWDC provides and figure out how to meet those needs in some other way. For me, that boiled down to:

  • Sessions
  • Labs
  • Social Events / Networking

Here’s a handy reference about the many substitutes available to WWDC. As James notes though, the Design and App Store Labs are irreplaceable, which really is a shame. Hopefully Apple can find a way to fill in this specific gap in the future.

How to Export Campfire Chats

If you’re looking for a quick way to backup your Campfire chats, I can highly recommend James Taylor’s Campfire Archiver. While savvy apps is now on Slack full-time, ensuring we had a backup of Campfire was a long-standing item on our to-do list. It just never got attention.

For a bonus—and possibly for those not yet abandoning Campfire—check out this script from Ron Alleva that removes files from Campfire. We’d often have to hunt down large files that would take up our allotted space and this script would have been handy. To keep our export slimmer, I actually ran the remove script against all of our rooms and then did the archive.

How to Choose a Revenue Model for Your App

Dan Counsell recently published a great post entitled “Paid, Paymium or Freemium,” in which I also happen to be quoted. It reiterates what I’ve been harping on for the last couple of years, which is that paid apps aren’t dead. More generally, it should help independent developers understand the pros and cons of the revenue models available to them on the App Store.

I’m especially glad that Dan correctly labeled them as “revenue models” because it’s a pet peeve of mine when they’re improperly called “business models.” I also agree with him that paymium continues to show promise, especially for yearly upgrades.

The First App You Open

You wake up. You grab your phone. What’s the first app you open?

This sounds like a silly question — or worse, an insulting one.1 But I find it’s a rather enlightening question. Depending on when the question is asked, the answer can either be telling about the current state of apps or the current state of you.

A seemingly simple question but exceptionally thought-provoking.

Working with Multiple iPhoto Libraries

When I threw my father a surprise 50th birthday party a number of years ago, we had to scour our family to find decent pictures of his childhood, teenage, and early adult years. In the age of cheap storage and phones that double as many people’s only camera, today we have the opposite challenge of past generations: we have way too many photos.

My wife’s MacBook Air is a testament to that. Her iPhoto Library has grown to over 125 GB, causing her machine to be resource-constrained while iPhoto is open. Between the birth of our son at the start of 2012 and the advancements of the iPhone, she went from snapping around 1,000 or so photos back in all of 2010 to nearly 7,000 just through October 2013 alone.

While a second stage will be to move significantly older photos off of her hard drive, step one was to make iPhoto more manageable by reducing the overall size of her iPhoto Library. My approach was to group photos by year into multiple iPhoto libraries. Beyond speeding up iPhoto usage, this felt like a nice way to browse photos and just as importantly ensure there was no longer a single point of failure by having a single, massive iPhoto Library.

iPhoto does natively support the ability to have multiple iPhoto libraries but as usual, the simple solution is not as simple as it sounds. The main issue is that the easiest way to get photos from one library to another will cause the important metadata associated with the photos to not be maintained. That’s where Fat Cat Software’s iPhoto Library Manager comes into play. While iPhoto Library Manager does much more, what I mainly used it for was to copy photos from the default iPhoto Library into ones associated with each year.

The best part about this app, is that it actually uses iPhoto itself to do the work. After you create the library and choose the photos (and videos) to copy, iPhoto will systematically open and close in the background. Unlike the “easy way” of moving photos mentioned above, iPhoto Library Manager automagically employs the importing functions multiple times to maintain event info and other metadata of the photos. Doing this manually would take a considerable amount of time and could also introduce copying errors.

iPhoto Library Manager also has a nifty find duplicate photo feature—even across libraries—that I’m sure will be helpful at some point. And if I ever want to eliminate certain libraries, there’s also a merge function. For now, problem solved…no more fans kicking off when iPhoto is open. iPhoto Library Manager is well worth the $29.95 price tag.