Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
WOW!:eek:

I sure glad that Steve is starting to realize that we need our 3rd party apps on our phone!

Do you honestly think they only just decided to do it?
Don't you think they might have planned it since before the phone was even announced?

So many people on this site think apple has no idea what it's doing, just because they have no idea what apple is doing.
 
Well, maybe both sides of this argument can concede that while Apple had been planning on researching this and POTENTIALLY finding a solution, and had reasons to both want and not want the iP* to be an open platform, the hacking and community/media response (I even saw the 'closed architecture' talked about on CNN!) deeeefinitely helped them along.
 
I really want to know who rated this story negative :p

I did. Here's why:

This is going to be great--for now--but a little worrying in the longterm.

The iPhone and its class is an entirely new and burgeoning market of device and software... opening up the iPhone by opening up an SDK is going to mean that Apple is going to be at risk for another situation like what happened in the late 80s and early 90s with Microsoft stealing all of their innovation. Right now they are doing a freehand sketch of the iPhone, but with access to all of the innards and sciences behind it, the methods, goals, and platform of the iPhone, it'll be a whole lot easier to start those photocopiers in Redmond...

This will all sound paranoid, but I'd rather be paranoid than myopic. Keeping it closed could have saved Apple and propelled them to 95% marketshare in those key early days. We'll have to see how this unfolds in, like Jobs says, several years...
 
Somethings can be tolerated more on PCs than they would be on consumer devices.

You may want to control your iPhone, but in order to do so, it would probably be at the expense of other users of the device. To turn it around, why should OTHERS be limited and inconvenienced by YOUR control freak impulses?

How is this a reply to my posts? I have been vigorously and annoyingly advocating AGAINST control. Let the device be what it naturally wants to be - a mobile computing platform, free to grow to meet the demands of those who hold it.

I can think of no scenarios where something I do to my phone, say installing some vicious application, would affect anyone else with a phone, any more than installing a similarly vicious application on a computer would be. How would "controlling" my phone come at the expense of anyone? However, if you wish to put in all these rules about what I can and can not do with my phone, then it will not meet all my needs (as it currently does not, and no other phone can). Rules that forbid me from writing an application outside of Apples blessing directly affects me in a negative way, and provides no real benefit that a free and open market won't already provide (as, once again, the macintosh demonstrates by example).
 
Don't kid yourself, this is Apple in re-actionary mode. They now realised they have their strategy wrong and cannot keep up with the hackers so they have no choice.... UNLESS you can give us documentary evidence to prove otherwise.... ;)

Excerpt from that article:
Later asked by an audience member about writing applications for the iPhone, Jobs said that Apple ultimately wants both the iPhone to be secure and open without compromising either attribute. The last thing Apple wants, he suggested, is an iPhone that can be easily hacked or that crashes as a result of installing third party software.

“I think sometime later this year we will find a way to let third parties write apps and still preserve security. But until we can find that way, we can’t compromise the security of the phone. Nobody’s perfect, but we sure don’t want our phone to crash. We would like to solve this problem, if you could be just a little more patient with us, I think everyone can get what they want,” he said.

Yep you are right, he did say that in May, I remember watching the video feed also.

What is it with all you people, are you all sooo short on memory (bad one).

You don't remember what it turned out to be?

"SWEET SDK", that is!

Don't you see now, that it's the same Jobso, pulling the same tricks of calming down (doubting zealots, hackers just hate him) with the SAME junk, he gave last time?

That "solution" turned out to be "Safari SDK".

An early iPhone quote from Jobs:
“These are devices that need to work, and you can’t do that if you load any software on them. That doesn’t mean there’s not going to be software to buy that you can load on them coming from us. It doesn’t mean we have to write it all, but it means it has to be more of a controlled environment.”

That was in January. Can you explain how web apps fit "buy," "load on them," and "it doesn't mean we have to write it all" description? (Actually, I don't doubt you'll come up with something.) Apple, right or wrong, holds back with strategies and development that they're not ready to announce. You may be used to other companies announcing mere ideas.

Unless you have first-hand knowledge confirming what you say, you're speculating, with biases firmly in place.
 
An early iPhone quote from Jobs:
“These are devices that need to work, and you can’t do that if you load any software on them. That doesn’t mean there’s not going to be software to buy that you can load on them coming from us. It doesn’t mean we have to write it all, but it means it has to be more of a controlled environment.”

That was in January. Can you explain how web apps fit "buy," "load on them," and "it doesn't mean we have to write it all" description? (Actually, I don't doubt you'll come up with something.) Apple, right or wrong, holds back with strategies and development that they're not ready to announce. You may be used to other companies announcing mere ideas.
You're completely right, but if someone doesn't want to be generous in their own speculation, regardless of how often they turn out to be wrong, they probably won't be. Some people make a regular habit out of declaring Apple guilty until proven innocent (or whatever more appropriate analog).

~ CB
 
I did. Here's why:
Originally Posted by wongulous View Post
This is going to be great--for now--but a little worrying in the longterm.

The iPhone and its class is an entirely new and burgeoning market of device and software... opening up the iPhone by opening up an SDK is going to mean that Apple is going to be at risk for another situation like what happened in the late 80s and early 90s with Microsoft stealing all of their innovation. Right now they are doing a freehand sketch of the iPhone, but with access to all of the innards and sciences behind it, the methods, goals, and platform of the iPhone, it'll be a whole lot easier to start those photocopiers in Redmond...

