Why Apple Didn’t Release An iPhone SDK

The short answer is that not all engineers are made equivalent, and Apple is about danger administration; with the desktop, for instance, they don't let simply anybody run OS X on the grounds that they need their OS to function admirably wherever it runs. On the off chance that you could pack it onto anything and power drivers into it, the experience would fall apart essentially. 

It's the same with iphone — envision I download the most recent Superapp for my iphone. It does x and y, and its truly cool, yet after 4 hours my administration all of a sudden stops. I call At&t and they say my record is suspended on the grounds that I've damaged my system understanding. Huh? 

It would appear, the application was Wikicache — a cool minimal arrangement that never-endingly endeavored to reflect a duplicate of Wikipedia on my iphone. Splendid!. 

So now I can't make calls, At&t is bothering me, and all on the grounds that I simply needed to run this application that Apple in a roundabout way upheld by discharging the SDK. That is the issue. What's more bear in mind that Apple and At&t are in another and unconventional business plan, i.e. each one counts on the way that the other gentleman will convey. 

For Apple to discharge an apparatus that permits non-programming mouthbreathers to make an army of demoniacally moronic system applications onto At&t's unprotected, non-3g system would be a major blooper. Also here's the manner by which that would generally break down, given how simple it would be to make applications in such a SDK: 

< 

p align="center">25% [serious Danger to Network and/or Device Stability] half [halfway Decent] 25% [professional Quality] 

So am I frustrated that there's no SDK? Certainly. It would have been incredible. At the same time I see where Apple is originating from and
 likely would have reluctantly settled on the same choice myself. Mollifying engineers simply isn't worth subverting the whole venture before it has an opportunity to beg.