Archive for the ‘state of the apps’ category

Apple Cracking Down on Mass Produced, Low Functionality Apps?

March 8th, 2010

app_store_church_lady

TechCrunch is reporting that companies who mass produce (or provide tools and templates for the mass production of) “cookie cutter” apps are hearing that they need to add differentiation and functionality or risk Apple not allowing them into the iTunes App Store. Jason Kincaid says:

Between the developers I spoke to, the consensus was this: Apple doesn’t appear to be opposed to ‘app generators’ and templates per se, but in the last month or so it has started cracking down on basic applications that are little more than RSS feeds or glorified business cards. In short, Apple doesn’t want people using native applications for things that a basic web app could accomplish. For some of these services that’s bad news, because that’s exactly the sort of application they produce; any new applications they submit are going to get rejected. But all hope isn’t lost for them, provided they can make their apps more useful.

Kincaid says Appmakr for one has taken suggestions from Apple to improve things like in-app purchases, instant notifications, offline access, and landscape viewing modes and describe the process as positive. Other services apparently haven’t had as much luck.

The move seems to be part of Apple’s ongoing efforts to increase the quality of the App Store experience and protect the brand. Much like the removal of sex-based apps last month, “cookie cutter” apps could seen as low value, sometimes verging on spam. For consumers it could result in a cleaner App Store and ultimately better apps (more than just re-packaged RSS feeds) but at the expense of quantity and choice. For developers, it’s likely another in a list of things they’ll consider before building on Apple’s platform.

If Apple is indeed working on revamping the mass produced app, what think you?

Apple Cracking Down on Mass Produced, Low Functionality Apps? is a story by TiPb. This feed is sponsored by The iPhone Blog Store.

TiPb - The #1 iPhone, iPad, and iPod touch Blog


UPDATED: Upgrade Pricing Finally Coming to App Store?

March 4th, 2010

itunes upgrade discount

UPDATE: Or not, as this dialog’s been around for a while as per 9to5Mac’s @llsethj. Sad now.

ORIGINAL: Developer Frasier Spears posted the above “curious” iTunes dialog to Twitter. It appeared when he hit “Update All”. We have no way of knowing exactly it means, but we’re hoping it means upgrade pricing is finally coming to the app store.

As background, one of the problems still facing developers has been the inability to offer paid upgrades. Either they had to give away new versions for free, or they had to create new apps with no way to discount the price to existing users.

That’s led some developers to slow down or stop making major improvements to their apps (since they can’t count on upgrade revenue), and it’s led to backlashes when releasing new versions as new apps.

In an ideal App Store, developers could choose to give existing users a discount when they upgraded.

UPDATED: Upgrade Pricing Finally Coming to App Store? is a story by TiPb. This feed is sponsored by The iPhone Blog Store.

TiPb - The #1 iPhone, iPad, and iPod touch Blog


Apple Removing Wi-Fi Scanning Apps from App Store

March 4th, 2010

wifi-where

Cult of Mac reports that Apple has begun removing apps from the iTunes App Store that scan for Wi-Fi access points. It looks like these apps are being removed due to their use of private APIs, which is prohibited by the iPhone SDK agreement. This would make it similar to the recent removal of apps that misused the iPhone camera DCIM folder to store and exchange documents.

There’s been some suggestion, however, that list reflects a policy change from Apple closer to the recent removal of sex-based apps.

Our speculation is that Apple has either added the Wi-Fi private APIs to their static analysis tool, or has just finally gotten around to checking for them. That would make it appear like a new policy when it’s actually the originally agreement finally being enforced.

Some developers believe long term lack of action by Apple equals tacit approval for private API use. Those beliefs likely have to start changing. When Apple makes an API public, they’re guaranteeing that developers can use them and have faith Apple won’t break them (and the apps built on them) in a future update. Private APIs are the opposite — Apple can and will change them at any point, breaking apps that try to use them when they shouldn’t. In some cases Apple is working on public versions of private APIs and will release them in future versions of the iPhone OS. In other cases they aren’t — sometimes for security, other times just for proprietary reasons.

In either case, this isn’t the first and likely won’t be last set of rejections. While we feel for developers, we feel more for users who may have come to depend on the functionality of these apps.

If you’re a developer who’s dealing with this and have a better take on the situation, please let us know!

[Thanks to everyone who sent this in!]

Apple Removing Wi-Fi Scanning Apps from App Store is a story by TiPb. This feed is sponsored by The iPhone Blog Store.

TiPb - The #1 iPhone, iPad, and iPod touch Blog


Apple Adding “Explicit” Category to App Store?

February 24th, 2010

explicit

Cult of Mac is reporting that Apple has added an “Explicit” category to iTunes Connect, the portal through which developers submit and manage their App Store apps. According to their developer source:

“It’s available for selection when adding a new app to iTunesConnect although I can’t see any sign of it in the actual App Store yet.”

MacRumors says they’ve confirmed the information, so where does this leave us now? Apple removed 5000 sex-based apps last week and stirred up a ton of reaction (cheers and jeers alike), only to come up with an organizational alternative a few days (and hundreds of blogs posts, thousands of tweets and comments) later? If it wasn’t a reconsideration, wouldn’t they have just added the category and reshuffled the apps without all the fuss and muss? Or did they want to force a re-submission to start the new category off with a clean slate?

Either way, hopefully this will include a better ratings implementation to go with it, so parental controls can turn off “explicit” apps without turning off apps that access the web along with them.

What think you?

Apple Adding “Explicit” Category to App Store? is a story by TiPb. This feed is sponsored by The iPhone Blog Store.

TiPb - The #1 iPhone, iPad, and iPod touch Blog


Closed vs. Open, Control vs. Chaos — What’s Best for Apple, the iPhone and iPad?

February 13th, 2010

apple_google_att_usual_suspects