This will all sound paranoid, but I'd rather be paranoid than myopic. Keeping it closed could have saved Apple and propelled them to 95% marketshare in those key early days. We'll have to see how this unfolds in, like Jobs says, several years...

I thought it was Curious that there was a specific mention of Nokia.
Don't Nokia use much the same Platform as Apple, isn't the Nokia Browser a ARM port of the WebKit open source project? http://trac.webkit.org/projects/webkit/wiki/S60Webkit

What i'm wondering is Steve hinting to a more active partner ship between them to not just release an iPhone SDK but to release an Open Platform SDK that of not only will Apple support and try like all might to produce the best device to run it on (ie. no multi-touch but on an Apple Product) but also provide the best enviroment to develop and distribute (Xcode and iTunesMS).

They aren't going to release the internal workings just the reference spec.
On the other hand there going rule the developer market.
 
I guess this mean there'll be another software update (hopefully) to further lockdown the phone/beef up its security so as to protect the core software and ensure reliability and one gateway would be left open allowing these apps to run.

I'll take a working phone over 3rd party apps anyday
 
What i'm wondering is Steve hinting to a more active partner ship between them to not just release an iPhone SDK but to release an Open Platform SDK that of not only will Apple support and try like all might to produce the best device to run it on (ie. no multi-touch but on an Apple Product) but also provide the best enviroment to develop and distribute (Xcode and iTunesMS).
An active partnership between Apple and Nokia? No... Nokia is really happy about their new "open" campaign (showing up how they're "better" than Apple), and like any political candidate, they're not looking to blur any lines of distinction, so much as dump mounds of manure all over the iPhone. I don't think that collaboration would work unless Nokia felt they needed Apple somehow.
I guess this mean there'll be another software update (hopefully) to further lockdown the phone/beef up its security so as to protect the core software and ensure reliability and one gateway would be left open allowing these apps to run.

I'll take a working phone over 3rd party apps anyday
Me too. Every now and then I try talking to my co-worker about doing more with his iPhone, and he looks at me like I have three heads. I got an iPhone, and I want it to eventually replace my Sony Cle that I used with BalanceLog. I'll wait though (especially with some kind of date to work with). I want them to do it right. I don't want to hear mocking reports of how lame iPhone security is, and find a worm/trojan has been busy recording my bank passwords.

~ CB
 
Are you quite certain that iPhone 1.0.x is based on OS/X 10.4? Perhaps you could share your source for that? The only information I can find indicates that the iPhone has been based on OS/X 10.5 from the start:
http://www.appleinsider.com/articles/07/01/18/apples_iphone_runs_mac_os_x_leopard___report.html

The guy in the Chicago Sun Times assumed just like everyone else that it's based on leopard because it has core animation. Apple's not said either way and aren't likely too. Core animation is just a framework, apple could ship it on Tiger if they wanted, except for the fact they'd have to update core image on tiger too.

I'm sure it's closer to Tiger than it is to leopard. Bottom line, iPhone OS X is NOT MAC OS X, it's a mix an match job. It's a arm optimised mach kernel with a subset of the Mac OS frameworks with a custom UI framework on top. I'd say it's closer to Mac OS than Wince is to Windows XP or Vista, and sure you'll inherit a lot of nice bits of non-gui code, but it's not Mac OS.

Apple never mentioned signed apps until just recently, i think because a lot of the delay we experienced this summer was about making this stuff rock solid. The fact that 1.02 doesn't have signed code and 1.1.1 does, tells me the kernel has been rebuilt to check sigs and thus is more like Leopard.

What's taking Apple so long in releasing the iPhone SDK, well their starting point is once they've worked out how binary signing and sandboxing is going to work. Which is right now. Over the next 4 months what'll they be doing? Rationalising the API's you will and will NOT be allowed to access.

M. ;)
 
I think it's fair analysis that Apple have been thinking about a native SDK for iPhone for a long time. But it was not a priority for July 07 as Apple's software teams have been stretched for resource (Evident from the Leopard delay).

It's also apparent that announcing the existence of an SDK by Feb shortly after the 1.1.1 release and not during one of their special events, indicates their reacting to people bricking their iPhones and hackers cracking 1.1.1.

They did the same last year by pre-announcing the AppleTV, the point was to get the message across to the TV & Film execs, look we're serious about selling video and look at what a cool implementation we've got. Get off the wall and agree to our terms.

This time round, they're saying, don't hack your iPhone/Touch, it's not worth the risk and anyway we'll have a nice official method of development and probably software delivery early in the new year. So hang fire y'all. ;)

M.
 
The Feb '08 date is probably a stretch and put out there so that Apple can 'beat the deadline'. Before the iPhone and delays with Leopard, that was standard operating principle. Remember the switch to Intel? That was supposed to take a couple of years but they got that done way ahead of schedule.

Personally, I wish they would hurry up and complete it so that we get non Safari apps (legit, not hacked). Although people have done some great work with Safari, editgrid is one of those nice apps, true non-Safari applications are the best way to leverage the iPhone's 'mobile computing platform'.
 
If I develop my own widget, I am hoping the apple SDK will allow me the same features as the native widgets do including iTunes support for saving and sync'ing. Otherwise, the settings and data associated my widget would not port over to another phone ( like for example, if I ever have to use a temporary phone for the phone repair etc. ).
 
Steve Jobs said:
Let me just say it: We want native third party applications on the iPhone, and we plan to have an SDK in developers’ hands in February.

funny-picture-cat-fail.jpg
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.