gedblog

To say things have been a little hectic at work lately would be an understatement. For the past several months, we’ve all been working hard to get you-know-what for the iPhone in ship shape. With the impending launch of the App Store, all of us have had our hands full and then some. In the midst of this massive effort, this 4th of July weekend, David and I travel to New York City to give a talk at the ICON5 Illustration Conference at the invitation of our friend and fellow artist, Von Glitschka. I can’t remember the last time I flew on a holiday and I can only imagine the travel nightmares that await us. My iPhone will be good and charged and packed with plenty of episodes of Futurama and Deep Space Nine.

Then there’s the little matter of day-to-day work at the factory. We’ve been snowed under at the office for months with a huge project that has kept us all busy every minute of every day. Having constant work is great, but it also makes it difficult to focus on internal projects like [REDACTED] and certain freeware releases that were only supposed to go on for a month, but due to forces outside our control, inevitably stretched into the future. If we could just get the R&D lab to perfect that cloning machine they’ve been teasing us with, everything would be peachy. However, as of this writing, there’s no word yet. Those bastards.

Somehow in the middle of all this madness, the gang at the Iconfactory managed to pull off an elegant punking of our dear friend and co-worker, Craig Hockenberry. See, back at WWDC Mr. Hockenberry came away with an ADA for his incredible work on Twitterrific for the iPhone and being the gracious man he is, he let Corey bring it back to North Carolina so the rest of us could get a fleeting glimpse of the “cube” before its return to Laguna Beach. Well, we thought it would be fun to create our own DIY ADA and mail that back to him just for kicks. We documented the creation process which you can find on the Iconfactory’s Flickr page. Needless to say the prank succeeded in putting a big smile on Craig’s face while relieving some stress around the office.

The good part of all this mayhem is that it keeps life interesting. There’s always a new challenge on the horizon, be it software, freeware or paying projects. Believe it or not, client work can sometimes provide a respite every now and then from the pressures we end up imposing on ourselves. Personally, if I can just get through July, I think I’l be just fine. Serenity now! Serenity now!

It always fascinates me to see what people’s workspaces are like. I love getting an inside look at how artists, programmers and designers organize their desktops and select the tools they need to do their job. Some workspaces border on zen-like art, while others take on an air of controlled chaos. Some of us work in our homes like my friends Wolfgang Ante or Craig Hockenberry. But most of us spend the majority of our weekdays at “the office”.

And so, I thought I would throw my hat into the ring and give you a small peek at my workspace. My desk at the Iconfactory in Greensboro is where I do much of the pixel-pushing, writing, designing and illustrating that helps keep the bills paid and clients happy. Each and every day, I’m fortunate to work in a creative atmosphere surrounded by talented and dedicated people. Like many of us these days, I’ve tried working at home for extended periods, but it just doesn’t suit me. I love the bustle of the Iconfactory and the creativity our “open plan” offers the group (except when more than 3 of us are on the phone at the same time). I hope you enjoy this small behind-the-scenes look where I spend my days. Head on over to Flickr to check it out. Enjoy!

Today, at Apple’s World Wide Developer Conference in San Francisco, the computer maker unveiled its plans for the next generation of iPhones as well as a sneak peek into third party applications headed our way. Due to hit public airwaves July 11th, Apple’s new iPhone/iPod Touch “App Store” as it’s being called, will allow users to purchase third party mobile applications directly over the air. I speak for all of us at the Iconfactory when I say we were just as surprised and delighted as you probably were to find our very own application, Twitterrific, featured heavily on Apple’s website.

It seems after flying high and far, sometimes to shady destinations, the little blue bird has finally gone legit. I don’t think any of us at the factory realized just how popular Twitter, and in turn Twitterrific would become in this past year. We’ve been making various software applications for a decade now, and in all that time, none of us would have expected such an unassuming little app to become our most well recognized piece of code. Twitterrific’s success speaks volumes about the fine work of the folks over at Twitter, and the hunger for today’s users to stay in touch with friends, relatives and co-workers via new media like social networks.

We’re very pleased the Mac community took to Twitterrific so well and helped make it the success it is today. We’re looking forward to bringing the application to a whole new generation of users for the iPhone and iPod Touch, and would like to extend our thanks to Apple for giving the blue bird such a fine new home. We feel both excited and privileged to be a part of the new App Store and are committed to bringing our users the best software we can offer. We look forward to these first steps on what is sure to be, a fun journey for both users and developers alike.