Yesterday at Macworld two events helped clarify something I’ve been discussing with Dieter for a while now — Apple, the iPhone and iPad, and closed vs. open systems, control vs. chaos. These two events were a presentation by John Gruber of Daring Fireball concerning the 10 biggest problems faced by Apple, and a brief conversation with Leo Laporte of TWiT about Google Buzz.

As part of his Round Robin BlackBerry review, Dieter departed on a rant about BlackBerry Messenger (BBM) of epic proportions. A closed communications protocol, he argued, was untenable. BlackBerry users create incredible amounts of content in BBM (yes, chat is content) but it’s all completely closed off and owned by RIM. If you leave BlackBerry, you can’t take your BBM content with you. If RIM ever disappears, all your BBM content is lost. Something like Gmail on the other hand, works across platform and if you switch from BlackBerry to iPhone to Android, you enter your Gmail account and everything is there. Since you can access it via standard protocols like POP and IMAP, you can also make local copies and upload them to a different service (i.e. upload your mail to a non-Google IMAP folder).

Laporte made a similar comment about Twitter and Facebook. If either Twitter or Facebook were to fail, all your status updates, all your wall posts, all your friends and those you follow and/or follow you would be gone.

I don’t know if Google Buzz will prove to be an open protocol and system for sharing status, location, and relationships, and certainly it’s implementation shows signs of the typical Google “release now, fix later, polish never” model, but something needs to.

And this brings me rather circuitously back to Apple and the iPhone. As much as a certain segment decries Apple as “closed”, in terms of protocols they’re remarkably open. They use IMAP for mail, and open-sourced CalDAV and CardDAV for calendaring and contacts. They use WebDAV for web directories and WebKit for Safari. iChat supports most IM protocols, including Jabber. They use BSD Linux and the Darwin kernel for the core of Mac and iPhone.

Apple is generally built on top of open technologies, and one of their core strengths is melding that open architecture with tightly controlled (i.e. proprietary) user interface layers (and developer APIs, and App Store review processes).

For some, that last part is an absolute deal breaker. But they have Ubantu and Open Moko. (Yes, even Android is closed — you can’t muck about with Gmail or Google Maps apps). For mainstream users, however, the front end, the user experience, “just works” to the point where it’s become a cliche.

I said it previously in my Round Robin summation, to use Google you must give up privacy, to use Apple you must give up control. (I don’t even want to think about what I’m giving up to use Google on Apple!)

So proprietary interfaces to open technologies — how does that work for us? What happens when we use something not controlled by Apple?

John Gruber suggested AT&T as an example. Indeed, he listed it a one of Apple’s problems. Now, some people get great AT&T service while others have connection problems that have become near-legendary. Either way, it’s hurt media and mainstream perceptions about the iPhone.

Gruber also mentioned Big Media (movie and TV studios, music labels) as a problem. They want to charge more than the market will bear (certainly enough to make free-as-in-torrent an alternative) and make less available via iTunes than via a retro 1980s corner video store.

Is it a coincidence that some of the main aspects of the iPhone and iTunes that Apple has absolutely no control over are some that cause the greatest amount of user frustration?

(The App Store and its review process mostly create developer frustration, and Gruber listed this as a problem as well, though one that’s slightly improving since the holiday shut-down).

So, we come back to and down to Apple liking to control the user-facing aspects of the iPhone (and iPod touch, and soon, iPad) but using and promoting open standards for a lot of the technology underneath. While this approach might clash philosophically with some users (and again, Android, Palm, etc. aren’t open, they’re just more open) and practically for others (power users who want the control themselves), its proved remarkably effective for casual, mainstream users, and for power-users willing to give up some control for a better experience.

Except for that part about AT&T and Hollywood, but then those are controlled with little concern for user experience…

Closed vs. Open, Control vs. Chaos — What’s Best for Apple, the iPhone and iPad? is a story by TiPb. This feed is sponsored by The iPhone Blog Store.

TiPb - The #1 iPhone, iPad, and iPod touch Blog


Apple to iPhone Developers: So… Happy with the App Store?

February 9th, 2010

Apple dev survey

TechCrunch is reporting that Apple has started sending developers invitations to take a satisfaction survey with regards to the App Store in general, and the App Store approval process in specific.

Apple asks you to answer with: “Very dissatisfied,” “Somewhat dissatisfied,” “Neither satisfied nor dissatisfied,” “Somewhat satisfied,” “Very satisfied,” or “Don’t know.”

They also ask, “What one thing could Apple do to make the iPhone Developer Program better?” and give you a text box to write anything you want. A few months ago they certainly would have gotten some interesting responses there.

Indeed and as we suspected, “wait for developers and bloggers to get really ticked off and then have Phil Schiller email them” wasn’t a scalable solution. TechCrunch speculates that the improvements in the App Store approval process starting 2010 involve more and better trained staff, since approval speed has improved and reportedly even communications between Apple and developers is better.

So, if you’re a developer, what will you be telling Apple? And if you’re not a developer, does it matter to you that Apple is trying to improve their developer relations?

Apple to iPhone Developers: So… Happy with the App Store? is a story by TiPb. This feed is sponsored by The iPhone Blog Store.

TiPb - The #1 iPhone, iPad, and iPod touch Blog


UPDATE: Apple has Stanza App Remove DCIM Work-around for USB Sharing

February 2nd, 2010

stanza

UPDATE: PatternMusic reveals that the issue is (mis)use of the DCIM folder (digital camera image folder — where your camera roll pictures are stored) to transfer non-image related files.

Apple, however, precludes apps from reading or writing data files to any other place except the app’s “sandbox” document folder through their developer agreement.

ORIGINAL: TechCrunch reports that the latest update to the Amazon-owned Stanza eBook reader [Free - iTunes link], version 2.1, removed USB sharing as demanded by Apple’s iTunes App Store:

Just for your reference: the feature enabled users to transfer books in the ePub or eReader format to their mobile devices using a USB cable.

