Apple drop iPhone NDA

About bloody time; Apple remove the NDA from their developer programme.

“We have decided to drop the non-disclosure agreement (NDA) for released iPhone software.

We put the NDA in place because the iPhone OS includes many Apple inventions and innovations that we would like to protect, so that others don’t steal our work. It has happened before. While we have filed for hundreds of patents on iPhone technology, the NDA added yet another level of protection. We put it in place as one more way to help protect the iPhone from being ripped off by others.

However, the NDA has created too much of a burden on developers, authors and others interested in helping further the iPhone’s success, so we are dropping it for released software. Developers will receive a new agreement without an NDA covering released software within a week or so. Please note that unreleased software and features will remain under NDA until they are released.

Thanks to everyone who provided us constructive feedback on this matter.”

The first step in competing with the much more developer-friendly Google Android platform?

Very cool Safari iPhone demo

It seems Apple included a Safari update in their recent 2.1 firmware upgrade and have now opened up a few new things for web developers to play with, as Matthew Congrove blogs about on myDailyPhoto. His iPhone Safari Flick Navigation demo is really impressive and opens up new ways of serving web content to iPhone/iPod Touch users.

Browse the demo directly from your iPhone by clicking here. Article originally spotted on Ajaxian.

Mac + Eclipse + FDT = a worthwhile huge pain in the ass?

Maybe it’s just me. Maybe I’m too used to things working out-of-the-box when it comes to applications. Maybe it’s because I’m on a Mac (at home). Maybe I’m a bit slow (a distinct possibility).

Today I tried to get a combination of Eclipse and FDT working, after two very clever ex-colleagues of mine highly recommended it as a better alternative to Flex Builder. After going for the PHP flavour of Eclipse on recommendation, I installed FDT through the Software Updates option within Eclipse. On restart I was prompted with memory warnings; that I needed to assign more memory to Eclipse. I thought this was a bit strange, as I was used to doing this years ago on Mac OS9 but hadn’t come across it so far on OS X. Anyways, I managed to sort this issue but then compiling my Hello World test required the Flex SDK being targeted. No biggie, but needed to tackle workarounds involving playerglobal.swc on the Mac. Eventually I published my swf from ActionScript.

Decided to try and publish some MXML. Learned that FDT seemingly doesn’t support it yet but that it’s coming soon. So, right now I’m in this kinda vague no mans land where I think I know I should kinda be checking out FDT, but I don’t appreciate why it’s so good and the workflow process that might be entailed with using it (especially if you’re also having to deal with MXML).

I’ll hopefully update this again once I’ve made further inroads into the process, but after day one checking it out I’m not sold yet. Is it better than working in Flex Builder 3 and/or Flash?

P.S. Hello Adam and Joe! Not THE Adam and Joe, although they are pretty funny themselves.

Safari 3.1 kicks ass

Apple have updated Safari to version 3.1 to include support for a lot of cutting-edge technology (including client-side database storage), along with adding a native developer dropdown (enabled within the preferences section). With Firefox 3, Opera 9.5 coming soon and, erm, IE8, it’s looking like the browser market is about to make web developer’s lives a lot more interesting soon.

By “interesting” I of course mean more difficult!

P.S. Visit this page in Safari 3.1 to see some funky CSS animation. Coo!