I discovered a bug in Hey Peanut running under iOS 4, which Apple released to the public today. The bug has been fixed. I had hoped to get an update to the App Store before today but I’ve been waiting for the new artwork for iPhone 4. I will be submitting the update to Apple as soon as possible. The bug, for those curious, causes Hey Peanut to crash when you touch the camera icon to add new photos.

In April I blogged about an issue I was having with Microsoft regarding a questionable past due invoice. I’m happy to report that the issue has finally been resolved. Microsoft owned up to the mistake and will be issuing a refund for full amount paid to the collection agency.

Long story short, the payment I made in December 2004 was applied to the December 2005 invoice. This basically resulted in me getting the first year of service for free, though I didn’t know it. And I never received the December 2005 invoice because it had been paid with the money charged in December 2004. Also, when the billing system was moved from Placeware to Microsoft, a mistake was made to my account which caused the December 2006 invoice not to be sent to me. Because I never received invoices for December 2005 and December 2006, it’s logical to see how I thought the account was canceled after the first year of service, which started in December 2004.

Thanks to the blog post in April, Microsoft did in fact contact me regarding the issue. If not for the attention received by the posting, I would have remained bitter towards Microsoft. Instead, an extremely helpful Julie McNamara-Dahl from Microsoft went above and beyond to get to the bottom of the issue. Julie’s efforts have single handedly restored my trust in Microsoft’s customer service. And best of all, with the help of others at Microsoft, she was able to get to the bottom of the matter and answer my question, “What happened?”

I hate that the matter blew up like this, and I hate that it was something haunting me for years. But in the end, the whole affair proved to me that Microsoft does listen and does strive to provide excellent customer service.

Finally, I want to say a big thank you to Julie and those who helped her. THANK YOU! This matter is definitely closed.

I ran into an interesting bug today while testing Hey Peanut on iOS 4. For those who don’t know, Hey Peanut is a universal binary, which means it runs on both the iPhone and iPad. My iPhone has the GM version of iOS 4 installed on it, which I’m using to test my apps under iOS 4.

Because Hey Peanut can run on both the iPhone and iPad, my code must include certain checks to avoid crashes. One check the code makes is to determine if the class UIPopoverController is available or not. Prior to iOS 4, this class was only available in iOS 3.2. The current release of iOS on the iPhone is version 3.1.3, and it does not include this class. To make use of the popover I use code such as the following:

   Class popoverControllerClass = NSClassFromString(@"UIPopoverController");
   if (popoverControllerClass) {
      popoverController_ = [[UIPopoverController alloc] initWithContentViewController:[self imagePicker]];
   }

Turns out there is a big problem with this code under iOS 4 causing Hey Peanut to crash each time. It wasn’t obvious to me at first why this code was failing but as I thought it more, and as I talked through the issue with an Apple engineer, I realized, “Duh! iOS 4 is running on the iPhone, not the iPad.” Simply checking for the existence of the class isn’t good enough any more. Instead, I need to also check the device type. So with a quick change to the code, shown below, I was able to fix the crash in Hey Peanut. The code now checks that the class is available and is running on a iPad.

   Class popoverControllerClass = NSClassFromString(@"UIPopoverController");
   if (popoverControllerClass && UI_USER_INTERFACE_IDIOM() == UIUserInterfaceIdiomPad) {
      popoverController_ = [[UIPopoverController alloc] initWithContentViewController:[self imagePicker]];
   }

A few weeks ago I was having some post-CocoaHeads beers with Jon Trainer and Daniel Jalkut. We were talking about the success I’ve had with Labor Mate. They both insisted I raise the price from $0.99 to something higher. Both had sound reasons why a price increase would work for Labor Mate. For instance, the price range for competing apps range is from free to $9.99. A higher price point will help Labor Mate stand out. Everything Jon and Daniel said made sense, but I was skeptical.

For those who don’t know, Labor Mate is a niche app for the iPhone. It has been in the Top 100 in the Health and Fitness category for multiple App Stores including the U.S. for more than a year. Back in November Labor Mate’s status in the Health and Fitness category started to drop due to two competitors being mentioned in the What’s Hot lists. Despite the drop in rankings Labor Mate continues to sale well, slowly and steadily earning more money per month. A big part of this success comes from international sales, which have steadily improved since translating Labor Mate into 8 other languages. Another part of the success comes from the fact that the app is rock solid. It doesn’t crash, and as one of the reviewers recently said about Labor Mate, “Maybe not the slickest looking app for counting contractions, but we didn’t want to risk crashing or accidentally losing data – we just wanted a reliable app that would work under pressure.”

Even though I was not confident of a positive outcome, I decided to follow the advice from Jon and Daniel. I raised the price of Labor Mate from $0.99 to $1.99. My plan was to leave it at the higher price for a minimum of one week. As expected the first full day at the new price saw spike in revenue. However, sales dropped. This trend continued for the first week. As a result, Labor Mate lost most of its visibility in the App Store’s Top 100 for Health and Fitness. I figured it was only a matter of time before sales and revenue hit an all time low.

Despite what appeared to be a downward trend, I decided to continue the pricing experiment for a second week. To my surprise sales started to return to its normal pattern, a spiky, Bart Simpson-like hair cut. What I noticed was exactly what Jon and Daniel said would happen. I started making more money. Jon and Daniel were right! Sure, daily unit sales were lower than before the price increase, but revenue was higher for those two weeks. So while Labor Mate dropped from the rankings of the Top 100 in the Health and Fitness category and the number of units sold per day dropped, in the end I made more money.

The next big question now is, will Labor Mate revenue continue its slow but steady climb at this higher price point, or will the overall trend start heading downwards? I’ve decided to keep Labor Mate at the $1.99 price for another week to see what happens.

Meanwhile, for those of you who prefer looking at charts, I’ve included the sales and revenue charts for Labor Mate covering the time period between April 1, 2010, and May 31, 2010. There was a spike in mid-April but sales started dropping afterwards. The red-dash line is the first full day at the new, higher price. The spike on that day was almost as high as the spike in April.