It’s going to become (if you haven’t already) the Holy Grail of the next few months, and it’s really attractive to try to schedule a native app for the iPhone, especially when Apple has pulled down the blind and offered an alternative solution to the one we all expected.

That decision was not to offer a native development SDK and decide that the applications would be via Safari. In doing so, they got some programming groups to “go live” and start tickling the iPhone. And they succeeded.

But the beauty of the road is walking it, not finishing it (as they say out there), and the group that achieved the feat packed the tools they had used and offered to the community as a “Developer Toolchain”. It is not properly a SDK, but a software application group that by working together they are “passing” work, combined with access libraries to the operating system, etc, …

And the difficulty is that this “Toolchain” we have to compile it us, which, according to TUAWIt is not easy at all. Setup is still cumbersome and slow, along with some absolutely unexpected version bugs pre-beta. However, there is already that “Hello World!” native whose meaning could not have been more accurate …

… Does anyone doubt that, sooner or later, an invasion will begin of native “homemade” applications? There is still a long way to go, and the inflection point it will be the day that “Toolchain” (or something better) is offered as a universal binary.

This is perhaps the best way to show apple that its users are the ones who are really thinking differently.

More information | TUAW

The problems of developing native applications for the iPhone today