iOS So, is the 4.0 SDK under NDA?

[Earendil]

So, I'm a little confused, and Apple doesn't have a simple breakdown chart.

I am currently (what I will call) a registered Apple developer, but not a paid one. I have a login/pw (though their site appears broken atm), I have the IDE and most recent SDK (not 4.0). I'm built and run in the sim a few proof of concept apps.

What I'm wondering is, is the 4.0 SDK (legally) available to me?
Is the list of new API's publicly available?
If not for either one, when will that change? Right at release date, or between now and then?

Basically I'm still in the planning stages of a project that might make use of my iPhone. Under the current set of API's, my project is turning into a bit of a PITA as far as the iPhone programming goes. This could be changed though with the 4.0 SDK. However I don't really feel like putting the project on hold, or making some half arsed implementation with the 3.2 SDK, if everything is going to get flipped on its head in June/July.

Thoughts? Answers? Information? Tell me I'm being stupid?
I'm open to pretty much anything...

 

[SilentPanda]

You can't use any of the 4.0 stuff including the SDK unless you are a paid registered developer. Once it is publicly available on iPhone devices you will be able to though.

 

[Earendil]

You can't use any of the 4.0 stuff including the SDK unless you are a paid registered developer. Once it is publicly available on iPhone devices you will be able to though.

Thanks for the quick reply!

By "use" does this include ever having a list of the API's? Or will that documentation be available at some point before the OS ships?

Do you know if the 4.0 SDK is covered by an NDA to the point that asking questions like
"Are there new API's for serial com" or
"Have they included math functions for FFT?"
would be wrong?

I don't want to get a dev in trouble. I'm just lacking knowledge on how this whole thing works

 

[fishkorp]

If the previous releases are any indication, the NDA will be lifted and the SDK and API docs will be made available shortly after 4.0 is released to the public. Some devs would be willing to answer your questions, others will hold firm to the NDA. Some site, somewhere might mirror the API diffs, but that's technically an NDA violation.

 

[Earendil]

If the previous releases are any indication, the NDA will be lifted and the SDK and API docs will be made available shortly after 4.0 is released to the public. Some devs would be willing to answer your questions, others will hold firm to the NDA. Some site, somewhere might mirror the API diffs, but that's technically an NDA violation.

Okay, thanks for the info.

Disappointing that there is no legal way for me to make an educated desicion about whether to include the iPhone into my project plan without paying $99

 

[lloyddean]

Okay, thanks for the info.

Disappointing that there is no legal way for me to make an educated desicion about whether to include the iPhone into my project plan without paying $99

You do realize that you can't distribute your application with out becoming a paid developer, don't you?

 

[Earendil]

You do realize that you can't distribute your application with out becoming a paid developer, don't you?

Yes I do realize that, and with all do respect, irrelevant

My project is not an iPhone app. My project is an Arduino project, that may make use of the iPhone. However it does not need to use the iPhone, and won't use it if it is impossible to incorporate it into the project. I might not even use it if the effort is too great. Still, it would be fun, and if I can manage it I'd like to.

So you see, the end goal is not to sell some iPhone app. It's to create this Arduino project. If the iPhone can feasibly be worked into the project, I will pay the $99 so that I can load the home brewed software onto my device. However I'd rather avoid paying $99 to browse the SDK, and then decide that the iPhone does not suit my needs.

Now I'm back to fiddling with the 3.2 SDK to see if it'll work.
Cheers!

 

[skunkworker]

Yes I do realize that, and with all do respect, irrelevant

My project is not an iPhone app. My project is an Arduino project, that may make use of the iPhone. However it does not need to use the iPhone, and won't use it if it is impossible to incorporate it into the project. I might not even use it if the effort is too great. Still, it would be fun, and if I can manage it I'd like to.

So you see, the end goal is not to sell some iPhone app. It's to create this Arduino project. If the iPhone can feasibly be worked into the project, I will pay the $99 so that I can load the home brewed software onto my device. However I'd rather avoid paying $99 to browse the SDK, and then decide that the iPhone does not suit my needs.

Now I'm back to fiddling with the 3.2 SDK to see if it'll work.
Cheers!

If you are talking of having the iPhone physically interact with your arduino over its ipod/usb cable, its gonna be a lot more than just getting the paid iphone developer account. You have to go through apple to be approved to get access to that device, it might just be easier for you to jailbreak it instead, if you really want to connect hardware.

Paying the $99 just allows you to codesign your projects so you can physically run them on the device & also gives access to the iphone os beta program to get code before the non-paid developers allow. Jailbreaking may be your best option if you aren't planning on distributing it.