Skip to Content

Free TUAW iPhone app -- try it now!
AOL Tech

sdk posts

Filed under: Analysis / Opinion, App Store, SDK

App Store Lessons: Picking an application name

iPhone developer Dan B. wanted to know if Apple would reject his application based on the name he wanted to use for his app.

So he did what you'd expect a sane developer to do. He wrote Apple. He used one of his technical support incidents to speak with the Apple Developer Technical Support teams and waited for them to reply.

They were quite prompt in answering, redirecting his question to the iPhone App Review Team.

Thank you for contacting Apple Developer Technical Support. We provide support for code-level questions on hardware & software development, and are unable to help you with your app naming question.

Please contact the iPhone App Review Team for assistance. You can contact them directly at [address redacted].

While you were initially charged a technical support incident for this request, we have assigned a replacement incident back to your account.

I hope this information is helpful to you.

So Dan contacted the App Review team. And they wrote back too.

Thank you for contacting the iPhone Developer Program. This email address is for inquiries regarding status of application submissions.

Apple is not able to provide pre-approval to developers for proposed application submissions.

We ask that you please review the Program License Agreement details against the specific application you wish to develop and submit any applications for App Store consideration in line with the application submission processes for the program.

If your application does in fact get rejected by the app review team, then we will notify you on what appropriate corrections/changes should be made.

So what's a developer to do? It seems like the only way to vet an application (let alone an application name) is to submit it and see whether Apple rejects it or not. If the name is used in the application art, you might have to redesign your screens. If the application idea is not okay, you might end up throwing away all your development costs because Apple would not give a preapproval before starting serious development.

Dan's problem reflects a wider problem with Apple's App Store black box. Developers should be able to pay for support incidents for exactly this kind of situation. It appears that Apple does offer this high level of consultation to partners and other companies that they work with (even to the point of having Phil Schiller call Google directly to discuss the progress for the Google Voice app review). Shouldn't they offer a similar kind of service to smaller developers?

Have you been able to get these kinds of answers out of Apple? If so, how did you approach the matter? Let us know in the comments...

Filed under: Software, iPhone, App Store, SDK, iPod touch

Turn your Flash into iPhone apps with Flash Professional CS5

So there's still no Flash in Safari, but once Adobe hatches Flash Professional CS5 you'll be able to port your wacky Flash games or animations out to real, live iPhone/iPod touch apps. Yep, ActionScript 3 nerds rejoice: that tasty App Store pie will soon be yours, never minding the whole plug-in debate.