I’m sure Apple has good reasons to prevent people from being able to transfer files to iPhone and iPod Touch devices using a USB cable, and I believe this isn’t the first time they’ve asked developers of apps with this or similar features to remove them for new users. That said, I’m not 100% certain which rules were broken here, and since Apple requested Lexcycle not to discuss specifics we’re left guessing why Cupertino had an issue with the USB syncing features.

Existing Stanza owners who want to keep the feature should, of course, ignore the update. Give us your take in the comments!

(Thanks to Fassy for the tip!)

This is a story by the iPhone Blog. This feed is sponsored by The iPhone Blog Store.

UPDATE: Apple has Stanza App Remove DCIM Work-around for USB Sharing


iPhone App Store Economy Even More Massive Than This Visualization

January 13th, 2010

go-app-store-r7

Think this GigaOm visual representation of the iPhone and iPod touch App Store Economy is massive? Check out that economy itself. (And we’re guessing there are far more devices on the market now, given how 50 million was nearly 2 quarters ago).

This is a story by the iPhone Blog. This feed is sponsored by The iPhone Blog Store.

iPhone App Store Economy Even More Massive Than This Visualization


Apple’s App Approval Process Getting Speedy

January 12th, 2010

jobs_speaks_app_store

TUAW recently remarked that the App Store approval process seemed to be working much faster lately. TiPb has been in contact with numerous application developers and the general overall feel we are getting is the same — Apple is finally coming around when it comes to the app approval process. Much has been said about Apple and their App Store over the past few years but things have seemingly changed for the better.

TiPb sometimes gets access to beta applications for feedback or review anywhere from a month to a week in advance. Generally we’ve seen the same 2 week delay Apple advises before the apps show up in the App Store (though sometimes it’s been up to 4 weeks or more in the past). Lately we have received an app only to find it released only a day later, sometimes hours later depending on the app itself.

What has brought about this speed boost we have no idea but we welcome it regardless and hope it continues.

[Thanks to Chris for the link!]

This is a story by the iPhone Blog. This feed is sponsored by The iPhone Blog Store.

Apple’s App Approval Process Getting Speedy


Apple’s iPhone App Store Passes 3 Billion Downloads

January 5th, 2010

appstore-hero-20090608

Apple has announced they have surpassed the 3 billion download mark within their App Store. Somewhere in Cupertino Steve Jobs must have a huge smile on his face as it was just this past September where downloads reached 2 billion:

“Three billion applications downloaded in less than 18 months—this is like nothing we’ve ever seen before,” said Steve Jobs, Apple’s CEO. “The revolutionary App Store offers iPhone and iPod touch users an experience unlike anything else available on other mobile devices, and we see no signs of the competition catching up anytime soon.”

So let’s stop and think about this, iPhone and iPod touch users in 77 countries downloaded one billion applications within a 4 month period. That’s pretty impressive and with no signs of slowing, it’s a safe bet Jobs is right about the competition.

This is a story by the iPhone Blog. This feed is sponsored by The iPhone Blog Store.

Apple’s iPhone App Store Passes 3 Billion Downloads


Tapulous Making $1 Million a Month in App Store, Even Apple Didn’t Expect App Store Success

December 21st, 2009

jobs_speaks_app_store

Making our collective jaws drop today is Tapulous, who are claiming sales approaching $1,000,000 (that’s on million) dollars a month, and news that even those inside and around Apple had no conception of just how successful the iPhone app ecosystem would be.

First, Reuters reports that Tap Tap Revenge maker Tapulous, a 20-person iPhone development team, has seen 20 million installs and 600 millions games played, adding up to sales approaching $1 million a month.

Tapulous’ chief executive said he expects it to ride a wave of exponential growth in mobile app commerce in the next two years, similar to that seen recently by social gaming companies like Zynga, Playfish and Playdom. Playfish was recently acquired by Electronic Arts for $275 million in cash.

Second, the Financial Times reports that even insiders weren’t expecting this level of success. Says Kleiner Perkins partner Matt Murphy, manager of the then $100m iFund announced alongside the original iPhone SDK:

“We had no idea there would be 2bn downloads by October. Most people within Apple, if you had told them it would be a fifth of that by now, they would have been pretty happy.”

Part of this is attributed to Steve Jobs, of course:

Even more important was Mr Jobs’ willingness to demand that AT&T and other network carriers give up control over what sorts of programmes could operate over their airwaves. He argued that the iPhone was a computer, not a phone, and that consumers expected to be able to do many things with computers. History had shown that this kind of freedom was what drove the more profitable “ecosystems” of computers – where sales of hardware were dependent on a wide variety of useable software.

So, remove the carriers, treat smartphones like real, mobile computing platforms, and everyone (mostly) benefits? Who could have imagined that?

This is a story by the iPhone Blog. This feed is sponsored by The iPhone Blog Store.

Tapulous Making $1 Million a Month in App Store, Even Apple Didn’t Expect App Store Success


App Store Bugs: App Updates Downloading Over and Over and Over Again

December 13th, 2009

App Store repeat download bug

There appears to be a bug on Apple’s iTunes App Store that’s causing apps to show up as having updates available even after they’ve been downloaded over and over again. We’ve gotten quiet a few readers writing in about it now, and there’s the usual huge thread up on Apple’s discussion boards.

Here’s what it looks like — the App Store on your iPhone, iPod touch, or iTunes on your PC tells you you have an update for an app. You tap or click to update, enter your iTunes password, and the app downloads — but it still shows the app in the update list. You tap or click update again, it downloads again, but again still shows the app in the update list. Or worse (as happened to me a few weeks ago), iTunes pops up a Checking for Available Downloads dialog then proceeds to try, over and over again, for days, to download 1.3GB of turn-by-turn navigation app update.

Of course, the problem seems intermittent and random — different users experiencing the it with different apps at different times. It’s also unclear if everyone is having the same problem. For some, Apple’s iTunes app servers may not be properly providing the updated app file and so the new version is not successfully getting installed on the device. For others, the file might be getting installed but iTunes doesn’t recognize or register it so keeps offering the same update.

