During Apple's Q3 Conference Call on Monday, Chief Operating Officer Tim Cook reported that, like the iTunes Store, App Store is not meant to generate revenue but to drive iPhone and iPod Touch sales. They've added 400 Apps to the 500 available at launch, bringing the total (at call time) to 900, though the percentage of FREE (as in beer, not speech) Apps has fallen from 25% (~125 at launch) to 20% (~180 now). Under $10 Apps remained constant at 90%. Seems like that's the current magic ceiling for many developers. And with over 25 million downloads and counting, they may be right.
What else is going on in App Land? Read on to find out!
With new Apps hitting the store at an ever-increasing rate, be sure to check out Brian's ongoing iPhone App Avalanche watch list, and for feed-reading demons, Pinch Media is providing both New iPhone Apps and New FREE iPhone Apps lists via RSS.
Dieter mentioned how well received the iPhone SDK/App Store offering has been by some developers, including those coming from other handset backgrounds such as RIM and their Java environment. Exposure developer Fraser Speirs goes so far as to say the iPhone will be Apple's mainstream platform by 2012. Gleeful over the 1,000,000 iPhone 3G sales opening weekend, he says:
[M]y iPhone app, Exposure, has picked up on average 3,200 new users per day since the App Store opened. Exposure already has twice as many users as FlickrExport for Aperture.
Developer Ilium, who we previously mentioned had mixed feelings over the silence surrounding how long it would take Apple to approve Apps for the Store, finally saw their eWallet app appear (look for a TiPb review shortly). 1Password developers Agile Web Solutions, however, are still waiting.
NetNewsWire developer Brent Simmons, meanwhile, vented to Wired about the secrecy and slowness surrounding the SDK and App Store approval process, including 4 updates to his App Store app having been uploaded but not yet made available to end users.
The platform is wonderful. It’s like what we’re already used to — Cocoa on Macs — but smaller and more streamlined, and, well, tons of fun to work on. The secrecy makes it difficult. For Mac programming, there are all kinds of resources — mailing lists, bits of code posted on the web, wikis, other developers — to help out. It makes a difference. For iPhone programming, no. We’re not supposed to discuss actually programming on the iPhone with anybody — even though that would raise the quality of the apps. The secrecy and locked-down approach also made getting beta testers on board pretty difficult. I bricked one of my co-worker’s phones in the attempt. (He got it un-bricked a day later. Temporary brickage.)
Martin Gordon has experienced this first hand, with his Flickr based App getting rejected by Apple not once but twice. First time it took two weeks for Apple to notify him it was rejected for failure to provide log-out or account changing functionality. Second time was for a free demo version of his app, with Apple advising that while "Free" and "Lite" versions were fine, no mention of demo or beta, or reduced functionality that references features available only in a "full" version, were allowed:
In spite of the lightning fast turnaround time, I am still just as angry about this rejection than the last one since there was no prior warning (in program agreements or otherwise) that demo versions would not be allowed. It's hard to believe that Apple isn't aware that people are crying out for demos and trials; going as far as explicitly prohibiting them (while letting all other sorts of crap through) is nothing short of infuriating.
Both versions are fully functional. The one with ads actually has more functionality :-) [...] Nope. Themes are not functions. [...] We spent a fair amount of time negotiating these points with Apple. They want don't demos in the store. A good thing, IMHO.
Though his frustration at the SDK NDA (Non-Disclosure Agreement -- which among other things prevents developers from discussing App development even with each other) is pretty clear (warning: explicit language).
So, Apple is poised to revolutionize mobile applications with their iPhone SDK development and App Store deployment model, but (again!) their Kremlin-eque secrecy is causing headaches for developers and users alike. Is the influx of new Apps still drowning Apple's processing and support capabilities? Are they stretched too thin to whip up a developers-only discussion area, even in the secure developer.apple.com site? And even if both of those things are true, could they not have Scott Foretall, or even someone in PR, post something to let devs know Apple hears their pain points and will eventually, in some way, address them?
Or is this all just mountain out of molehill stuff, and the same types of growth problems any widespread launch of a new platform will encounter?
Are you a developer? A user? What do you think?