While many sites are reporting that the iPhone App Store has hit 10,000, MacRumors says it’s not quite there yet, but will be soon:
While several sites have reported that 10,000 iPhone Apps have been released into the App Store, the actual number of active iPhone apps that can be downloaded is about 9,676 as of today’s count. The discrepancy comes from the fact that many apps have been removed from the App Store for various reasons (trademark infringement, discontinued apps, pulled and released).
With approximately a quarter of those being games, and a tenth each for entertainment and utilities.
Want to get your App up as part of the next 10,000? Erica Sadun has some tips for you. What are they in brief?
Keep your icon consistent throughout the various sizes, don’t link to web sites you haven’t deployed yet, don’t ever include any mention of “beta”, and do not reference forbidden accessories (like a mic for the iPod Touch).
Check out the full article on App Store Lessons for much more by way of explanation and example.
A few days ago we mentioned Ars’ iPhone expert, Erica Sadun was taking the lifting of iPhone OS 2.2’s NDA as an opportunity to dump code and sift for gold. Turns out she’s not only found some in the way of “hidden” TV-out features in iPhone 2.2, she’s sacrificed her well earned turkey day to experiment with them. From her previous post, here’s what’s at work:
The MPTVOutWindow class allows your iPhone to send its video to a connected TV rather than to the built-in screen. Intended to be used with movies, the unpublished class creates a live video feed that is sent out through the iPhone’s connector port. End-users will need to buy a video adapter or cable to use this functionality.
Early days still, but fairly awesome stuff. Can’t wait to see what she and other developers — not to mention Apple eventually — come up with!
First up, with the previous rejection of Gmail client MailWrangler, Engadget says another app which also dares to “duplicate features” found in a Dock App (Apple’s own MobileMail) has actually been accepted into the App Store. Did BdEmailer slip through the cracks? Or is this a sign of inconsistency on Apple’s part? Hot on the heels of the controversy surrounding Google’s Advance Voice Search using non-public API’s, developer confidence in the approval process might drop even further…
…Though Ars’ own Erica Sadun reveals the story of one developer who, after initially having their App rejected by Apple, tried and tried again, and without making a single change to the app, had it approved the second time around. Embarrassing for Apple, if the policies really are that inconsistent.
Speaking of embarrassing, Wired reveals that one developer actually got Amazon’s mechanical turk involved in paying for reviews. Users who get $4 — $2 to “buy” the app, and $2 in bonus for leaving a 5-star review.
Lastly, Erica Sadun is back to remind us that, with the release of iPhone OS 2.2, the NDA is now lifted regarding that firmware, and the public dumping can begin! Any guesses as to what goodies will be found?
UPDATE: iPhone dev extraordinaire Erica Sadun investigated over at Ars and found the following: Google is both linking to Private Frameworks and using unpublished APIs. While the latter is likened to jaywalking, the former is apparently a ban-worthy offense. Yikes. Check out her complete investigation for more. And now that it’s public, the question shifts to what if anything Apple will do about it? Cave to Google over a killer feature and betray the confidence of other developers, or yank Google’s app, alienating a huge (if guilty) partner and likely creating another furor among users?
Original post:
Is Google using private (i.e., not publicly available via the official iPhone SDK) APIs to create the silky-smooth “raise the phone and talk” activation for their new Advanced Voice Search feature in the update Google Mobile App? That’s the latest question Daring Fireball’s been looking into, and here’s what they’ve found so far:
If you use something like the command-line strings utility to examine the UIKit framework, you can see that there’s an undocumented (and therefore private to Apple) method named proximityStateChanged. And if one were to strip the FairPlay DRM from the current Google Mobile application binary — which, of course, you wouldn’t do, because you’re not supposed to strip FairPlay DRM, but I’m just saying if one were to do this — a class dump of the application binary would show that Google Mobile does in fact implement proximityStateChanged.
DF posits three possible explinations: 1) No one at Apple noticed the private API usage, 2) Apple noticed but turned a blind-eye, or 3) Apple approved the use of a private API. Citing sources, DF claims #3 to not be the case, and perhaps that’s why Google promoted the feature so heavily, and stirred up interest so high Apple would feel pressure to approve it (though we wonder if Steve Jobs’ Apple ever feels that type of pressure?)
By contrast, DF states #1 is not without precedence, while #2 would be grossly unfair to other developers, and either way, users may suffer if Apple makes changes to their private APIs (which is one of the reasons to keep them private after all).
So what do you think? Which scenario is most likely? And what would you rather, that developers (Google or not) use officially unsupported features if it means better apps but also apps that might just break when the next firmware drops?
While I can’t claim to understand it, included in the update is aurioTouch and oalTouch for scilloscope and positional audio, Accessory and TouchCells which (apparently!) give greater options in tables and cells, and URLCache and Reflection which focus on Web-based data and image reflections respectively.
Says Sadun:
The iPhone Reference Library is an amazing resource for developers. It offers access to sample code, guides, and release notes. The new items I listed here augment Apple’s already rich iPhone sample code suite. Make a habit of stopping by the library page; Apple will often add new items there without announcement.
No sooner did Apple drop the iPhone SDK Non-Disclosure Agreement (fondly referred to as the [Redacted] NDA among aficionados, as it forbade developers discussing the topic even among themselves), then the floodgates of knowledge burst open. Cases in point:
According to TUAW, iPhone coder extraordinaire Erica Sadun’s The iPhone Developer’s Cookbook is already available in PDF form from informIT (along with code samples!):
If you’re getting started with iPhone programming, this book brings together tested, ready-to-use code for hundreds of the challenges you’re most likely to encounter. Use this fully documented, easy-to-customize code to get productive fast—and focus your time on the specifics of your application, not boilerplate tasks.
Meanwhile, Mike Clark writes in to let us know that Pragmatic Programmers is now offering a set of screencasts targeted specifically at iPhone developers:
There’s also a free (no account required) 20-minute “Getting Started with Xcode and Interface Builder” screencast [where Bill Dudney] shows you how to build the simplest of iPhone apps (a Hello World app). More important, he shows you how it works—from the main functions triggering Nib files being loaded, to wiring up interface controls, and all the way through a button push running code that you write.
For the last week or so I’ve been beta testing a well known iPhone application. Beta testing involves using the 100 iPhone “Ad Hoc” distribution method first outlined at WWDC 2008. I was planning on writing up the process, and my experiences being involved in it (all straightforward, all great — all definitely far more work for developers than testers) when, thankfully for all involved, one of the foremost iPhone devs, Craig Hockenberry of Twitteriffic fame, went and did it the way it should be done.
Interested in Ad Hoc distribution and how iPhone beta testing works? Get you to reading over at his site, Furbo.org.
Meanwhile, Erica Sadun over at TUAW presents a very well though out essay on how Apple could (and should?) improve the App review process with more objectivity, consistency, and transparency.
In [redacted] NDA land, John Gruber over at Daring Fireball offers an interesting theory, via a reader: what if it’s all about patent protection? Seems Apple might start the clock ticking when the NDA is lifted, and the technology gets published, and their lawyers may not have all the dots and crosses in place yet.
Finally, is it time to put BoxOffice on a milk carton yet?
No, not the 2.1 firmware beta, that one’s for realz. We’re talking here about the Washington Post, which ran a Techcrunch story breaking the news that:
Now we’re hearing from an app developer that Appleis finally going to start rolling out a new beta program in the next few days has released an Ad-Hoc program. Details are slim, but it seems like Apple is capping the total number of beta participants at 100 per app. In order to download a beta app, users will need to submit their iPhone’s UDIDs number to the developer,who will then need to flag its eligibility in the store itself. All betas will still be distributed through the App Store - you won’t be able to download one on an external site.The apps will be directly distributed by the developer.
Sound an awful lot like the Ad-Hoc distribution method Apple announced for educational institutions way back at WWDC to you? Sure did to iPhone developer extraordinaire Erica Sadun, who rumor smashed thusly:
The “Beta Program” will not be released in the “next few days.” Ad-hoc distribution is already available and working. Developers can create ad-hoc provisions through the iPhone Developer Program site today.
Sadun also provides a handy-dandy Ad-hoc Helper app for mailing your UDID directly to a developer, should you be part of an Ad-hoc app distribution group.
The App Store went live last week (what day exactly depends on whether you snuck in to iTunes 7.7 and snooped around on your own, or waited for the official links to surface), tying in to the iPhone 3G and 2.0 software launches. How’d it do? According to Steve Jobs:
“The App Store is a grand slam, with a staggering 10 million applications downloaded in just three days. Developers have created some extraordinary applications, and the App Store can wirelessly deliver them to every iPhone and iPod touch user instantly.”
Probably why Apple has finally started putting a dent in its backlog of developer acceptances, eh? But is all happy in App Land? Nope. Find out why after the break…
After a month of waiting, with no contact from Apple save form letters that went out to all developers, we’d grown quite frustrated. We don’t know if we should invest our time in a platform for which we may not even be allowed to release software. Finally on April 8th, one of our developers decided to apply to the program as an individual, to see what would happen. Shockingly, in under 24 hours he had a certificate which enabled him to work on actual hardware.
Kafasis thinks that Apple is handling individual applications separately from — and for some reason much faster than — company applications, which he finds confusing given the possible impact of large development houses and the only real (and critical) differentiator of the $99 program acceptance being the ability to tether and test actual hardware (rather than simulators) and, of course, the ability to sell through the App Store. Ultimately, he believes the problem lies in Apple’s communications — not only its lack of clarity, but its complete lacking (almost a trademark of the tight lipped company).
iPhone dev expert extraordinaire Erica Sadun follows up with some analysis of her own:
25000 applied; 4000 admitted. By any stretch of the calculator, thats only about a 16% acceptance rate. It’s one that has left many independent OS X developers behind.
Was Apple overwhelmed by the sheer volume of applications? Have they botched the program from the get go? And what could they do now to help get developers (and their developments) back on track?
The iPhone Blog merged with the Phone different site in May of 2008. Both sites were founded on a premise that comes one from one of Apple's old slogans: Think different. The iPhone Blog: for people who dare to phone different.
"