Possible solutions include rebooting your iPhone or restarting iTunes on your PC, or just waiting and trying again in a day or so. On rare occasions it looks like it takes a few days to sort itself out, which for small apps isn’t a show-stopper for those 1GB apps (or large games), it can be untenable, especially for people in countries with tight data caps on their home internet.

Some developers are hearing enough feedback on this that they’re contacting Apple in hopes of some server-side fixing (see image of Twitter conversation above). We’re hoping for some as well.

If you’re having this problem, let us know in the comments, and let us know what (if anything) is fixing it for you.

This is a story by the iPhone Blog. This feed is sponsored by The iPhone Blog Store.

App Store Bugs: App Updates Downloading Over and Over and Over Again


Apple Updates App Store — Less Words, More Screenshots

December 12th, 2009

Screen shot 2009-12-11 at 9.18.01 PM

Apple has begun rolling out an update to the way the iTunes (on Windows or Mac) shows the App Store, including fewer words and more screenshots. Rather than the lengthy app descriptions of old, iTunes now shows only the first two lines, with a “more…” tag that needs to be clicked to reveal the rest (time to tighten up that text, developers!). Instead of one screenshot at a time, iTunes also now shows a series of scrollable screenshots, similar to how the on-device App Store began showing them with iPhone 3.0.

iTunes 9 gave media a makeover, so it’s nice to see Apps get the same treatment. iTunes 9, also like iPhone iTunes and App Store, transitioned to WebKit and HTML, CSS, and JavaScript for the UI. So, Apple can update it at any time without needed to provide a new version for users to download. This is exactly the reason they’re promoting WebKit UI for apps in general (when and where they make sense) during their Tech Talk World Tour.

Again, it’s rolling out, so a lot of apps still show the old pages. If you can find the new look, however, let us know what you think. Better for buyers? How about developers?

(via TechCrunch)

This is a story by the iPhone Blog. This feed is sponsored by The iPhone Blog Store.

Apple Updates App Store — Less Words, More Screenshots


Notes from Apple’s iPhone Tech Talk World Tour

December 8th, 2009

tech_talks09_iphone

TiPb had a chance to talk to some developers who attended Apple’s recent iPhone Tech Talk World Tour (San Jose, Seattle, New York, Toronto, Paris, London, Hamburg, Bejing, and Tokyo), where they promised expert advice at cities near developers. So how has it gone? The T-Shirt’s given away say it all they “came, saw, and coded”.

There were different tracks for developers to choose from, and one of the complaints we heard was that the devs wished it had been longer so they could have attended them all. Still, we have some notes they were willing to share, after the break!

(And if you think this is just for geeks… well it is, but it explains some of why the iPhone does what it does, and what developers could do to ease some of our frustrations).