While we patiently wait for the new Apple Store to open at the Shops At Friendly Center here in Greensboro, a small bit of placation has appeared in the meantime. Yesterday when I walked into the Best Buy off of Stanely Road, low and behold part of the formerly all Windows PC section had been ripped out and replaced with an ultra-mini Apple Store. Right where Toshiba laptops, Dell desktops and other Microsoft loving hardware had stood was the familiar spartan trappings of Steve Jobs’ retail store. It was like the Borg had sliced out a 15×20 foot section of the Southpoint Apple Store in Raleigh, and transplanted it directly into the middle of Best Buy, carpeting and all.

While a surreal experience, it was great to finally see someplace in Greensboro where Apple products can be purchased. Since we lost our local CompUSA back in December, if you wanted to pick up a new MacBook or iMac, you had to make the trek to Raleigh or Charlotte. The inclusion of Apple goods in Best Buy is an impressive about face for two companies that have not always been on the best of terms. I think mini-stores like this one in Greensboro are a testament to Apple’s growing popularity and the strength of the brand. No matter what caused it, I’m just glad to see a tiny bit of Apple in Greensboro once again. Maybe now I can stop driving over to Friendly once a week to check on any signs of life. Nah!

Summary: The length of some audio podcasts are increasing at an alarming rate. Podcasters should learn to master the fine art of editing or risk losing large portions of their listening audience. I provide some helpful tips to help them avoid pitfalls and offer some anecdotal evidence on the subject.

Even if you read no further than the above summary, you’ll have a pretty good feel for what this post is about, where it’s going and what will be discussed. Unfortunately, this is more than I can say of many of today’s most popular audio podcasts. I’ve noticed a few alarming habits that podcasters are adopting that have put me, and others like myself, off from listening to their content. By writing about these trends, I hope podcast producers will look at the criticism objectively and perhaps find some room for improvement.

“The most valuable of all talents is that of never using two words when one will do.” ~ Thomas Jefferson

Rambling Ratholes

Almost a year ago, I started listening to the excellent Mac-based audio podcast by Leo Laporte and company called MacBreak Weekly. MBW is a “round table” discussion between Leo and a cast of regulars including Merlin Mann, Andy Ihnatko and others. I enjoyed MacBreak Weekly for a long time, until I noticed the length of the broadcast kept creeping up and up. The hosts would often wander off on tangents that often had nothing to do with the subject of the discussion. Leo proudly dubbed these tangents “ratholes” and they even came up with a little musical jingle for the things. They were cute at first, but soon grew annoying. When episode number 70 hit 112 minutes back in December, I had had enough.

The length of MacBreak Weekly episodes has been rising slowly for some time, and I don’t think they even realize it. I love a good 20 minute discussion about Apple IIc’s as much as the next fanboy, but there are limits. Laporte seems to have forgotten how to edit his podcasts and the result are bloated episodes. In addition, TWiT doesn’t even supply an episode summary until a week after its initial broadcast. Podcaster tip: if you can’t be bothered to listen to your own content and post a detailed summary of what you’ll be talking about for the next 1.5 hours, I can’t be bothered to listen.

“It is my ambition to say in ten sentences what other men say in whole books.” ~ Friedrich Nietzsche

Can I Buy Shares of GRUBR?

Another one of my favorite podcasts is The Talk Show with Dan Benjamin and John Gruber of Daring Fireball fame. Like MacBreak Weekly, episodes of The Talk Show have been getting longer. Unlike MacBreak Weekly, the creators of The Talk Show are firm believers in editing, which results in more “cake” and less “frosting”. And although the running length is increasing faster than that of MacBreak Weekly, Benjamin & Gruber haven’t yet reached the dreaded average running length of 1.5 - 2 hours that Laporte and company regularly flirt with.

Dan Benjamin says that they typically record 1.5 to 2x as much material as they need and then edit out all the non-essential bits to arrive at their final running time. They don’t set a time limit for The Talk Show, but they do make a conscious effort to bring listeners the interesting bits and leave the rest on the cutting room floor. This being said, I still think set running times are a good idea. Podcaster tip: It’s much easier for someone to plan to listen to a podcast from week to week when its length is fixed. A great example of this is NPR’s Wait, Wait, Don’t Tell Me. Each episode is 47 minutes long and so I know exactly where I’ll be when it starts, and when it ends. If you can’t say what you have to say in a set time, consider editing it down or breaking it up into parts.

