Respected Developers Begin Fleeing the App Store
wiedzmin writes "Facebook's Joe Hewitt, Second Gear's Justin Williams, the long-time Mac software developer known as 'Rogue Amoeba' and other respected App Store developers have recently decided to discontinue their work on the platform, citing their frustration with Apple's opaque approval process. Continued issues with erroneous and snap rejections of applications and APIs are prompting more and more developers to shun the platform entirely. Though there are tens of thousands of other developers who have pumped out over 100,000 apps for the platform, continued migration away from iPhone development will most likely result in lower quality software."
Same story... "Hi, I'm Mac guy, and I've got nothing to do...because I have no software..."
This is my sig.
> "...continued migration away from iPhone development will most likely result in lower quality software."
Dooooooooooom!!!
The only ones to "stick it out" are the ones who are the most likely to profit. This tends to be apps people mostly want.
One could argue the less likelihood of profit on an Apple Mac platform is what increases the average quality of programs -- only the "good stuff" gets ported, in addition to a handful of Mac-only apps.
Keep in mind part of Apple's "problem" with the approval process isn't related to quality at all, but rather strategic thinking on which apps to allow, to discourage competition to its own apps, or the OS as a whole.
(-1: Post disagrees with my already-settled worldview) is not a valid mod option.
There's an app for that.
The Kruger Dunning explains most post on
Note the irony of a FaceBook employee complainng about Apple's closed system.
I've got an iPhone and I use a Mac at work, but I certainly don't consider myself a "fanboy". I got the iPhone in part because there were a few good apps that I wanted on my first smartphone. However given all the bad press Apple gets over summary rejections of apps I'm very inclined to NOT buy another iPhone when I decide to get rid of this one. There are a number of smartphone apps that I'm aware of that Apple doesn't allow on their phones for one reason or another. My brother can dictate entire e-mails or text messages on his Blackberry using an app from a company called Vlingo. It apparently provides high quality speech to text capabilities and integrates with almost any app on that platform. They released an iPhone version a year ago but it's very limited in what it can do because Apple restricts things so much. The iPhone Vlingo app is limited to Google searches and updating Twitter & Facebook, and it's all apparently because of the way Apple restricts things.
If a company like Vlingo can extend the functionality of smartphones like the Blackberry, Android, etc. in ways that Apple and others never seriously considered then I'll very likely go with those phones in the future, and not one that's artificially restricted due to the limited vision of people like Steve Jobs.
They may cite disapproval with Apple's approval process but the reality the app store is getting diluted with more and more apps and developers, and it's getting tougher to make those million dollar apps. Like anything, the first on board have the best chance of benefiting the most fiscally and in popularity. I assume some of these developers are also getting disillusioned that the glory days are gone.
I'm a full time iPhone developer. I'm going no-where.
I find Joe Hewitt's whining to be maddening. He made a very popular iPhone library (the Three20 project) and knowingly used some private API's inside - as far as I can tell without anyone knowing. Then when it turned out Apple started looking to see what symbols your code was using in an extra step to enforce this, Joe basically abandoned the community and decided to quit.
The sad part is that he didn't even need to use them. There are multiple forks of Three20 now that fix the use of the private API's with no loss in functionality.
The other guys, they have more of a reason to be angry although apps rejected continue to be a pretty minor aspect of things, and many rejected apps get through with a few simple changes. But Joe lost any right to complain when he abandoned the people that relied on his expert judgment in the creation of a framework.
"There is more worth loving than we have strength to love." - Brian Jay Stanley
The N900 is about to be launched. Come on over to http://www.maemo.org/
You will be welcome, and no one will tell you what you can, or cannot do.
Cheers!
* Carthago Delenda Est *
Not the trend I have noticed. In the beginning lots of useful apps came out. Lately i have noticed a ton of crappy 99 cent "games" and anything more complex is having a heck of a time getting approved.
I love my iphone, but I'm going to get a nice Android phone when my contract is up because I'm tired of Apple putting its own design philosophy and profit motives over my preferences as a consumer. Their rejection of the Google Voice app was bs, plain and simple. I like Google Voice, and I want to use it as easily as possible. Their meddling in the app store prevents me, the user and customer, from doing this.
I wonder what other great, useful Apps are being turned down because Apple thinks they will "ruin the user experience" or "confuse the user."
Imagine if Microsoft tried to tell people what software they could and couldn't put on their PC's.
I think this also has to do with the maturing of the platform. The low-hanging fruit is essentially gone, and it will get harder and harder for the free-thinking lone wolves to come up with original and compelling software that can compete. Businesses however, have the resources to continue to create more advanced and complicated iPhone versions of their products. They also have the resources to better manage the approval process, both by building carefully to the API, and (for bigger businesses) by having a phone call relationship with Apple.
Hewitt, who is undoubtedly a great and innovative developer, decided to strike out for more open pastures. Who can blame him? But the Facebook app is not going anywhere, and most likely will continue to be developed to a high quality. Over time I expect we'll see a greater mix of apps by existing software businesses, and less duplication in app functionality as more independent developers get frustrated or bored and leave.
Build a man a fire, he's warm for one night. Set him on fire, and he's warm for the rest of his life.
People who use the iPhone don't care about things like this.
And I'm going to put forward that the approval process has less to do with developers leaving than the fact that the iPhone app market is quite saturated and the Android market is not.
Don't take life so seriously. No one makes it out alive.
Perhaps they're leaving because there's 100,000 apps in the store, so many of which are out and out horrible that it drowns out any possible quality product unless you have a large marketing budget or can get lucky enough to crack one of the top 10 lists.
Or they might just prefer working in a more open enviroment, which is what it sounds like. As a software engineer, things like the iPhone approval process make me very nervous about investing quite a bit of time and money into a project, especially if the process is overly opaque. I've worked with large corporations on getting software approved before, and usually it is more of a cooperative process.
Apple likes to control user experience, and that won't change. That is their niche. They may relax their review process a little bit if there's a backlash, but they won't change their spots. Other phone brands will probably take up the cowboy coders who don't like red tape because they want to catch up to Apple's offerings. Their more relaxed review process will probably result in cheaper and perhaps more varied apps. However, it will be just like the Windows world compared to the Mac world:
* more choice
* lower prices
* more hackers
* more chaos
* more bugs
* inconsistent UI
Same as it always was.
Table-ized A.I.
This is already possible; Verizon doesn't lock down their Android devices. "Open Application Development" was actually something that Verizon advertised for the Droid. Android's app store isn't restrictive at all (there's even software for rooted phones on there), and if the software you want isn't there, you can download and install it from somewhere else.
The only ones to "stick it out" are the ones who are the most likely to profit.
I disagree. The unprofitable applications will be unprofitable on other phones too. The profitable applications will be profitable on other phones too. The developers who migrate away from the platform are the ones getting rejections from Apple. These are the most unique, edgy, or innovative applications, or ones that compete with the built-in Apple functionality.
Therefore, I conclude that this will not increase the quality of programs on the iPhone. It will decrease the diversity, while increasing the diversity and quality on other phones. But that was going to happen no matter what Apple did: When you are at the top, the only direction to go is down.
People who use the iPhone don't care about things like this.
I use an iPhone, and I _do_ care. iPhone started promising, but Apple killed several apps I wanted. Now the good devs are leaving for Android? I may buy a droid or droid++ next year.
When any app can be rejected for any reason at any time by someone who is for practical purposes anonymous and answerable to nobody and the process has a reputation for being capricious and arbitrary, nobody wants to risk a significant development cost on AppStore acceptance.
Economically, the most likely to turn a profit are a series of $0.99 throwaways that might become the next "pet rock". If it's rejected by some guy because his corn flakes got soggy that morning, little is lost. Statistically, some of them will certainly be accepted.
Add in that Apple has ALSO gained a reputation for rejecting anything more useful or more polished than their own iPhone apps and you create a huge disincentive to spending a lot of time and energy on an iPhone app.
Developers who want to spend a lot of time and energy on a killer app will tend to target a platform where they are certain to be able to market the result. If successful there, they *might* decide to risk the cost of porting to the iPhone. In making the decision, they will consider that the more "killer" the app is, the more likely Apple is to decide it threatens their platform dominance and kill it.
Except I'm not really sure if Joe Hewitt counts.
The app isn't leaving the app store. The app is still going to be updated. Facebook owns it. Joe Hewitt threw a hissy fit, and stopped working on it, and Facebook assigned other developers to it, so in practical terms there's nobody actually leaving, just some noise.
At least that's my understanding from reading up on this.
I was going to attempt an insightful and informed response...
But I am an early fan, and see the potential of paragraphs.
Don't thank God, thank a doctor!
The only ones to "stick it out" are the ones who are the most likely to profit. This tends to be apps people mostly want.
Speaking as somebody currently living on the proceeds of a software company I sold, this is a naive view.
It's not enough to have an app people want. You have to (a) sell it for enough money to make a profit and (b) keep support costs down enough so your sales profit doesn't disappear.
Right off the bat, when you sell software, it's not a matter of "a lot of people wanting" your product; it's how many want it at the price you set. Let's say you have a product that nobody would be willing to spend much money for, but you could sell it for about the price of a cup of coffee. Let's suppose the product is cheap to make and after you sell it your customers never call you. You can make money with that.
Suppose you come up with a ringtone. It takes you a week to get it into whereever you are selling it, then 5000 customers download it at $1.99, of which you clear $1.00 after the store gets its cut. $5000 for a week of work isn't going to make you rich, but it's a respectable payday. You can live off of that kind of project.
Is this something that people "want"? Well, sure, so long as its priced cheap. The key is that of those 5000 customers, you'll hear from maybe one or two, and you can just pay them $2.00 to go away.
Now suppose you (like I did) develop some kind of mobile data collection app that drives important enterprise decisions. That's pretty damned valuable. You can easily convince a company to pay you $500 *per seat*. The problem is that even if you could wish the software into existence, the customers need more than $500 per seat of support. In fact that's why an open source model works very well for critical systems -- you give the software away and charge for the real expensive parts. In any case, my calculations showed that we broke even on a $10,000 sale, after all was said and done, so we might as *well* have given the software away. We typically sold consulting services at anywhere from $20,000 to $50,000 a pop, which was where we made our money. Believe me, when you've got a team of six engineers, a $20,000 project doesn't look so big.
The point is that the "build a better mousetrap" theory is simply wrong.
Your ringtones and iFarts are bottom feeders in the world of app development. They are profitable for their developers precisely because users don't care very much about them. Price a product like that low enough and you can make money.
The kind of apps that developers garner respect and admiration for developing are a different kettle of fish. It's *hard* to make a profit selling apps that people really care about, because customers demand a relationship with you. That's expensive.
The last thing you need is a third party inserting itself into that expensive and delicate process -- especially an opaque, unpredictable one. You work with your customers and discover they really need some extra functionality. You build it, then have to wait to find out whether you can sell it? That's nuts. You need that like you need a hole in the head.
And this is even worse: you make a portfolio of apps, and then you can't sell them to a different developer? That's a critical exit strategy for many small developers. They have the vision and brains to create an app, but don't have the size to support it. So they develop and market it, and sell it to somebody who is already supporting apps for the main customer base. That's what I did when I sold *my* business. When I had more customers that I could know personally, it wasn't fun anymore so I told one company that if they didn't buy the software I'd sell it their competitor.
Basically, what Apple is telling is that the iPhone is *still* not a platform. It's a music playing phone that can also run toys like iFart.
Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
Exactly - I spent a couple of weeks and a reasonable amount of money to develop a small app that I thought was useful. Not million-dollar, but useful.
Many months later, apple rejected it. A nice chap called me up. I'm not breaking any rules, it isn't offensive or bad taste. It's just a utility that they don't want.
He said that he felt bad - but that there it was.
It certainly makes me think twice about investing time or money in any idea that is at all innovative in the way that it uses the platform.
VLC Remote for iPhone and Android