It means lots of opportunities for 3rd party apps, which is good for elearning.
Sadly, that doesn't appear to be the case (at least not yet). Here are a couple of snippets from developer message boards etc:
> I just got back from Macworld Expo where I had a chance to speak
> briefly to one of the iPhone "experts" on the show floor. I assume
> this means that he is a member of the iPhone product team. He told me
> that no decision has yet been made on whether or not to include Java
> on the phone and, if so, to use J2SE or J2ME. He also said that the
> phone does use Cocoa but that it is "not an open system".
>
> I asked specifically if individual developers could write applications
> for the iPhone and the answer was not yet, but that Apple would listen
> to input from developers when deciding how or if third-party
> applications could run on the phone. He agreed with me that filing a
> Radar request would be the best way to for developers to let Apple
> know about their interest in writing third party apps for the iPhone.
>
> He also confirmed that although the home screen of the iPhone looks
> like Dashboard and the applications are called Widgets, it does not
> use the same technology and standard Widgets will not run.
Also:
* No 3G. As someone put it: "We know you know, but still, it hurts man"
* No over the air iTunes Store downloads or WiFi syncing to your host machine.
* No expandable memory.
* No removable battery.
* No Exchange or Office support.
* Not much news on the Safari implementation, Flash support etc
Considering that the device will not be available in Europe before the autumn, I also think that a 2MP camera will look decidedly low-key for potential buyers by then. There are several 3.2MP phones out now and even a 5MP.
Don't get me wrong, it's a beautiful device and the interface looks fantastic. It misses a few tricks though, and like so many Apple concepts, it all looks rather 'closed' and proprietary.
W