When the App Store first launched almost a month ago, I must say, I thought that it would be a great thing. Not only were iPhones and iPod touches opened up to have third-party apps available on them, but they would be available in one centralized location to make it easy for users to get these apps, and the fact that handle was handling distribution in its own store meant that little, smaller developers could have just as much of an entry into the iPhone app market as the big boys.

But now, it appears that the latter part of that belief was not true, as the more I’ve been reading about the developers’ side of the App Store, the more I’ve not been liking it.

Yesterday, I posted a topic on phpBB.com comparing the App Store to phpBB’s MOD Database (remember, I spent nine months on the MOD team as a validator during November 2005-August 2006), and noting some of the similarities and differences between Apple’s infrastructure for iPhone/iPod touch developers and phpBB’s infrastructure for MOD authors. Both run central databases for people to come and get add-ons for their main products (App Store to get apps for the iPhone/iPod touch; MOD Database to get MODs for phpBB). Of course, Apple’s App Store is the only way to get apps (other than jailbreaking), whereas MODs are not entirely dependent on the MOD Database for distribution. Also, Apple supplies the entire across-the-board system: the development tools (XCode et al), the system for distribution and marketing (App Store), the system for sales and security (FairPlay DRM), and the system that installs the apps (iTunes or the device itself). phpBB’s MOD team so far only has documentation of its MODX spec (though more tools will likely show up soon), and the distribution system (the MOD database), though they’re working on a Package Manager tool, codenamed “Blinky,” that will permit the auto-installing of MODs to take place. (Go listen to phpBB Weekly to hear more about all of that.)

But the major advantage of the MOD team here is that they’ve been handling submitted add-ons from developers to their central database for many years now–they’ve been doing it since before the iTunes Store even existed, before the iPhone was even dreamed of, and as the last month of evidence has shown, and was underscored to me more than ever by this TUAW post from today, the MOD team knows a lot more than Apple does about how to treat its developers in this regard.

One of the caveats of any centralized database, which can be either an advantage or a disadvantage, depending on the circumstances, is that developers lose some amount of control over their creation when it’s being distributed that way. When a developer is simply distributing an application on their own (like developers of Mac applications do), they really can do whatever they want, and the users downloading their stuff assumes the risk. But when a central group is maintaining a database of these add-ons, be it the App Store, the MOD Database, or anything else, it is in that group’s interest to ensure that the things appearing on their database are of at least a minimum amount of quality. At the very basics, apps/MODs must work as advertised, must be secure, and must be PG, otherwise the reputation of the entire service being offered will suffer. In fact, that’s part of the reason that there is an App Store or a MOD Database; their purposes are to give users confidence that when they are looking to download apps/MODs, they will be of good quality. It is, therefore, a privilege for a developer’s product to be featured on one of these services, and in exchange for that privilege, the developer gives up a few of its own freedoms.

That exchange of services and privileges, however, depends on a very delicate relationship between the group providing the service and the developer, and that relationship HEAVILY depends on good communication. For the most part, the phpBB MOD Team has, in my opinion done a fairly good job at communicating with MOD authors. They have clear standards for MOD authors on what is required for their MODs to be approved, they provide open forums (literally) for MOD authors to ask questions of and communicate with the team, and in the event that they deny a MOD, they are clear on why it was denied and what needs to be done to fix it.

Apple, on the other hand, does not appear to be having clear standards. Some of the bigger developers seem to be getting priority on getting apps and updates on the store while other developers have to wait in a seemingly long line, certain apps are being denied for basic aesthetic purposes that do not hinder the fact that the app is still usable and still works, and Apple has been repeatedly approving apps to their store (like that stupid I Am Rich app) and then later taking them down again with absolutely no explanation as to why, not even with the developer. This, coupled with the fact that the App Store is the ONLY way for developers to release apps for the iPhone, means that developers are finding themselves very unable to rely upon Apple to allow their app to succeed. Quite frankly, it appears as though Apple is being as incompetent at properly treating its iPhone/iPod touch app developers as it was at launching MobileMe and communicating with its paying customers. (And remember, to submit to the App Store, developers have to pay that $100 to get into the iPhone Developer Program too, so they’re actually paying Apple for these rights, and this is how Apple is treating them.)

While the bases of the App Store have been built, it is clear that some evolution needs to take place within the App Store so that it can better satisfy the needs of developers and end users alike. Here’s what I think is the proper prescription for the App Store:

• Apple needs to define clear standards for iPhone/iPod touch apps submitted on the App Store, and it needs to stick with these standards. Developers should not be surprised by learning that an app has been denied by Apple; the main point of Apple’s review is to ensure that the apps are secure, clean, work properly, and have some minimum amount of quality; that’s it. These standards should be made clear to developers, and if possible, Apple’s development tools should be able to assist developers in pre-validating their own apps to meet these standards. Furthermore, Apple should have a policy that it doesn’t come up with new standards “out of the blue,” but is clear about what is and is not acceptable on the App Store.
• Once apps are approved, they should not be taken down except for the most extreme of reasons, like if there was a security issue, decency issue, or some other critical issue that was missed the first time. If this happens, it should not be for some mysterious reason, but should be for reasons that are made known immediately to the developer and to the public, since after all, people may have already downloaded the app to their phone. This should not be done willy-nilly as has already happened with quite a few applications.
• Apple should permit some support for public betas. While Apple may only issue public betas of its programs once in a blue moon, there are companies that are dedicated to the philosophy of open source software, and this includes the philosophy of providing betas so that users can help companies test out their software. Currently, however, the App Store only permits final releases of apps, and this means that bugs in apps are more likely to go unnoticed, resulting in an increase of updates that are submitted and more disgruntled users. Since Apple has made the App Store the ONLY WAY for apps to be released, they should come up with a way for developers to release public betas. My suggestion would be a separate part of the store designated for public betas (it could even be restricted so that it could only be accessed via iTunes), which is clearly indicated to end users that the section is for beta versions of apps and so the quality of those apps are not guaranteed. Developers could optionally specify an expiration date for their beta apps, after which date the betas are no longer functional on iPhones/iPod touches until they’re updated (i.e. to require users to upgrade to a paid, full version of an app once it’s final).
• On the note that I briefly mentioned about companies believing in open-source, Apple needs to get rid of that pathetic NDA that developers still have to abide by. Okay, so you launched the SDK four months before the App Store opened, I could get the NDA then. But the store is open now and has been open for a month, and if you really want to see good quality apps on the store, you need to let developers talk with each other and exchange ideas and good coding practices. We’ve seen time and time again that open-source is the way to propel software forward, and Apple already believes that since so much of what makes OS X work is based on open-source software. Get rid of the NDA and let’s start moving forward, already.
• Developers aren’t just artists. They need statistics about how well their software is doing. They need to be able to hear from their users when they need help. Developers should be able to get accurate stats from the App Store on how well their app is selling and how much they’re earning so they can be able to determine whether they’re suiting their customers’ needs. The reviews system is leftover from iTunes, and is not that helpful to developers. Anyone can write reviews, even if they’ve never even touched the application, making it unreliable. It’s too easy to confuse the reviews section for a support section. I know that I’m a little short on original ideas for how to fix this one, but Apple should be smart enough to figure out how to make the App Store a true store for applications, not just a cheap ripoff of the iTunes Store. This is a completely different type of media that is being sold here, in a completely different way. You can’t just apply old habits to new technology and expect to get very far.
• And above all, if Apple really wants to see the App Store succeed, the best thing that they can do is to step back out of the way. Ever since the concept of the App Store was first unveiled back in March, people have been unsure of just how restrictive Apple was going to be on apps coming in the store, and the actions that Apple takes on its way into getting going with its store is going to determine how people look at Apple and the App Store. It’s also going to determine how willing developers are going to be to jump into the App Store, and if Apple turns the process of validating apps into an obstacle, then developers are not going to be willing to join this party, and that’s just going to hurt Apple and the entire iPhone/iPod touch ecosphere as a whole. Apple needs to stand back, just validate apps based on decency, security, and functionality, and let the App Store grow with as little Apple influence as possible.

I’ve said before on this blog that I truly think that the App Store can be a great thing that really takes the iPhone/iPod touch and gives it some real meaning, in my opinion. But that depends on Apple staying competent and doing what’s right to make it successful. Between a difficult iPhone 3G launch, an embarrassingly miserable MobileMe launch, and these App Store issues, July 2008 was not a very good month for Apple. Here’s hoping that they come full circle, fix their mistakes, and move forward.

Tags: App Store, Apple, authors, developers, iPhone, iPod touch, iTunes, MOD Database, MOD Team, phpBB, problems, Software, suggestions