“If you bring that sentence in for a fitting, I can have it shortened by Wednesday.” ~ Hawkeye Pierce, M*A*S*H

The Butter Zone

So how long should your average audio podcast be? Not surprisingly if you ask a podcast producer they’ll probably tell you “As long as it needs to be.” Unfortunately this attitude often reflects the desires of the creator and not those of the audience. People’s time is limited and in this modern age, attention spans wane. I took an informal survey on Twitter to ask people their thoughts about what was the right length for an audio podcast. Fifty people responded and took the poll. Although the tally can’t be considered scientific by any sense of the word, I believe the results are indicative of your average content consumer. Is it really any wonder that people’s preferred length for a podcast is the same as your average television show? Podcaster tip: When podcasts approach the length of feature films, people start to lose interest. It’s better to break long epics up into short, multiple features.

Another portion of the Twitter poll asked respondents where they listen to podcasts the most. A full 46% of them said “On the go” meaning in their cars, while jogging, riding the subway, etc. Sometimes I load up my iPhone with episodes of The Talk Show and listen to them on my morning drive of about 15 minutes. Until the recent spike in length, I was able to get through one episode of TTS in a single day’s commute, which was just perfect. Indeed, the 2005 U.S. census reported that the average American’s commute time to and from work was 25 minutes. Large cities like New York were a bit higher at 38 minutes, but all were under an hour. I think this fact helps explain the audience’s desire for 30-45 minute podcasts. By nature, people love closure and enjoying a podcast that can be completed in a single commute is a satisfying experience.

“Let me explain. No, there is too much, let me sum up.” ~ Inigo Montoya, The Princess Bride

To Sum Up

Despite what the creators of podcasts may think, their audience is looking for manageable chunks of auditory content that can be neatly parsed into a daily commute or a walk around the park. Thanks in part to the ever increasing HD sizes of iPods, podcast producers no longer feel restricted by file size, and have a tendency to let their hosts ramble. Unless content creators re-dedicate themselves to producing top-notch, edited podcasts, more and more people will undoubtedly lose interest. When I visit the latest episode of MacBreak Weekly and I spy a running time of 1 hour and 42 minutes, it turns me off. The length is too intimidating to even attempt and I just surf away. From one Mac fan to another, I urge Leo and others like him to take the words of Baltasar Gracian to heart - “Good things, when short, are twice as good.”




Hat tip to Craig for his help with the graphing portion of this post. Me bad with spreadsheets. Craig good.

Let me just say up front that the engineers, programmers and developers I work with are some of the most talented people in the industry. They manage to write software and code few others have the skill to create, and I am often in awe of their abilities. That being said, I’ve recently been reminded of an inequity between designers and programmers which I have to get off my chest.

Last week I watched the excellent video from the C4 developer’s conference with my friend Cabel Sasser of Panic fame called Coda Confidential. Something he said in his presentation struck home. At the 22 minute mark Cabel starts talking about Coda’s “Toolbar of Doom” and the implications the toolbar had on his developers. If you’re not familiar with the story, you can listen to the description of the problem from the C4 video, or check out Cabel’s blog post on the subject. The short version is that Cabel designed Coda’s toolbar to appear a certain way, the way he knew it looked best. But it turned out that designing it this way was hard. Very hard. After trying to bend the Cocoa toolbar implementation to their will, they decided instead to throw in the towel. And when Cabel says “throw in the towel” he means write their own toolbar code. From scratch.

Despite their impressive ability to solve the toolbar design problem, Cabel makes the point that he’s constantly “choosing his battles” between himself and the programmers at Panic. They don’t always have the luxury of writing code from the ground up to solve a particular design problem. They are constantly asking themselves is this particular design decision worth the time and effort it will take to implement? As I know from personal experience, sometimes the answer to that question is unfortunately, “No”. As a co-owner of my company, like Cabel, I’m constantly looking at the “big picture” to determine if a difficult design is worth the time and money required to implement it.

But from a creative point of view, purely as a designer, I still find it frustrating that the ideas and creations I come up don’t always get implemented. Some are considered “too difficult” or “too time consuming” to put into practice and therefore must be abandoned. I consider this to be a double-standard in our industry between designers and developers. As a designer, I’ve almost never told a developer I’m working with that a particular icon, user interface or web design is “too difficult” to implement. In my entire career, I think I’ve said “no” a grand total of 2 or 3 times. And that only happened because someone asked for something physically impossible, like making a 5 letter word legible at 16×16 pixels. I realize the programmers reading this will probably say “that’s because coding is more difficult than designing”. This may or may not be true, but that’s a whole other topic for discussion.

