iPhone Analysis Part 2 - Not Closed For Sure

In my previous post on the iPhone, I said that I thought Apple’s biggest mistake with iPhone was to make it a closed device. That is, it was looking like Apple would not allow third-party independent developers to build applications for iPhone. However, I may have some good news….

I’ve just been told that, while they might so far be leaning towards making iPhone closed, the powers that be at Apple haven’t actually taken a final decision on this. And, in fact, to this end, they’re still considering putting Java on iPhone. So, if enough Apple developers make it known to Apple that they want to develop applications for iPhone, they may well get their wish.

For what it’s worth, I think Apple should ship either Java SE, or the CDC version of Java ME (not CLDC) with iPhone. I don’t mind which - whatever makes most sense for the hardware (I’m guessing it’s a Samsung ARM chip in there, but I could be wrong). And, it would be great to have as many JSRs as they can put in there, to let developers interact with the phone hardware and other features.

Having said that, the key thing with any Java implementation for iPhone is that Java apps on iPhone need to be first-class applications. That is - they need to look and feel just like native apps. That means Apple would need to ship a special Java class library that lets developers deal with multi-touch gestures; and also interact with the fantastic graphics etc. Also, it needs to be easy for anyone to build and deploy applications for the phone e.g. they could make the development environment work well in Netbeans. The big benefit of Java for device makers, of course, is that they can ensure that developers can’t screw the phone up, and cause problems on the phone network, because of a buggy application.

I really it hope this happens. iPhone would be an incredible device to develop applications for, and the developer community could do some amazing things with this platform, if they’re given the right tools. So, if you’re an Apple developer, please let Apple know if you want to develop applications for iPhone!

I don’t think Apple could have all this ready for launch. But, it might not take too long, if the right people can only be persuaded to make the relevant decisions.

Trackbacks & Pings

  1. MyMicroISV » iPhone - Open or Closed? on 11 Jan 2007 at 8:17 pm

    [...] According to this report, the decision has not been made. If you know any Apple exec’s now is a good time to ring their bell about this, or at least join this petition. Do you as developer want an open or closed future? [...]

Comments

  1. Bob Walsh wrote:

    But the question is, who told you? Are they someone who is in a position to really knpw?

  2. simon wrote:

    Well, it wasn’t Steve Jobs ;-) So, from that perspective, no they wouldn’t really know, would they?! I would say it’s pretty good information though. If I had to put a percentage on the accuracy, I would say there’s probably a greater than 70% chance of it being on the money.

  3. Asam Bashir wrote:

    Sign up for free, http://developer.apple.com/

    developer forums there..

  4. Asam Bashir wrote:

    All they need to do is add an OS X pluggin to the existing Xcode development platform..

  5. Asam Bashir wrote:

    http://developer.apple.com/leopard/overview/dashcode.html

    all those apps in iPhone, like the weather are just Mac OS X widgets, identical to ones already in Tiger….

  6. Asam Bashir wrote:

    Java SE 6.0 Release 1 Developer Preview 6
    Java Platform, Standard Edition 6 Release 1 is based on JDK 1.6.0_b88 and brings enhanced functionality to Java applications.

  7. Asam Bashir wrote:

    Yah, I still got my top secret killer java app idea - n now I got the hardware to go with it ;)

  8. simon wrote:

    Asam, I don’t think OS X widgets on Macs and iPhone are the compatible. Clearly, Apple has built a little widget platform for iPhone, but I doubt it’s the same one that the Mac uses.

    I don’t know for sure - just how it looked to me - that’s why Apple only had two iPhone widgets ready to go.

  9. Steve wrote:

    Why do we need Java on the iPhone???

    I really don’t think the world will miss it. There’s no device like this in the Java world, so what knowledge are you going to bring forward to help you develop your apps? You’re going to have to learn a new set of class libraries anyways.

    Let go of Java, use Objective-C (I’m sure this will be the preferred way). The world doesn’t need Java on an iPhone, what it needs is apps and developers who aren’t afraid to let go their insecurities and self-doubt and do something a little different.

  10. simon wrote:

    Steve,

    I agree that iPhone needs, “apps and developers”. And I agree that Java isn’t needed as much as the iPhone needs to be open. So, if Apple were to let developers build iPhone apps using Objective-C, that would be great. Objective-C is a fine language.

    But, you know, the Java thing really isn’t about “insecurities and self-doubt”. Not sure why you would think that. No, it’s about applications.

    There are well over a billion Java-enabled devices deployed currently; and 80% of new mobile devices have Java. I don’t agree that there aren’t any devices like iPhone in the Java world. iPhone is unique (for the moment) only in that uses a gesture-based user interface.

    So, there’s a huge volume of Java ME code out there, making use of a multitude of Java standards for interacting with phone features and hardware. This code could be rapidly ported to iPhone if it had Java ME and the relevant JSRs… meaning lots of choice of apps for iPhone owners…

Post a Comment

Your email is never published nor shared. Required fields are marked *

*

*