Too Big To Fail

Aug 20, 2011

There is a reason I do not develop iOS applications. Every time Apple decides they need their cut from a developers hard work, I am reminded why. Ironically, every time Apple decides to update their terms to make sure they have the upper hand, is about the time I start thinking I should start developing native mobile apps. I wake up quickly. I agree that Apple is entitled to their cut, but they are destroying what used to be a great platform for developers. A great developer friendly platform is what catapulted the iOS line of devices to begin with. There is no way the iPhone is where it is today without developers creating awesome apps for it. I’m not saying it wouldn’t have been successful; just not this successful.

I see Apple as having a “too big to fail” attitude. That is a razor’s edge. Just ask Microsoft and they will tell you that no company is too big to fail. Back when I switched to Apple products, it was because they offered what I wanted. I wanted to do Rails development, and I liked what I saw in terms of tools. TextMate, for example. Sure, I could do Rails development on a Windows machine, but it sucks. Trust me. I set up a Rails environment on a Windows box. Torture! So I jumped ship.

I fear a similar situation with what Apple is doing now. It won’t be anytime soon, but if they keep screwing around with their iOS developers, they will leave. They will take the path of least resistance, just like I did when I came to Apple. And when Android has that one exclusive app, think Angry Birds when it was iOS only, the ball will start rolling. It all starts with one awesome app that you can’t get anywhere else.

(2-18-11) Update: Google may have smelled blood. They just released One Pass, a possible competitor to Apple’s subscription plan.

More stuff:

or go see everything in the archive.