I know that even programmers themselves can’t always create the software or features they dream up, but it seems like they often have “outs” that simply don’t exist for us designers. We’re always expected to push through and solve the problem, while for them, something is either technically not feasible, would take too long to implement, or is simply a bad idea due to poor user behavior. Just once, I’d love to be able to tell a developer who’s asked me to solve a design problem “Nope, it’s too hard. Not gonna happen.”

I know that given enough time and money, pretty much anything is possible, and unfortunately most small software companies are not made of gold. We must therefore attempt to balance our desires as designers with what is best for the success of the product. I also know that the balance between a talented designer and a skilled programmer can transform mediocre titles into outstanding apps. I just wish I had the ability to even the score every now and then. I take solace in the fact that often as designers, we’re usually only limited by our imaginations rather than API’s or function calls. Our relationship may indeed be a one way street, but for developers, it’s often littered with road blocks.

With reports that iPhones are sold out of all three New York Apple stores, and Gartner analyst Ken Dulaney believing that Apple has placed an order for 10 million 3G iPhones, Apple’s stock price climbed another $3.66 today to $144.64. I’ve been keeping a close eye on AAPL and would love to have purchased some additional shares of the stock after it bottomed out in late February at $119. But given the recent volatility of the stock, I figured I should probably just sit tight.

I personally don’t buy the rumors of new OLED displays, but this could indeed be the time when the 3G version of the iPhone finally takes center stage, right before WWDC and the launch of the iPhone App store. The iPhone is definitely poised to fill the increasing hole left by slowing iPod sales, and so the App store couldn’t be timed better. The more I think about the sheer number of software possibilities for developers in relation to the iPhone, the more my inner Mac boy grins from ear to ear. Neither RIM, nor Windows Mobile or any of the other cell carriers have anything that even approaches the reach of the soon-to-be application store. Apple is about to make installing new software on your cell phone as easy as buying songs on iTunes. If I was a mobile competitor, I’d be pissing my pants and buying AAPL like there was no tomorrow.

Will AAPL return to the $200 a share price it held just a few months ago? Of course. I suspect how long the rebound takes depends on seemingly unrelated factors like the price of oil, the weakness of the dollar and the continuing problems in the housing market. All these things have depressed the stock artificially, which in the end is probably a good thing. It gives average investors a chance to jump in low and enjoy a (hopefully) slow and steady climb back up. Despite the recent plunge in price, I think this is a good time to own stock in Apple Computer. Retail stores are buzzing, thousands of developers are working away on cool new iPhone software and if we know Steve, there are bound to be a few surprises thrown in for good measure. Go AAPL, go!

Despite the long-awaited release of the iPhone SDK yesterday Wall Street in their usual “wisdom” decided to punish Apple stock. Despite all the incredible news about iPhone for Enterprise, the immediate availability of the beta, the iFund, and even the game-changing nature of the event itself, AAPL managed to lose $3.41 on the day. Here’s how I think it all went down:

Disclosure: Yes, I own stock in Apple Computer and I’m about to own a whole lot more. Once the reality of the SDK starts to sink into investors, $200 a share is going to look like peanuts.

Ever since Christmas of 2007, I’ve had a problem. Sudden, seemingly random Airport signal dropouts. These frustrating gaps can last anywhere from a few seconds to minutes or even hours. When this happens, the internet connection in our second story bonus room is lost completely. Sometimes it comes back on its own but lately we’ve had to turn Airport off and then on again to re-acquire the wi-fi signal. The problem has been so bad that I’ve even considered calling an electrician to hard wire the bonus room for CAT-5 cable. A costly and extreme solution to be sure. After two solid months of vexing investigation, I think I’ve solved the mystery. If you’ve been experiencing sudden wi-fi dropouts on your airport enabled Mac, read on.

The Usual Suspects

I’ve been reading about Leopard wi-fi problems for weeks but since our Macbook Pro is still running Tiger, these reports didn’t make sense. Perhaps it was one of the three Airport base stations we have in our home. The Airport Extreme in our home office acts as the router, and there is a second Extreme in the upstairs bonus room itself. When we first moved into the house four years ago, I set up an Airport network with an original UFO base station and an Airport Express in the hallway of the second floor. This served well for years, and when the new Airport Extremes were released, we upgraded but left the Express to boost signal.