WebKit

  • One dev who was new to Apple technologies found WebKit and their specific CSS (-webkit-gradient, -webkit-mask, webkit-box-reflect) to be “astoundingly powerful”. (If you run WebKit or Safari, check out the http://westciv.tools.gradients demo.
  • Apple stressed the advantages of using WebKit and embedded WebView. The AppStore app is an example of a native app with a WebKit UI made by Apple.
  • A button made in CSS is much lighter than an image file and also scales elegantly (resolution independent).
  • Even a JPG that’s only 50k in size will take up 10 times more memory when it’s decompressed and rendered in a UI.
  • WebKit interfaces can be updated outside of the App Store approval process, so no resubmission just to change UI elements.
  • Client-side database storage API in HTML 5 saves state locally and reloads the next time you view the page. (Again, http://webkit.org/demos/sticky-notes/ demo.)

App Performance

  • Apple believes every developer should be obsessed about performance.
  • For the end user experience, every fraction of a second is important. They want to load and go, not invest time in waiting for an app to load.
  • iPhone uses 12MB for graphics, 32MB for kernel, 12MB for daemons, 4MB for phone, so for iPhone 2G and 3G, half the memory is gone before any 3rd party app even loads.
  • There’s no swap file, so the size of binaries matter since they’ll be loaded into memory.
  • When a low-memory situation occurs, there’s a warning. On second warning, background apps are killed, on third warning (95%), front-facing app is killed. (Think Safari disappearing and getting dumped back onto the home screen).
  • Apple stressed that developers need to handle these warnings elegantly and free up memory as/when appropriate.
  • A user should never be warned about memory or asked what to do (hello AnDROID!).
  • Where a developer stores cache is important. If a developer stores cache in a location that iTunes backs up, it creates slow iTunes backups for users. They should cache in temporary areas instead.
  • The iPhone uses a single core processor, but can handle multiple threads. In the future these devices may be multi-core so starting now and building them for that future is a good idea.
  • Apple believes that great apps come from developers who pay attention to details beyond just what’s necessary to get the job done.

What About Those Rejections?

  • The most common reason for a rejection, according to Apple, was when an app crashed on launch.
  • Developers tended to know that if an API was private, they shouldn’t try to make an app that depended on it since it would likely get rejected.
  • No specific rejections were brought up or addressed.
  • One dev we spoke to liked the App Store and Apple as “gatekeeper” because it created greater end-user trust — people were more likely to trust that App Store apps would work and not mess up their phone or do anything criminal.
  • Another dev, when asked about iPhone development vs. another platform, liked that Apple handled all the transactions and getting all the apps in front of all the users, which would be a huge chore and expense otherwise.
  • Yet another dev just thought the size and reach of the App Store made it the best place to develop at the moment.

All in all it sounds like developers enjoyed the free event, and the free coffee, pastry, and t-shirts. Hopefully Apple will continue to provide them next year, and going forward.

If you attended an iPhone Tech Talk World Tour session and have any additional notes for us, please send them our way!

UPDATE: Stephen Rayner Jr. let us know he’s putting his lengthy, detailed notes from the Toronto Tech Talk online via blog.nuthatch.com.

This is a story by the iPhone Blog. This feed is sponsored by The iPhone Blog Store.

Notes from Apple’s iPhone Tech Talk World Tour


New York Times Gives Sweet Front-Page Love to iPhone App Store

December 7th, 2009

appstore-hero-20090608

The New York Times had a huge, gushing, front-page-of-the-business-section story this weekend about the iPhone App Store titled Apple’s Game Changer, Downloading Now.

Now the App Store, with over 100,000 apps and 2 billion downloads is a runaway success, no doubt about it, but given the continued problems with developer relations and capricious approval processes, seeing Apple Senior VP of Marketing Phil Schiller, and VP of iTunes Eddy Cue, attack public relations via the New York Times, and not help restore faith the developers via a come-to-jesus-phone open and honest airing of grievances and non-opaque plans for improvement just comes off as… awkward (and perhaps a tad insulting). And the New York Times — really? If you don’t have the guts to go for the story and ask the tough questions of Apple, who’s left?

Anyway, here’s what we did get from the Apple brass:

There’s a 24″ (20 LED screen) display in the lobby of 1 Infinite Loop displaying 20,000 top-selling app icons, and each time one is bought, its icon jiggles and ripples the adjacent icons. Yeah, that’s pretty cool.

First up, Schiller says the review process is a necessary evil to ensure customers trust that apps won’t crash their iPhones, steal their data, or contain illegal content, and that most apps just sail through the process. They received 10,000 apps a week.

“I absolutely think this is the future of great software development and distribution. The idea that anyone, all the way from an individual to a large company, can create software that is innovative and be carried around in a customer’s pocket is just exploding. It’s a breakthrough, and that is the future, and every software developer sees it.”

“I think, by and large, we do a very good job there. Sometimes we make a judgment call both ways, that people give us feedback on, either rejecting something that perhaps on second consideration shouldn’t be, or accepting something that on second consideration shouldn’t be.”

“We care deeply about the feedback, both good and bad,” he says. “While there are some complaints, they are just a small fraction of what happens in the process.”

“Our goal is very simple: We want to have the best platform for applications that there has ever been on any product. We know we’re not perfect, but we know we’re better than anything else that has been and we want to keep improving it.”

Apple is typically considered to be a perfectionist when it comes to aesthetic and experience, however, so a “good enough” argument is hard to process — that small fraction should be keeping Steve Jobs up at night.

The Times does mention the controversies and offers some developer comments about apps almost a year in limbo, and large gaming companies being treated the same as hobbyists. They also cover the jailbreak alternative. When it comes to Cue, however, we get:

“A rocket ship is even too small of an analogy. We’ve been able to leverage a lot of our iTunes technology for the App Store. But it’s completely different. We’re reviewing all of those apps. We really don’t have to review each and every song.”

Apple told the Times they’re “trying” (?) to increase the number of reviewers and streamline the process.

Check out the full article, which also features RIM/BlackBerry, Palm, Microsoft, and Google’s take on the App Store and apps in general. And let us know what you think!

This is a story by the iPhone Blog. This feed is sponsored by The iPhone Blog Store.

New York Times Gives Sweet Front-Page Love to iPhone App Store


iPhone APInsanity: Unity Updates to Avoid Rejections, Compatibility Causing False Positive Dejection

December 1st, 2009

app_store_church_lady

9to5Mac brings word of Unity’s latest update:

Unity iPhone 1.5.1 includes improved XCode support and improved AssetBundle support, but more importantly Native APIs (NSGetEnviron and exc_server functions) have been removed to comply with new Apple requirements.

“The main reason for this is to avoid problems with applications breaking when Apple releases new versions of the iPhone OS,” the company explains.

In case you hadn’t been following the story, Apple is using a new static analysis tool to find and reject apps using private APIs, and in so doing flagged a bunch of them caused by some calls inside the Unity game development engine (and the Three20 framework, perhaps among others).

On the flip side, it’s possible the same static analysis tool is also generating false positives when it comes to apps using Apple’s own recommended backward compatibility guidelines.

According to Apple’s Dev Center:

By using “weak linking” in your Xcode project, you can include frameworks you’ll need for the newer features, and check for API availability when your application is running. This technique provides you with the broadest possible audience for your application.

Yet developer Juicy Bits Software speculates that:

we’ve been bitten yet again by the static analysis tool. 3D Camera Lite runs on iPhone OS 3.0 or later, and we check the OS version before calling any of the new 3.1 APIs…

So, basically, Apple’s not acknowledging the OS check, and rejecting based on 3.1 APIs being used for apps that run on earlier versions of the iPhone OS that don’t include those APIs as public.

If correct, that’s certainly “frustrating” as they put it, and yet another sore point Apple will need to address and quickly.

[Thanks to Jordan for the Juicy Bits tip!]

This is a story by the iPhone Blog. This feed is sponsored by The iPhone Blog Store.

iPhone APInsanity: Unity Updates to Avoid Rejections, Compatibility Causing False Positive Dejection


iTunes App Store “Release Date” Sorting Sorta Broken?

November 24th, 2009

app_store_date_broken

Swing by the iTunes App Store, pick a category, and get/go to the Sort by: Release Date listing and it may look like Apple hasn’t added any new iPhone and iPod touch apps since November 19 — only they have, and it’s just the iTunes listings that are broken.

Rewind: We started getting questions from users who thought no new apps were being released, or that Apple had somehow frozen the App Store. Then we got reports from developers saying their apps weren’t showing up in the release date listings even though they’d been approved and put into the store. Finally, we got reports of the release date listings being flat out busted, and that’s what looks to be the case.

What does this mean? For users looking to find new apps in iTunes, good luck with that. Absent sort by release date, you’ll have to hit up third party tracking sites like AppShopper until Apple fixes the App Store proper. For developers who were hoping for the brief spotlight that listing provides for those users, well you’re out some primo free marketing. And for many, that’s going to hurt.

So, to sum up, yes Apple is still posting new apps, but no they’re not updating the release date lists, and yes this sucks for both user discovery and developer exposure.

[Thanks to everyone who sent this in -- in all forms!]

This is a story by the iPhone Blog. This feed is sponsored by The iPhone Blog Store.

iTunes App Store “Release Date” Sorting Sorta Broken?


UPDATED: Phil Schiller Addresses App Store — Not to Developers but to BusinessWeek

November 23rd, 2009

schiller time

UPDATE: As expected, Rogue Ameoba’s Airfoil Touch has been approved, with the original graphics displayed from Mac OS X. Meanwhile, Gx5 tells us it took over a year to get their one-touch search portal app, iClueless approved following a string of time-consuming (given Apple’s process) rejections. Again we wonder if having a “big voice” makes a big difference?

ORIGINAL: Apple Senior VP of Marketing, Phil Schiller, has once again stepped forward to address growing concerns about the iTunes App Store approval process — but this time he’s avoided developers and their complaints about opacity and inconsistency, and instead gone to BusinessWeek to get ahead of the story going mainstream.

Let’s think about this for a moment. Schiller’s previous, highly publicized comments have been emails addressed to bloggers and Mac developers, and wrung truthy enough to give a tiny glimmer of hope to those who just assumed Apple’s upper management was oblivious to the problems around rejected apps. These comments read more like spin; like instead of fixing the App Store, they’re worried concerns are spreading beyond developers and the blogsphere, and instead of earnestly working even harder to fix them, they just want to minimize and marginalize the complaints in the minds of the general press and public, who might be hearing about it for the first time following Facebook developer Joe Hewitt’s high-profile exodus from the App Store.

The problem is, Apple has historically proven they’re terrible at handling bad PR. From the original iPhone price cut to MobileMe’s disastrous launch to Steve Jobs’ health to everything involving the App Store approval process to date, they come off as wrong-headed and out of touch until it seems almost too late. Case in point, Schiller’s comments to BusinessWeek today, where he cites 90% of rejections being related to technical bugs in the app (and contends developers are happy about the “safety net” Apple QA provides). 1% which fall into gray areas Apple hadn’t previously considered (example given, apps that help cheat at Casino gambling), and an undisclosed amount that violate trademarks or copyrights:

  • “We’ve built a store for the most part that people can trust. You and your family and friends can download applications from the store, and for the most part they do what you’d expect, and they get onto your phone, and you get billed appropriately, and it all just works.”
  • “Whatever your favorite retailer is, of course they care about the quality of products they offer. We review the applications to make sure they work as the customers expect them to work when they download them.”
  • “There have been applications submitted for approval that will steal personal data, or which are intended to help the user break the law, or which contain inappropriate content.”
  • “We had to go study state and international laws about what’s legal and what isn’t, and what legal exposure that creates for Apple or the customer.”
  • “We’ve had a lot of eyes on us. We’ve had inquiries from governments and political leaders asking us what we were doing to protect children from inappropriate content,”
  • “If you don’t defend your trademarks, in the end you end up not owning them. And sometimes other companies come to us saying they’ve seen their trademarks used in apps without permission. We see that a lot.”

Rogue Ameoba’s Airfoil Touch rejection is used in the article, and Schiller responds in the abstract:

  • “We need to delineate something that might confuse the customer and be an inappropriate use of a trademark from something that’s just referring to a product for the sake of compatibility. We’re trying to learn and expand the rules to make it fair for everyone.”

Apparently it will work out, however, as Airfoil Touch is being re-submitted with the original Mac OS X-pushed artwork restored. And some of Schiller’s points are fair enough, we suppose, they’re just addressing the wrong forum, and overall (still) avoiding the real problem. And no, it’s not Apple being a “gatekeeper”.

If Apple wants to run a boutique instead of a flea market, good for them — the market will decide if end-users ultimately prefer that to the webOS, Android, BlackBerry, Windows Mobile, Symbian, and WebApp alternatives. Just stop being a bad “gatekeeper*. Talk to your developers. Get a dedicated developer point man like Palm has. Take questions about the App Store (especially at WWDC). Spend less time with BusinessWeek and more talking to the great developers, so end users get those great apps. B’okay?

This is a story by the iPhone Blog. This feed is sponsored by The iPhone Blog Store.

UPDATED: Phil Schiller Addresses App Store — Not to Developers but to BusinessWeek


Gameloft: 13% of Revenue from iPhone, Nobody Making Money on Android

November 21st, 2009

iphone_vs_android_kill_switch

Gameloft — and other developers according to Gameloft — are cutting back on development for Google’s Android platform due to the “weakness” of the Android Market. According to Reuters, Gameloft finance director Alexandre de Rochefort said:

We have significantly cut our investment in Android platform, just like … many others. [The Android Market] is not as neatly done as on the iPhone. Google has not been very good to entice customers to actually buy products. On Android nobody is making significant revenue.”

Ouch. Harsh words. Meanwhile, with iPhone generating 13% of Gameloft’s revenue (400 times more than Android), we’ll no doubt see plenty more on the iTunes App Store.

While we’ve heard developers and pundits talk about the business advantage of the iPhone before, and while Android’s numbers may be rising and soon, in the short term the bigger houses like Gameloft might just stick with where the money is.

[Thanks to the Reptile for the tip!]

This is a story by the iPhone Blog. This feed is sponsored by The iPhone Blog Store.

Gameloft: 13% of Revenue from iPhone, Nobody Making Money on Android


Three20 Framework and More on App Store Screening for Private APIs

November 20th, 2009

app_store_church_lady

A little while ago we posted about Apple’s new use of a static analysis tool to find private API calls and reject the apps that make them. Rather than Storm8 or Unity this time, however, it’s former Facebook developer Joe Hewitt’s pioneering Three20 framework that’s getting caught.

Daring Fireball has some details:

One popular open source framework, Joe Hewitt’s Three20 (linked here on DF back in March), played a bit fast and loose with private APIs, and so now there are numerous developers with apps getting flagged for private API calls made from the Three20 framework. This Google Groups thread [link] covers the problem and the work that’s being done to create a branch of Three20 that’s free of private API calls.

Gruber also links to RogueSheep, whose Postage app has gotten caught via Three20, and has some suggestions to help them help Apple help them avoid getting rejected for unintended private API calls in the future:

Making the static analysis tool available to developers would indeed be helpful. But I suspect it wouldn’t work in terms of game theory. Honest developers could make good use of having access to the tool, to help ensure their projects are free of private API violations. But dishonest developers would use the tool to figure out ways to slip private API calls past the checker. Parrish’s second request, for Apple to run the tool against submissions far sooner in the review process, strikes me as a good and reasonable one.

Us as well.

This is a story by the iPhone Blog. This feed is sponsored by The iPhone Blog Store.

Three20 Framework and More on App Store Screening for Private APIs


More on the iPhone (and iPod touch) Development Advantage

November 18th, 2009

jobs_speaks_app_store

Instapaper and Tumblr developer Marco Arment riffs on the NYT’s article on Palm webOS’ trouble wooing developers, and it’s predictably good stuff.

His major point is that with its huge install base (which topped 50 million iPhones and iPod touches months ago), it makes more financial sense to develop for Apple’s platform, rather than Google’s Android or Palm’s webOS which might have on 5% to 10% as many devices on the market.

Giving developers an app store is the easy part. The hard part is bringing us enough customers. The iPhone is so good that it built up a huge installed base without any third-party apps, but no Android or webOS devices can say that yet.

Arment points out that the iPod touch makes a huge difference as well, giving developers a similar device to work on without the need for an expensive cell phone contract. He also echoes Fake Steve’s comments on different hardware complicating development, though he thinks if Android popularity continues to grow, the platform might justify the investment one day.

This is a story by the iPhone Blog. This feed is sponsored by The iPhone Blog Store.

More on the iPhone (and iPod touch) Development Advantage


Fake Steve on Android Fragmentation, i.e. Why It’s Harder to Develop for than iPhone

November 17th, 2009

fake_steve_retires

Is the Android Marketplace a more open alternative for developers compared to the iPhone App Store, or does the growing diversity of hardware, software, and overlays make it just as frustrating in its own way? Okay, so Fake Steve is likely to be more pro-Apple than a Fake Eric would be, fair enough. And, yes, some high-profile developers have taken issue with Apple’s draconian incompetent App Store approval process, well taken. But as much as Fake Steve is funny, the real Dan Lyons (of Newsweek) behind him is an equal opportunity offender, happy to take the p*ss out of Apple at any opportunity, often anti-Linux, and just as often insightful when it comes to things like Old Media and, yes, competing platforms. So take this with a giant-sized fake grain of salt, but take it:

There are just a bunch of different devices that have a lot in common with each other but aren’t quite the same. Trying to turn that into a “platform” is like trying to build a porch using three hundred pieces of wood, none of which are the same size. From the [Gadget Labs] story:

A slew of problems have made managing Android apps a “nightmare,” they say, including three versions of the OS (Android 1.5, 1.6 and 2.0), custom firmware on many phones, and hardware differences between different models.

Dear friends, this is only going to get worse, not better. Think about it. Every handset maker wants its device to be different. And special. So they intentionally tweak the OS to give themselves what they think of as an “advantage,” when really it’s nothing of the sort, because all it does is prevent ISVs from writing apps for them. Even if the handset makers weren’t totally short-sighted and evil, there’s the competency issue.

No doubt Apple’s App Store can make developers tear their flesh off in frustration, and GPS/CPU/GPU/Camera/etc. issues fragment the iPhone/iPod platform as well, but at the end of the day, does 50+ million “compatible enough” iDevices that are gate-keeper’ed still offer developers a better experience than a wide range of quasi-competitive, free’er devices?

(Yes, Google is closed as well, just not as closed…)

This is a story by the iPhone Blog. This feed is sponsored by The iPhone Blog Store.

Fake Steve on Android Fragmentation, i.e. Why It’s Harder to Develop for than iPhone


After 3 Months, 3 Rejections, Airfoil Speakers Touch Ships, Developers Leave iPhone

November 13th, 2009

Airfoil Speaker Touch 1.0

After submitting a minor .1 bug fix for Airfoil Speakers Touch 1.0.1 [Free - iTunes link] for iPhone and iPod touch, longtime Mac developers Rogue Amoeba waited for what they assumed would be a routine App Store review. Three and a half months, three rejections, and the unsuccessful intervention of a champion at Apple, the app is finally in the store, but the developer has decided the process is too odorous to continue with the iPhone platform.

Don’t stop us just because you’ve heard this before over and over again.

The issue this time was Rogue Amoeba discovering the type of Mac and exact application that was being used as audio source, and displaying the corresponding Mac OS X-provided image of the machine and icon for the app.

Though standard — intended — behavior on the Mac, Apple’s App Store policy branded this a trademark violation and they requested it be changed. Rogue Amoeba assumed the request was erroneous and tried resubmitting, tried escalating via email, even had a champion inside Apple try help get it through. In the end, the App Store policy was an immovable object, and Rogue Amoeba had to remove the Mac and app icon images. Airfoil Speakers Touch 1.0.1 was then approved and placed in the app store.

(And during the whole process, Airfoil Speakers Touch 1.0, buggy as it was, and using the exact same artwork Apple had issue with in 1.0.1 was left untouched in the App Store for users to download and use).

In the future, we hope that developers will be allowed to ship software without needing Apple’s approval at all, the same way we do on Mac OS X. We hope the App Store will get better, review times will be shorter, reviews will be more intelligent, and that we can all focus on making great software. Right now, however, the platform is a mess.

The chorus of disenchanted developers is growing and we’re adding our voices as well. Rogue Amoeba no longer has any plans for additional iPhone applications, and updates to our existing iPhone applications will likely be rare. The iPhone platform had great promise, but that promise is not enough, so we’re focusing on the Mac.

Add our voice to the chorus: fix. this. More after the break…

While many of these developers point to Apple acting as App Store gatekeeper as the issue, we’d submit right now the actual issue is Apple continuing to act as a capricious, illogical, unpredictable, often stupefying gatekeeper.

Curating a store is just a business model. It may well cost them developers philosophically opposed to the idea, even incredibly talented ones like Facebook’s Joe Hewitt, but every decision has an opportunity cost. Choosing to curate a store, even one growing so fast it has 2 billion downloads and 100,000 apps, and continuing to suffer from poor communications, overzealous legal oversight, unclear guidelines, and the crap shoot that seems ultimately at the core of any given app getting approved on any given day… it just doesn’t work.

Getting rid of the gatekeeper might treat the symptom but is it the cure? Apple legal could just as easily issue a DMCA demand notice for an app using artwork they felt was a trademark violation, and have it taken down — even under Google’s more open, publish-first, investigate-if-flagged App Market system. The problem is Apple shouldn’t think using that artwork is a problem on the iPhone if it isn’t on the Mac. That, and the dozens of other so-obvious-it-hurts-our-brains-issues, are what needs to be fixed, and what are driving developers to question the platform.

Like Palm, Apple could allow developers to skip review entirely, leave them off the storefront, but give them a direct download link to market and distribute on their own. That wouldn’t fix this issue. They could extend Ad-Hoc to infinity so there’d be no update notification or over-the-air (re)downloads, but developers could make binaries available themselves and users could drag and drop them into iTunes to install, along with beefy warning flags for “unapproved apps”. They could create those $999+ “pro” developer accounts, along with dedicated App Store point-of-contact and accelerated review process (levels of partnership program exist on many other platforms and in many other businesses).

Or Apple could just spend some of that 35 billion on hiring a legion of reviewers (rather than just 40ish), training them to the standards of Apple Retail, creating a second team dedicated to communicating with developers, and third team focused solely on whatever tiny percentage of cases, like the one above, spiral out of control.

Yes, Apple is making incremental improvements like email escalation and better review status messages, but every step forward always seems to be met with an equal and opposing step back.

2 billion downloads, 100,000 apps — Apple touts the growth and size of the App Store in press releases, they need to start respecting that size in practice. Observably respecting. It shouldn’t take a champion inside Apple. It shouldn’t take emails from Apple Marketing SVP, Phil Schiller. It shouldn’t take an open letter from Steve Jobs. (Though it might help restore some developer confidence at this point). It should just work, and Apple needs to invest whatever they need to invest at this point to make it work.

This is a story by the iPhone Blog. This feed is sponsored by The iPhone Blog Store.

After 3 Months, 3 Rejections, Airfoil Speakers Touch Ships, Developers Leave iPhone


Why It’s Easier to Make a Great Twitter Client for iPhone than for Android

November 11th, 2009

tweetie_2_0538

Why is it easier to make a great Twitter client for Apple’s iPhone than for Google Android phones like the new Verizon DROID? After Robert Scoble wrote a typically impassioned post entitled The Droid fails AS A PRODUCT when compared to Palm Pre and iPhone, and used Twitter clients as an example, Thomas Marban of Android’s premiere Twitter client, Twidroid, responded:

one of the main reasons why UIs are unequally inferior are not only the way you build apps (open vs. closed hw/sw system) and the SDK itself but also marginal to non-existing UI standards, no ready-made drag & drop UI items, variations in carrier- & device firmware, hard- & software input, screen sizes, international customizations, modded phones, rooted phones and last but not least completely different expectations among users and the linux’ish target group itself. in a nutshell: beautiful mess. obviously, all these reasons eat up a huge pile of time that one could better spend with improving UX and polishing the interface. those who started early with android development have learned and are still learning it the hard way, just like they did with win 3.1 back in the days.

John Gruber of Daring Fireball, in Lots of Excuses comments:

That doesn’t sound like someone who plans to ever ship something of the caliber of Tweetie, Birdfeed, or Twitterrific. From what I’ve seen of Twidroid, it’s not even as good as Craig Hockenberry’s original version of Twitterrific for iPhone, which was written as a jailbreak app before the iPhone officially supported third-party software. If Android hardware diversity is already a problem for third-party developers, it’s only going to get worse.

This also highlights the advantages Apple has given iPhone developers. Not only is the iPhone based on OS X, but the development tools are based on Xcode and Interface Builder, and while not as many developers are likely already familiar with Cocoa touch as, say, developers might be with Android’s language(s) (or web developers may be for the Palm Pre), existing Mac developers can make those tools sing. And, given the SDK Apple provided, even new developers get a huge head start in terms of functions and user interface elements.

Sure, that means there’s a lower barrier of entry to creating poor iPhone apps, but it also means great developers aren’t wasting their time re-inventing UI wheels, or fighting the OS to do right by their apps. They investing that time in making great apps.

This is a story by the iPhone Blog. This feed is sponsored by The iPhone Blog Store.

Why It’s Easier to Make a Great Twitter Client for iPhone than for Android


How Macworld Got Their iPhone App Approved or How Having a Big Voice Helps

November 7th, 2009

app_store_church_lady

Umpteenth verse, same as the first — Macworld turned their iPhone ebook into and app and submitted it to the iTunes App Store. It was rejected. Several times. Finally editor Jason Snell expressed his frustration on Twitter and several high profile blogs picked it up. Apple called him immediately to try and make it right.

Good for Macworld. Bad for all the developers who lack the same megaphone by virtue of their job and connections.

Granted, with 100,000+ apps, the non-sensical and erroneous rejections remain a tiny percentage, but even a tiny percentage of 100,000+ represents many developers’ time, effort, and money. It’s frustrating for them and embarrassing for Apple.

Tim Cook and Phil Schiller claim they’re making improvements, and no doubt they are. From a pure perception point of view, however, this is one issue that needs fixing sooner rather than later.

This is a story by the iPhone Blog. This feed is sponsored by The iPhone Blog Store.

How Macworld Got Their iPhone App Approved or How Having a Big Voice Helps