I have karma to burn, so here it goes with another hard truth:
There is a big, undeniable, compelling reason for Apple to distrust us iOS developers: as a whole we're incompetent bumblers. I'm talking about security. The number of iOS developers who do things like transmit the UDID (Universal Device ID) in plaintext, or who "encrypt" their communications by doing things like zipping it (no encryption, or the same key for every client) then "securely authenticate" it with CRC32 is just jaw-dropping. In terms of doing things with just a competent level of security, large numbers of us are screwing the pooch in ways that severely contaminate the pool for the rest of us.
Of course, this points to the ultimate incompetent bumbler in this regard: Apple. Apple should've built a better security library -- one which makes it harder to use security in an incompetent way. (Forces you to do security right, or the API doesn't work at all.) For heaven's sakes, they require you to muck with 3 objects just to shift a date from one month to the same day-number the next month. Some better support in security might benefit the iOS developer community just a bit more than the ability for our apps to work smoothly in both Julian and Gregorian calendars.
I plan on making my living through iOS in the next year, but Google seems to be way ahead of Apple with regards to security.
But I also think there is more to it than that. Apple needed to provide those services in order to highlight the devices they were selling, because specs alone don’t sell. [...] And you can’t trust third party developers to do it for you.
It all sounds pretty reasonable until you remember that the 30% tax is more or less aimed directly at removing Amazon ebooks from the platform, and that the kindle app was available well before iBooks.
> 30% tax is more or less aimed directly at removing
> Amazon ebooks from the platform
Lots of books apps were available before iBooks. Apple has no interest of driving any content provider off iOS: anything that helps sell hardware is good for them.
Amazon is not going to leave before they absolutely have to. Every second they hare on the iPhone increases their exposer, makes them money, and keeps their customers happy.
It is more than that. The latest estimate I've seen says that Amazon has 58% of the ebook market, while Apple has 9%. With every Kindle book bought and every day that passes under the status quo, Amazon's leverage grows. They have no interest in forcing a confrontation even a minute early.
>If Amazon were serious about leaving, they would have left by now, to try and force Apple to not make the change on June 30.
No, Amazon leaving now would make it look like Amazon pulled the app. Perception is very important. Most of the customers do not read tech sites, but they will notice when apps are pulled, and will ask 'Who pulled my app?'? Amazon (and I suspect Apple as well) wouldn't want to be the answer to that and be object of rage.
If Amazon doesn't want to play by the new rules, I suspect they will wait for Apple to make the first move.
This is definitely true of Netflix too, I suspect there's a percentage of iPad buyers who bought the device just for Kindle/Netflix apps.
> I suspect there's a percentage of iPad buyers who bought the device just for Kindle/Netflix apps.
It wasn't the only reason I bought an iPad, but had the Kindle app not been there, it would have certainly been a deal-breaker. And even if they back off now, the uncertainty Apple has introduced has driven me to an Android replacement. I simply don't trust Apple to proceed with the customer's best interests in mind anymore.
Apple's service agreement actually demands price matching, which means a content provider must provide their best price available through the app. It is probably possible to charge more for an "iOS edition", but Amazon specifically has a standard publisher contract that requires them to charge the same price on all platforms.
Which is a sensible clause for Apple, so that Amazon can't go and say "all books bought on the Kindle device are 50% off what you pay when you buy the book on the Kindle for iPad app" to drive device sales.
You have it a bit backwards, the kindle is there to drive ebook sales, not the reverse. Apple only added the clause when they added the mandatory in app sales with the 30% tax - if amazon had any intention of doing something like that you'd presumably already have seen that behavior on the iphone or pc or osx or android.
Whats in it for the companies? Run afoul of Apple and get locked out(rejected or worse, approval gets delayed for months) of the tens of millions of potential customers? This has already happened for many apps.
No one except very small companies are going to go this route, if any.
I think "Trust" is used in a weird context here.. "Why Apple Doesn't Rely on Developers" might be a more accurate title.
He's saying that Apple doesn't sit around waiting for developers to create compelling apps for their products, not that developers are "untrustworthy."
Apple seems determined to avoid depending on Photoshop and Final Cut Pro to sell hardware, to the point of curbing software offerings that might become the reason to own an Apple device.
They don't simply believe that "you can't count on third-party software to sell your device." They believe "if you let third-party software sell your device, you have made a deal with the devil that you will regret."
Nintendo might be the same way, which is why the own so many of the big title characters for their machines. Sony and Microsoft picked up on this, and own their own franchises as well.
Not trusting developers is kind of a problematic approach when your platform's key strategic asset is a vast library of third party applications. Apple's own iOS software is great, but the playing field for Android and Windows Phone 7 seems a lot more level without developers on Apple's side.
> but the playing field for Android and Windows Phone 7 seems a lot more level without developers on Apple's side.
The funny thing is, I bet Apple prefers that to the alternative - having the health of platform being dependent on a 3rd-party act. Love 'em or hate 'em, it's clear to me that pretty much all of the decisions Apple made over the last 10 years has been to keep them out of the position they were in in the 1990's where Microsoft and Adobe were essentially threatening to sink the Mac platform by yanking their most popular applications.
>Not trusting developers is kind of a problematic approach when your platform's key strategic asset is a vast library of third party applications.
I still don't think that's true. The key strategic asset is the unbeatable user experience and the core functionality - web browsing, movie watching, book reading, maps, stuff that comes built in.
A very large number of iPad users have never downloaded an app. Same for iPhone users. They find the core functionality to be sufficient for their needs. And they would be unhappy with ANY Android device because the user experience is sub par.
Well I have heard on a few occasions that over a third of iPad users haven't touched the App store.
I would assume it's even more for the iPhone... I know several non technical people with iPhones who have never used the app store but they're still happy with the phone.
The key strategic asset is the unbeatable user experience and the core functionality
The number of apps, which Apple mentions frequently in their ads, is one of Apple's key strategies to bring people in to make a purchase. You can't really say that the "unbeatable user experience" is as key because you don't experience that until you've made the purchase and used it for a while, and you'll never find out if it's unbeatable until you've used something else. Something like number of apps is easy to compare when making a decision among platforms, just like screen size is easy to compare, because it's a number. Unless you're in the lead on the specs, you downplay or don't mention specs because the numbers are not subjective like "unbeatable user experience" is. Number of apps is one of the few objective measurements Apple continuously uses when doing comparisons.
Most people try Apple products first, and THEN buy them.
They try them out at the store or they play with a friend's. This is the common pattern. Have you ever been to the Apple store? It's one big room full of people playing with iPads and iPhones
The user experience is unbeatable and everyone knows it, the non-techies just don't call it "user experience".
But they play with the iPad/iPhone/iPod and then they play with a few other competitors and the difference is beyond obvious. And this keeps them sticking with Apple.
Especially with phones -- everyone has tried blackberries, androids and iPhones because it's so easy to try out other people's phones. There are a few really nice android phones that are as beautiful as the iPhone but they are rare - it's rare to run into a person with one of them.
Most of the non-iPhone phones people own are ugly pieces of crap. This is negative advertising for the Android/Blackberry platform. Blackberries in particular are incredibly unintuitive on the first usage, while typical Android phones (admittedly cheap, but no one talks about the price at a party) suffer from blurry screens and clunky animation.
I use my phone as a phone, an e-mail reader, a GPS, and a web browser. I bought it for those things, and apps are a nice bonus, but a pretty negligible part of the overall value proposition for me.
The article exaggerates a lot. Denying users to have a browser other than Safari does not make iOS a better platform. Safari(and other similar apps) is not the best there is, the there ever was and the best there ever will be. Someone may create a way better browser then Safari at any time.
There is something we call competition in a free market. Example: when only IE was relevant, Microsoft couldn't care less about making IE better, but when things started to heat up, Microsoft took up the challenge and made IE a lot better.
Apple shipping a default browser and whatnot is good, but not letting developers compete with them is terrible.
The article provides no evidence to support the conclusion that it's about Job's or Apple's trust of developers. It just recounts some history and then jumps to disjointed conclusion.
In fact, it has nothing to do with trust. I can predict with 100% certainty that developers will flock to popular platforms and mostly stay away from failed platforms.
In the platform business Jobs had failures (NeXT, Macintosh classic) and successes (Apple II, iPhone, iPad). His successful platforms had no problems attracting developers, his failed platforms less so.
The trust relation actually goes in the other direction: it's important that the developers trust the platform maker.
Platform providers have a symbiotic relation with their developers which creates a positive feedback loop: successful platform attracts developers which make useful programs which makes the platform even more successful etc.
At the same time platform providers invariably compete with developers on their platform. Nintendo competes with other game companies writing games for their consoles, Microsoft competes with some companies writing software for Windows and Apple competes with other companies writing software for Mac or iOS.
To me the core of the issue is: how fair is the game. Platform provider will always have technical and marketing advantage over independent developers. Nintendo programmers probably know the hardware the best and Nintendo can cross-promote their games with their console. At the same time we know it's not enough to win: there are games that, at a given time, sell better than Nintendo's games. Microsoft Money couldn't beat Quicken and the Windows software market is so huge that Microsoft is not even playing in most categories.
Apple did set up the game to be unfair and they are fully taking advantage of that to maximize profit.
As such, they've broken my trust and trust of many developers.
First, unlike Android or Microsoft, they set themselves up as a final arbiter of what kind of software is even allowed to run on iOS. When Microsoft was competing with Netscape, they actually had to write a better browser for Windows. Due to Apple rules (no interpreters allowed => no JavaScript allowed) you can't even write a competing browser for iOS which is why there's no FireFox for iOS or Chrome for iOS.
When they didn't like Google Voice app, they just banned from iOS (despite it not even violating any official rules). It allegedly took government (FCC) investigation to get it enabled.
But that wasn't enough: the new in-app payment rules target companies that have much bigger and comprehensive businesses that just writing iOS apps. Apple wants to interject themselves between any service that offers some kind of paid service and users using iOS devices and collect chunk of the revenue despite the fact that for many such businesses 30% is economically impossible.
Those are major violations of developer's trust on the part of Apple. I for one will not write a single line of iOS code as long as there is a viable alternative like Android.
Breaking developers' trust isn't enough to break the platform. If the platform is successful enough, most developers will just swallow the bitter pill.
However, if there's one thing that doesn't change it's this: things change. Apple is on top of the world right now but Android is gaining momentum. Apple's greed is a dangerous game: if the Android momentum continues, it'll be much easier for developers to walk away from Apple's platform into a welcoming embrace of Google.
> The article provides no evidence to support the conclusion...
+1
I also agree that success of the platform was the driving factor in attracting developers. In fact I think some pundits put way too much weight in the argument about attracting developers. If people use it, they will come.
> they set themselves up as a final arbiter of what kind of software is even allowed to run on iOS
Personally I think this policy is part of the successful formula. The ugly truth is this is the right decision fr most people. Building trust in the platform by the users is FAR more important than the philosophical objections by a few developers and users.
As for competing browsers it's a little more complicated than that:
Technically Google Voice wasn't banned either. It was just held in limbo with no decision. The end result is basically the same however.
I for one am waiting to see what happens with the Kindle. I think it's now so influential that Apple would be idiots to kick it off. If they don't it'll lead to confusion about their policy. If they do it'll be the first competitive advantage Android tablets will have (IMHO).
Lastly when it comes to App Store rejection, in spite of Apple's nebulous rules it really is a case of "you'll know it when you see it" 99% of the time (if not more).
There seems to be a trend for some people to create apps that were never going to get rejected, submit them, get rejected and then immediately come to places like this to complain about how they've been victimized, which of course gets a certain level of support from the Apple haters irrespective of the merits.
It's almost like the blog post complaining about rejection is written before the app is submitted.
Im the author of the blog post, so first I wanted to thank you for your feedback.
Second, I thought a lot about what you said and it seems that I wasn't clear enough with my use of the word 'trust'. I also thought that the historic recount provided enough evidence that they do not let others control the experience of their devices. Apparently, it needed some more explanation. To be clear, I'm not talking about the App Store in general, but in the context of John Siracusa's article. I have updated the blog post accordingly, and here is what i wrote:
-------
Update:
It seems that I wasn’t entirely clear with my decision to use the word ‘trust’ . The main question seems to be,
Apple has over 400.000 apps on the App Store, then, how can they not trust developers?
The point I’m trying to make isn’t that Apple is not willing to work with developers on improving the platform, or in creating new uses for their devices. You can see their disposition every time they invite a third party developer on stage to talk about their apps, and how much money the are making from them. What I was referring to was the idea of the complete experience of a product from day one. Every aspect of the hardware has to have a counterpart in the software that can be used in a real world scenario. They would never include a hardware component without a killer way to take advantage of it in the software on day one. And for strategic reasons they have to control that software. Case and Point: FaceTime. There were videoconferencing apps before it, even on the App Store, but Apple felt that they were not showcasing the full potential of the new device, so they made their own. You may say that it’s just videoconferencing and that Skype already did everything. To that I tell you, Skype was not ready to take advantage of both cameras, they could only use the one on the back, so if you wanted to use the new front facing camera on day one, you simply couldn’t. You had to wait for Skype to issue and update. How is that a complete experience?. By contrast Motorola seems fine shipping a Barometer and even a SD card slot that have no use at all on day one, or shipping 4G support when they don’t have the hardware for it. When they announced the iPad they explicitly said that it needed to be better than a laptop and a phone on two key areas: browsing the web and reading ebooks. They already had a killer mobile browser in the form of safari, what they didn’t have was an ebook reader, so they made iBooks.
This is what I mean when I say ‘trust’. They are never going to trust a third party with a core competency of the device. Even if the software or service already exists. The only difference now, is that the device does so much, that they are stepping on everyone’s toes.
And thats the main idea behind John Siracusa’s article, they are now on both sides, and this could end up badly for Apple. The new subscription rules are just the latest expression of this internal discrepancy, as was the rule to ban apps created using Flash from the app store, and rejecting Google Voice from it altogether. I’m sure there are gonna be at list a couple more before Apple decides to or is forced to change their ways.
-----
There is a big, undeniable, compelling reason for Apple to distrust us iOS developers: as a whole we're incompetent bumblers. I'm talking about security. The number of iOS developers who do things like transmit the UDID (Universal Device ID) in plaintext, or who "encrypt" their communications by doing things like zipping it (no encryption, or the same key for every client) then "securely authenticate" it with CRC32 is just jaw-dropping. In terms of doing things with just a competent level of security, large numbers of us are screwing the pooch in ways that severely contaminate the pool for the rest of us.
Of course, this points to the ultimate incompetent bumbler in this regard: Apple. Apple should've built a better security library -- one which makes it harder to use security in an incompetent way. (Forces you to do security right, or the API doesn't work at all.) For heaven's sakes, they require you to muck with 3 objects just to shift a date from one month to the same day-number the next month. Some better support in security might benefit the iOS developer community just a bit more than the ability for our apps to work smoothly in both Julian and Gregorian calendars.
I plan on making my living through iOS in the next year, but Google seems to be way ahead of Apple with regards to security.