All seemed fine until around Christmas when the dropouts started. At first I thought it was a hardware failure and tried swapping the Extremes, changing their location in our home, altering the configuration of the network from b/g compatible to just g, then to n. I tried closing the network, removing the Express completely, etc, etc. Despite all of this, the network dropouts persisted.

Next I tried removing the other Wi-Fi enabled devices in our home. Through a process of elimination I removed our Nintendo Wii, my wi-fi enabled iPhone and even my TiVO from the Airport network. I had suspected the TiVO for a long time since the dropouts seemed to come at set 5 or 6 hour intervals (when the TiVO was downloading program info?) and was disheartened to discover that after dissconnecting the TiVO for a full 2 days, drop outs were still the rule and not the exception.

A Break In the Case

The clue to the solution came when I made the connection between when the problems started and the time of year. I said earlier that the dropouts began shortly after Christmas of 2007, just when other families in the neighborhood would be getting wireless routers and hooking them up. Further clues were provided by my friend Craig Hockenberry that told me he has had similar problems due to interference from his neighbors. From Craig’s home, some 12-18 wireless networks are available. Being at the end of a dead-end street, I always assumed we were pretty isolated from interference from other networks. When we first moved in, my Airport network was alone in the neighborhood. But sure enough, a quick check with AP Grapher this week revealed between 6-8 other wi-fi networks. After a walk around the development, and chatting with neighbors, I was able to create a rough map of the wireless networks that surround our home.

Advances in 802.11 technology have dramatically increased the strength and range of home wi-fi networks. Unfortunately this also increases the potential for interference from one source to the next. You can see in the map to the right that although the house in pink is hundreds of feet away from mine, I still get a 42% signal from their wi-fi router. Craig turned me onto a few articles that talk about potential interference from sources like cordless 2.4 GHz phones, microwaves and especially other 802.11 devices. Suspecting one of these was the culprit, I watched AP Grapher like a hawk and noticed that our Airport channel would sometimes overlap those of our neighbors. When this happened, sure enough, a dropout occurred. In Mac OS X, I have Airport set to select channels automatically, and this turned out to be the root of the problem.

Book ‘em Dano!

When Airport is set to automatic, it quickly “scans” across the entire channel range and selects the one with the least interference to use. At the time of the scan, channel 11 may be relatively clear and so all is well. If however, a competing wi-fi network on the same channel turns on, or increases signal strength due to atmospheric conditions, that channel becomes cluttered with radio noise. The protocol for 802.11 is designed in such a way that when this happens, base stations can hold off broadcasting until the interfering signal goes completely away, which could be minutes, hours, or even days. This also accounts for the apparent randomness of the original problem.

Thanks to AP Grapher/Scanner, I can easily see the channels that all my neighbors are using for their networks. Since most wireless routers are set to channel 6 out of the box, avoiding this channel as well as two channels to either side is best. I’ve now set our Airport network to broadcast on channel 9 and I’m very pleased to report that so far, the dropouts that have plagued us low these many weeks, have ended. If you are able to manually set your wireless network channel to something that avoids the channels of those around you, this should do the trick. I foresee a time in the very near future however when the 11 channels currently used by wi-fi in the United States just won’t be enough. Hopefully, refinements in 802.11 technology (or something completely new) will stay one step ahead of the problem and keep us all up and running. Case closed baby!

You have to hand it to the people at PopCap. It’s amazing how something so simple can be so addictive. I mean the player strategy behind their hugely successful game, Peggle Deluxe, amounts to little more than a digital coin toss. Despite this, the game is immensely satisfying and keeps players coming back for more. One of the reasons is the sheer joy you get when you pull off shots like this:

In many ways, Peggle has a lot of the same visceral qualities that made games like Ambrosia Software’s Malestrom and Apeiron so great. These noteworthy creations from Ambrosia Software helped to inspire my love of Mac gaming and provided a great deal of inspiration when it came time to bring the user interface and general feel of Frenzic to life. Ambrosia has gotten away from these types of straight forward, fun as hell, games lately (with the possible exception of Sketch Fighter) and it’s too bad. I would kill for an updated OS X version of Malestrom. One that combines the simple fun of Peggle with the classic sensibilities of Ambrosia and the power of Mac OS X.

In the meantime, my hat goes off to the folks at PopCap for creating Peggle. I think it’s almost as addictive as Frenzic… almost If you have videos of your favorite shot replays, post links to them in the comments and help spread the Extreme Fever. Tally ho!