This is truly quite awesome in one regard, as it lowers the barrier to entry for some app developers, and will ease the port of some cool online games that we've seen floating around the interwebs. Then again, if you've spent a little time at places like Newgrounds.com, you will quickly see the dark side to this announcement from Adobe. All those crummy Flash toys online just got one step closer to coming to life on the App Store (we're guessing most will sell for the low, low price of $.99). At this rate there will be more apps than iPhones!

Still, back when I taught animation and game design, we had a lot of fun playing around in Flash for the powerful prototyping capabilities, if nothing else. It would have been cool to test games on the iPhone so easily. The video on Adobe's site looks pretty cool, with them touting the "responsiveness" of apps. Yeah, unlike the slowpoke performance my kids suffer on our G4 Mac when playing Flash games, eh? I get it -- when Unity 3D for iPhone came out there were problems with performance (it has matured nicely now), and any tool that exports in this way (turning an .fla into an .ipa, essentially) is bound to suffer from performance. Does anyone else find it ironic that a plug-in that was designed to make multimedia on the web lighter has become one of the most bloated? I digress.

No word on what SDK features are supported yet, but you can sign up for the demo when the beta starts. Those SDK features could be a killer, of course. If you can't leverage some of the features on the iPhone (multi-touch, GPS, camera, etc.) these may be relegated to the Entertainment category. One other thing to note about all the CS5 applications: they will be Intel-only, Cocoa and 64-bit native.

Update: Well, lookee there, apparently some games in the store have been using this already. Did you know South Park Avatar Creator was made using Flash? Amazing.

Filed under: App Store, SDK

Apple introduces the App Store Resource Center

As part of Apple's efforts to make the ins-and-outs of the App Store more clear to everyone, Apple has just Introduced the App Store Resource Center. Apple states this new site is "a single destination where you can find everything from how to prepare for submitting your app to managing your app once it been posted to the App Store."

Basically, this new site offers an easy way for developers to read over and learn the many different policies and details about the App Store. It covers app submission, the App Store approval process and managing your app details, among other things There's really not much new, but you maybe able to find stuff easier now instead of looking through large PDF App Store guides.

If you're one of those developers who feels lost around iTunes Connect, you'll probably want to look over the guides in this new site. Anyways, if you're a registered iPhone developer, check out this new site, you just might learn something, maybe.

Filed under: Rumors, Video, Beta Beat, Developer, iPhone, SDK, iPod touch

Wondering what's in iPhone OS 3.1? There's a YouTube video for that


So here's something interesting, if you're curious to know what features might be in iPhone OS 3.1. It seems YouTube is chock full of videos shot in what seems to be defiance of Apple's NDA for 3.1 features. A couple of gems hint at expanded copy/paste functions, and there's one video which we could swear might hint at a real-time zoom... perhaps not just for photos but for framing video?

Anyway, it's a bit of a mining expedition, as searching for specific [REDACTED] methods or properties yields best results, so don't get all hot and bothered thinking you'll peep an iPad by searching for "setAppleTabletSize" or something. In fact, all of these could be fake, although the sheer number of videos seems to suggest something other than a grand deception.

Filed under: Gaming, Software, Developer, iPhone, App Store, SDK

iSimulate brings iPhone apps to the big screen


Apple's iPhone simulator built into Xcode is nice, but it doesn't completely replicate the actual feel of playing with an iPhone (not to mention that things like multitouch and accelerometer info can't be tested on screen). Enter iSimulate, a new app from a company called vimov. In conjunction with a program on your Mac, it allows you to take the input (including multitouch and accelerometer) of an iPhone, and wirelessly connect it to an app running on your monitor. The effect, as you can see above, is basically an iPhone controlling a big-screen app.

Which has all sorts of possibilities. Developers can use it to both test and show off their apps, which is nice. But perhaps more importantly, (assuming it works smoothly -- we haven't tested it yet) it will let people use apps on their big screen monitors. Playing on the iPhone's screen is fun and all, but wouldn't it be nicer to play on two big screens at the same time?

The app might not quite be ready for that use quite yet -- not only is the app for your Mac called an "SDK" (which definitely means it's meant for developers, not gamers), but the price might be prohibitive as well. They launched it at $2, and the price is going up exponentially (it's now $8) until it arrives at its final price of $32. But this is definitely a great idea. And it if happens to be popular even at that price (for consumers and developers), we wouldn't be surprised to see Apple finally "get it" in terms of bringing some of the App Store's offerings to their own big screen.

Filed under: iPhone, SDK, iPod touch

Apple posts iPhone OS 3.1 Beta 3 for developers

Apple has just released Beta 3 of iPhone OS 3.1 for iPhone developers. As this remains under NDA, I cannot post any details about changes to the OS. The updates include the OS for the device, as well as the SDK used to develop iPhone applications. If you're a registered iPhone developer, head on over to the iPhone Dev Center to download your updates.

Filed under: Analysis / Opinion, Apple, iPhone, App Store

App Store Lessons: No promo codes for apps rated 17+

Developers whose apps meet the criteria for a 17+ rating in the App Store are now running into yet another roadblock, but this time it's not about getting their apps approved, it's about distributing them. Or, more specifically, distributing promo codes for them.

Typically, when a developer uploads a new version of an application to the App Store, they have the ability to create up to 50 promo codes, which they can then provide to media outlets for reviewing the application, give away to users in a contest, etc. Aside from some reasonable restrictions on their usage (you can't sell them, they expire after 28 days and are one-time use only), promo codes provide quite a bit of flexibility to developers of paid apps who wish to freely distribute their app to select individuals without having to worry about the hassles of exchanging device information and doing special ad-hoc builds.

So where is the problem? It's in the new app rating system that was released a few weeks ago. As it stands, neither the 3.0 software nor iTunes display parental warnings when using a promo code to purchase apps with a mature (17+) rating, so Apple has made the promo code functionality unavailable for apps that fall into that category. We were informed of this condition by a developer who prefers to remain anonymous.

This obviously puts developers of these apps in a bit of a bind, as well as eliminates the potential amount of sales that could come from being able to distribute promo copies. Developers in this position may be stuck doing ad-hoc builds or going back to the questionable practice of sending iTunes gift cards to reviewers.

And if you're thinking this just applies to the massive number of adult-oriented apps that have recently poured into the App Store, you're wrong. Apple specifies that any application that may contain high levels of offensive language, violence, sexual content, or references to drugs or alcohol receive a rating of 17+. But, according to Apple, apps that feature an embedded web browser or provide access to 3rd party content also automatically require the 17+ rating, regardless of the application's content or intended audience.

Here's hoping that Apple is already working on a solution to this, as the lost potential sales caused by this not only affect the developers of the individual apps, but the overall success of the App Store as well.

Update: Several developers have reported that they are now able to request promo codes for their 17+ rated apps. We have an updated post with details here.

Filed under: Gaming, Software, Freeware, iPhone, SDK, iPod touch

OpenFeint drops dev fees as Chillingo announces social gaming network Crystal SDK

The social gaming market on the iPhone has taken two sharp turns recently. First up, right after announcing that their system hit a full million users, OpenFeint announced that their social gaming platform has gone completely free for developers. Originally, the SDK was free to download, and then there was a small cost-per-user fee for developers, but with this new change, that cost is gone, and OpenFeint will now make all of their money, as we were told by Peter Relan, from referring users to other games and in-app purchases, and then taking that cut from Apple.

The popular publisher Chillingo has also announced a newcomer to the social gaming scene: they're planning to introduce another system called Crystal SDK, that will presumably both be free to all developers, and automatically included in most of Chillingo's games. Their release specifically tells us that "Crystal is iPhone's answer to Microsoft's Xbox Live," so they're officially throwing their hat in an already crowded ring.

With a million users, OpenFeint is still the biggest network going, but obviously Chillingo believes there's still many more to pick up. Should be interesting to see, as always, what users decide to do.

Filed under: Gaming, Software, Odds and ends, Apple, Developer, iPhone, App Store, iPod touch

Worms for the iPhone submitted to Apple


Everyone's favorite battling invertebrates are coming to the iPhone and iPod touch very soon -- the game was actually announced a little while ago, but Team 17 now says the game has been sent off to be examined by Apple's eyes, and so, as long as it doesn't have any objectionable content (you can't object to exploding sheep, right?), we'll see it up for download very soon.

Exciting. Unfortunately, I'm coming off of a Worms 2 purchase on Xbox Live, so I'll probably be passing on this one, but if you haven't had a Worms fix in a while, the video on the next page shows what Team 17 is saying over on their Facebook page: it's "a full console-style experience," with extra options, including probably the ability to play your own music as you play. Multiplayer will only be pass-to-play to start with (bummer!), but they're hoping to add in both Internet and Bluetooth local multiplay at a later date. And there's no official word on price yet, but we should know it soon: look for Worms on an iPhone near you.

Continue readingWorms for the iPhone submitted to Apple

Filed under: Gaming, Software, Odds and ends, Developer, iPhone, App Store, SDK

Scoreloop introduces Scoreloop Community for the iPhone

We've talked about OpenFeint quite a few times on the site before (and even interviewed the creators), but while they're definitely one of the biggest names in creating gaming communities for the iPhone, they're not alone. A company called Scoreloop has today announced a service called "Scoreloop Community," made up of two different features: a web presence, and a downloadable application for the iPhone that hooks right into other developers' games and apps and allows players to create avatars, view friends and their activities, and share challenges and high scores with others. Just like OpenFeint, Scoreloop says they're offering an easy-to-implement solution for push notifications, letting players send and receive messages (as well as promote and encourage usage of games in the service) and earn achievements and tokens.

Of course, the real test for services like this will be in the implementation -- while OpenFeint claims a nice stable of developers, we still haven't seen too many apps take advantage of the latest and greatest versions (Pocket God is an extremely popular app that has implemented OpenFeint, but they use an older version of the software that doesn't have nearly as many features as the latest). Scoreloop says they've got over 50 game commitments from third-party developers already (it sounds like Zombie Pub Crawl is their biggest title yet), but even then, it remains to be seen exactly how devs will implement their functionality, and how players take to the service.

If you're a developer looking to implement push notifications and social challenges and networking in your app, it seems that there's no shortage of companies willing to step in and help you do exactly that (you can download the free SDK, if interested, on Scoreloop's site). But in terms of how consumers view and will use these networks, it's still a very wide open field.

Filed under: iPod Family, Developer, iPhone, SDK

Developer-to-developer: application sharing for the iPhone simulator

Last week, TUAW showed you how to sign iPhone applications for informal developer-to-developer distribution. That approach lets you share applications between members of the iPhone developer program by using your signing credentials to authorize the application for use on your development units.

iPhone applications compiled for the Intel-based simulator can also be shared between developers. And, since the free developer program offers access to the simulator, the apps can be distributed even more widely than with the re-signing approach.

Simulator testing does not offer the full suite of device-specific capabilities. You cannot simulate the onboard camera or retrieve proper accelerometer feedback. The simulator does not vibrate or provide general multitouch input. (You can pinch, but that's about it.)

The strength of simulator-based distribution is that it lets you send out applications for early testing and feedback. Sim-only tests strengthen the preliminary design process; this approach helps solicit feedback on user interface and general program layout before the main development push gets underway.

Simulator-based apps are easy to transfer and easy to use, cutting out a layer of overhead that's needed for when you go to a full ad-hoc beta.

To distribute a simulator application, go to the Library/Application Support/iPhone Simulator/User/Applications/ folder in your home directory. There you'll find the application sandbox folders that are currently installed for your simulator. Each folder is named with a unique id (i.e. 56E66CE5...DC028F) that does not reflect the folder's contents.

You'll have to peek inside to determine which folder is which.The folder contains the application, and three sandbox directories: tmp, Library, and Documents.

To share a simulator folder compiled for 2.2.1 and earlier, you must zip up both the folder with the application and the .sb (sandbox) file that shares the same name as the folder. 3.0 and later applications do not use a .sb file. Just zip up and share the folder.

Install the shared app by decompressing its sandbox folder (and, for 2.x, its .sb file). The recipient must have installed the iPhone SDK. Drop it into the simulator's Applications folder on another machine and launch the simulator. The app should appear in the simulator, ready for testing.

Filed under: iPod Family, Developer, iPhone, SDK

Apple releases 3.1 beta for iPhone SDK

Apple has released a 3.1 beta for the iPhone SDK. Both the SDK beta and firmware are available for testing and development to paid members of the iPhone developer program. As pre-release software, any details about this new release remain under NDA.

A pre-installation advisory and beta release notes are available as per Apple's usual release strategy. As before, you cannot use the 3.1 SDK to create applications for submitting to the App Store, so if you plan to download it be prepared to create a separate installation directory.

The new release comes just on the heels of the public 3.0 firmware. Its full-dot-number indicates that it contains more than just minor bug fixes (a relatively minor revision would probably be listed as 3.0.1).

Thanks to everyone who sent this in.

Filed under: Analysis / Opinion, Gaming, iTS, Odds and ends, TUAW Business, Apple, iPhone, App Store, SDK, iPod touch

TUAW Interview: OpenFeint, continued



Have you seen anything like that already, where developers have said, well we thought about doing it this way, but we're going another way?

PR: Too early. The phones aren't even out yet, user experience hasn't occurred yet. I would say July, we'll get a lot of feedback once these games come out with push notifications. The other thing that's kind of interesting, by the way, is that OpenFeint is working on cross-compatibility, because if I have a 2.2 iPhone and you have a 3.0 iPhone, and you send me a social challenge, in my app on 2.2, it won't show up as a push notification, right, because I don't have the 3.0 iPhone. So we are support the concept of push notifications in the plumbing and infrastructure of OpenFeint, however on a 2.2 phone, whenever the user next opens the app, they would see a screen that is an OpenFeint screen that would have a notification saying "you've got to beat my score," as opposed to seeing it on the iPhone icon, as a number, like the Mail thing, where it says you have notes waiting for you.

So I think as a user experience, the jury's still out, because the platforms are just getting ready, right? So the key here is to say that we're going to make it trivial by continuing our tradition, which is no servers, very easy to integrate, and some big games will launch in July with push notifications and then we'll go from there.

I think, to a certain extent, the same thing will happen on the microtransactions side. It already has happened with Xbox Live -- I don't know if you remember the story of horse armor, where everyone says "how can you release a different graphic and ask us to pay for it?" Have you seen examples yet of how developers want to use microtransactions? Are they aware of that danger or are they fearful of that at all?

PR: So I think the obvious one, just because I have, as I said, investments in companies in the Facebook app space, the big reason for microtransactions is virtual goods. So any kind of virtual world, avatar apps, some of these Mafia iMob apps, you can assume that there will be virtual goods unlocking with microtransactions. That one I think will translate over fairly well, in fact Net is going next week to China, where he's a keynote speaker at Tencent's annual conference. Tencent is an Asian company which does a billion dollars in microtransactions, all of it virtual goods. So I think that microtransactions, as we see them on social networks today, will come pretty much that way onto the iPhone social network, or the iPhone gaming network.

NJ: I also think that it will actually lead to the pricing, might even drop dramatically, but those who are charging for applications are going to go free, because they're going to earn much more by making it free and leveraging microtransactions.

Yeah, if you're charging $4 for an app and can sell four levels for $1 each, that's the way to go.

NJ: The user starts playing, gets very engaged, and wants to get to the next level and make the purchase, and it's very difficult not to make the purchase if you're engaged and you want to continue the game.

PR: The thing that's a little trickier, I think, is when you have microtransactions that aren't directly virtual goods, because virtual goods don't fit the theme. But are like chapters, or just additional content in the game. Then, I think, the business model is a little trickier, because that's your content update strategy, and to some extent, the iPhone user is used to -- like, if you look at the success of Pocket God, it's a double edged sword. If you talk to the Pocket God guys, their game is one of the few games that stays in the top five constantly. It's just always in the top five. And they use OpenFeint, and they're going to use push notifications, but when we spoke to him about microtransactions, he said, I have to figure that out, because their commitment to their userbase is, every week you're going to get an update with more content. So given that he's already committed that on the current price point, how does he unlock more content with microtransactions? So he was the first to say I definitely want to do push notifications, but I have to think hard about how I could incorporate microtransactions into Pocket God. So I do think there's a little more complexity there, especially when it's not just direct virtual goods. But I think they'll crack it. I think some other people we're talking to are certainly thinking of Chapter 1, Chapter 2, Chapter 3, three microtransactions. And certainly the virtual goods guys are like no questions how they'll do it.

And there are definitely precedents for both, in terms of episodic gaming on other services. Jason maybe you can talk about this, too, as a developer -- I'm really interested in the balance between making sure that what you're selling people is worth it, or something that's not. If you're asking to pay a dollar for a gun that's just a re-skin, people won't go for that. What do you think of that?

JC: I think, as a game designer, what you have to really think about is the motivations for why people will want to purchase this content. Whether it's a re-skin or not is less important than what it will allow you to do in the game. And the reason why I think virtual goods have done so well on social networks is that social pressure is a huge motivator to getting people to do things, and if part of that social pressure results in you engaging and buying virtual content, people are much more likely to do it. I mean, if you just have another gun that allows you to increase your DPS by two points, that's not terribly interesting to anyone but the ultra hardcore gamer, and then they'll probably just be pissed off that they have to pay for it. So that's not really an appropriate way to go about it. As a traditional gamer, buying episodic content or buying level packs, or substantially new gameplay experience, fits with my head, and then virtual goods, I think, have to be motivated through social pressure.

And the last question I have is just about the future of OpenFeint. I have to give it you guys -- there were quite a few, and there still are, services poking around that want to do the kind of stuff that you're doing. And just in terms of size and influence right now, you're kind of the top of the heap. So what's next, are you planning to kind of sit on the heap and just keep things set, or are you still aiming to improve here?

PR: I think that definitely we will continue to innovate and add more services to the platform -- there's no question that it's a platform play, and that we will continue to add features and additional things. I would say two things: one is, we will publish games, always, on top of our own platform technology, that will really kind of push the borders of gameplay design around the OpenFeint platform, to sort of demostrate and lead the way. So in the last announcement, we did hint at a new game coming out this summer based around push notifications and microtransactions, where we want to lead the industry. Because we never think that by being in front today, that we will be always in front. So we want OpenFeint to be the premiere platform, we agree that today, we certainly feel like it's way up there, but we feel like you constantly have to build new product on top of your platform to really make a world class platform. Because otherwise you're just sort of opining and thinking oh, this is good stuff. So we always want to test our own platform, and expect a title this summer based on OS 3.0 and OpenFeint features.

The second thing, which is, I think we're really doing something different around the business model. Ngmoco announced their Plus+ platform this week, and it's really a publishing tool rather than an open platform, and we're pretty proud of the fact that we're sort of the biggest player who is really able to provide an open platform where a developer does not have to make a publishing deal with us in order to get access to the platform. Ngmoco's platform is hey, we have this platform, it's part of our publishing network, and if you want to publish games with us, that's how you get the platform, and obviously you know the economics of the publishing business in the game industry, right? There's revenue that has to be sacrificed there. So I think as a guiding strategy, we will never make our platform related to anything with our publishing because it's our belief that this OpenFeint thing does two things that we will always have to provide for publishers: no servers, because 90% of developers have no experience building servers, they build great console games, client side stuff, C, C++ programming, all this stuff, but they really don't have any backend experience. And two, we're not going to take rev share, in terms of publishing deals. And those two things, I think, are sort of our long-term guides. The third thing is to build our own games constantly, so we can use Danielle and Jason's game design and knowledge to say here's the kind of games we can do. So if we can do that and execute, I think, with some fingers crossed, with some luck, we'll emerge as the de facto standard, which is our goal.

I had talked to Danielle a little about pricing already, but I wanted to ask about microtransactions as well -- when you do that stuff, are you not skimming off revenue as it comes through, or what is the pricing scheme there?

PR: Well even today, we have cross promotion inside OpenFeint 2, even before microtransactions, where if two players meet in a lobby, and they're from different games, then one player clicks on the other player's game, and you go to the App Store and you buy that other player's game? That's what you call our one-touch iPromote product inside of OpenFeint, it's a big draw for a lot of developers, because our community is now three million and growing -- we call it our social bazaar, because the App Store is so cluttered now that it's hard to differentiate. So you use OpenFeint and get your game in front of three million people in these lobbies. That revenue, when someone buys a game using OpenFeint's cross promotion feature, doesn't come from the developer, it comes from Apple. Because we are an Apple affiliate, through BigShare. So we take the user into a webview, which is our own catalog, where you can buy games off the App Store, and then Apple actually pays us. So that's hopefully -- this is the same thing, the whole idea is to get Apple to pay us every time there's a purchase in the App Store, including in-app purchases, as opposed to the outside.

Great. That's pretty much everything I had to ask, was there anything else you wanted to share? I guess we'll keep an eye on the game coming out this summer.

JC: Yeah, I guess the only other thing worth mentioning is that OpenFeint is available now -- it can be downloaded by anyone from our website. It's real.

Cool. Thanks very much.

Filed under: Analysis / Opinion, Gaming, Software, Odds and ends, Developer, iPhone, SDK, iPod touch

Two different services offering plans to developers for push, microtransactions

With iPhone OS 3.0 only having been released yesterday, two big companies are already angling to be developers' go-to for setting up push notifications and other online services for the new apps. OpenFeint was the first service we've heard about -- they have been offering social networking connections to developers for a while, but with the new firmware release, they tell us that they're also hosting options for both push notifications and microtransactions to their stable of app developers.

That stable includes apps like Pocket God and Aurora Feint (Danielle Cassley of both Aurora Feint and OpenFeint told us a while back that she was very excited at the prospect of microtransactions with 3.0), and both of those games, as well as others on the service, are planning to include push notifications with "social challenges" -- you'll challenge a friend to complete a certain goal in game, and then get notified when they meet that goal. Look for those new features in an OpenFeint app near you.

And OpenFeint isn't the only service jockeying for developers' attention -- Urban Airship is also making a bid to host push notifications for iPhone game developers. They've landed one of the first push-enabled games, Tap Tap Revenge, and are looking to offer push to more devs, along with in-app purchase support as well. They don't quite have the library together that OpenFeint already does, but their service integrates, they say, in just a matter of hours, and their aim is to make it "brain dead easy" for developers.

The floodgates are open, and we're sure to see more and more companies jump in on hosting plans like this in the future. Prepare to be pushed.

Filed under: iPod Family, Bad Apple, iPhone, App Store

App Store Lessons: the game changer rejection

A new kind of App Store rejection is making the rounds in the iPhone World. It's not about violating the SDK. It's not about objectionable content. It's about Apple empowering its reviewers to reject software without providing any substantive reason or feedback. TUAW reader Kenneth Ballenegger received the following rejection notice for his iLaugh application.

This kind of rejection is a gamechanger. Devs have complained that Apple's review policies to date have been inconsistent and arbitrary, since it was relatively easy to compare rejections and demonstrate the multiple standards in play. This rejection shields Apple's internal processes even further. Instead of moving towards transparency and responding to developer concerns, Apple has pointed itself in the opposite direction.

Making this rejection sting more, the app already was in the App Store; this submission was a bug-fix update. The premium edition of the same app, submitted at the same time, was approved without issue. It seems that previous and current approvals for the same application would argue in favor of letting this version through, or at a minimum providing an explanation of what's wrong with this one. As Christina posted yesterday, developers aren't getting straight answers about App Store rejections, even at WWDC.

"Sole discretion" hides a lot of possible review errors, both subjective and accidental. It makes it harder than ever for smaller companies to appeal rejections and denies them a factual basis on which to evaluate whether their rejection was issued in error. It also gives a firm answer to those who have been hoping for a transparent ticketing system and a open appeal process. Apple isn't interested; it's their store, their rules, and Caveat Developer to anyone whose business plan depends solely on Apple's beneficence.

An app full of admittedly lame jokes might be an appropriate candidate for App Store rejection, but the combination of veto power, the opaque review/appeal process, and inconsistent and capricious application of Apple's ax adds up to a troublesome situation in the developer ecosystem and in the App Store.

Postscript: Kenneth writes in to clarify that the 1.1.1 bug-fix update submitted 3 months ago was rejected. This will not affect his 2.0 Lite version, which was just submitted.

Tip of the Day

F11 moves all your windows off the screen so you can quickly glance at your desktop. F10 shows you every open window in an application. F9 shows every open window for every application that isn't hidden or in the dock.


Follow us on Twitter!
 TUAW [Cafepress]

Featured Galleries

DNC Macs
Macworld 2008 Keynote
Macworld 2008 Build-up
Google Earth for iPhone
Podcaster
Storyist 2.0
AT&T Navigator Road Test
Bento for iPhone 1.0
Scrabble for iPhone
Tom Bihn Checkpoint Flyer Briefcase
Apple Vanity Plates
Apple booth Macworld 07
WorldVoice Radio
Quickoffice for iPhone 1.1.1
Daylite 3.9 Review
DiscPainter
Mariner Calc for iPhone
2009CupertinoBus
Crash Bandicoot Nitro Kart 3D
MLB.com At Bat 2009
Macworld Expo 2007 show floor

 

More Apple Analysis

AOL Radio TUAW on Stitcher