Sunday, March 13, 2011

Japan Disaster Relief

All proceeds from the sales of the Tunemark Radio app between March 12th and March 20th will be donated to the Red Cross and Salvation Army for the disaster relief efforts in Japan.

If you prefer to make a direct donation to the relief efforts, Apple has set up a way for you to do it via iTunes here.

3/21/2011 UPDATE: Thanks for all the support! Over $620 was donated to the Japanese Red Cross Society and The Salvation Army from Tunemark Radio app sales.

Tuesday, March 8, 2011

Tunemark Radio 2.1 - the iPad update

Much to my disappointment, I accidentally introduced a bug into the 2.0 version of Tunemark Radio, causing the app to crash on launch on devices running iOS 3.x. Thankfully, Apple let me put through a rush update to fix the problem, so the new 2.0.1 version now available on iTunes fixes the problem for those people with an iPhone or iPod Touch running iOS 3.x.

Unfortunately, I hadn't realized the same bug also existed on any iPad that is still running iOS 3.x. and the 2.0.1 update does not fix that bug.

I had been in the process of creating an improved version of Tunemark for the iPad, and had it nearly complete this weekend when I started receiving reports of the iPad 3.x problem, so I decided to roll the new iPad look for the app into this bug fix update.

So, yet another update is now pending review with Apple, this time addressing the problem for those with an iPad running iOS 3.x., but also with the bonus of (in my opinion) a much better UI for iPad. Here's a screenshot showing how it will look on iPad:

Hopefully you will agree this is a much better look than what is currently Tunemark Radio on the iPad.

And in case anyone was curious what country-western music looks like in Japanese, here's another screenshot:

You can tap on either image for an iPad-sized version of the screenshot.

Tuesday, March 1, 2011

Tunemark Radio 2.0 now available!

Tunemark Radio 2.0 is now available on iTunes for 99 cents. This latest updated adds a few new features:

1) Album artwork and artist information is now available via If has any information about the current playing song, a “” button will appear allowing you to view the content provided by Also the album artwork (if available) will automatically be displayed on the “Now Playing” screen.


If you prefer to only have your own custom background image displayed, don’t worry. There is an option in the settings to disable album artwork.

2) The switching of stations should be noticeably faster. I discovered I had a minor inefficiency in the transition which caused a noticeable lag when starting playback of a new station.

3) If you are a Japanese user of the app and were disappointed that you lost all the “cool” English text when I recently added Japanese language support, I listened to your complaints. Via the settings, you now have an option to force the app to use English only. Please note, this will require that you either force-quit the app or reboot your device after choosing this setting.


Wednesday, January 12, 2011

Apple's New Policy on Single-Station iPhone Radio Apps

Back in November there was a a bit of stir in the radio community regarding one developer's claim that Apple was no longer allowing single-station radio apps. The article found here gives a decent summary of the story. The final conclusion was Apple hadn't changed their policy, but instead it was just this one developer's approach to making "template-based apps" that was the problem. Apple was even quoted as saying: "There are many unique radio apps on the App Store and we look forward to approving many more. One developer has attempted to spam the app store with hundreds of variations of essentially the same radio app and that is against our guidelines."

So, at the time of the article, the general thought was if you develop custom radio apps, and don't have them with little content other than playing an audio stream, then you should be OK. It turns out, this answer is true, but with one important caveat: Apple is now requiring any new single-station radio apps be hosted under the radio station's own developer account.

I ran into this new policy two days ago when I received a rejection for a new single-station app. The text of the rejection was a bit alarming to me when I first read it:

"We've completed the review of your apps[sic], however, we are unable to post them[sic] to the App Store because they provide the same feature set as your existing radios apps and simply vary the content. Apps that replicate functionality with different content create clutter in the App Store, hindering users' ability to find apps. They are therefore not appropriate for the App Store, as noted in the App Store Review Guidelines :

2.20 Developers 'spamming' the App Store with many versions of similar apps will be removed from the iOS Developer Program"

First, I only submitted one app, but the text implied I had submitted several. Also, the claim I was "spamming" the app store seemed extreme - every radio station app I've developed is commissioned (i.e. paid for) by the radio station and is completely customized per the radio station instructions. Granted, some of the apps are similar to others, but this is because it is common for one radio station to say something along the lines of, "I want an app just like the one you did for station X." From the radio station's point of view, it's all about getting their brand onto the iPhone - they want their listeners to be able to have easy access to their station, and having an app in the iTunes App Store is one way to do that.

Based on the text of Apple's rejection email, it seemed a bit doom and gloom for the single-station radio app. I quickly sent off an email to Apple requesting some clarification about the rejection, outlining the reasons why I thought single-station radio apps are not "spam" and asking Apple for some clarification.

Today I spoke with someone from Apple on the phone and got the needed clarification. Apple is no longer allowing developers to host large numbers of single-station radio apps under their own account. Instead, they are requiring the station to apply for their own developer account and host the app themselves under their account.

I can see why this makes sense for Apple. Most single-station radio apps are free. Apple makes zero money on them. Best case, they get a bit of free advertising for the iPhone platform from the radio stations when the station says, "Download our free iPhone app" on-air. Now, Apple will instead be making $100/year on each new single-station radio app.

Financially, from Apple's point of view, this change of policy makes sense. For us developers, it's not too big a deal - we'll just have to do a bit more hand-holding with the stations to help them set up their developer account and upload their apps. For a radio station, there's now going to be an increased cost for an app ($100/year), but really that's a not a huge amount of money.

The only part that doesn't make sense to me, is this goes directly against Apple's original explanation for why the app was rejected in the first place. They said single station apps "create clutter in the App Store, hindering users' ability to find apps", but this change in policy is not going to reduce the number of single-station apps. They're just going to be hosted under different developer names. But, since Apple reserves the right to reject an app for any reason, I suppose it's a moot point. Their reasoning doesn't have to make sense - we developers just have to do what they say.

The good news for radio stations is they will still be allowed to have their own custom apps.

All content copyright © 2009  Brian Stormont, unless otherwise noted.   All rights reserved.