Saturday, April 10, 2010

iPhone Development Just Got Harder

When I look into buying a new phone this year I look at a lot of things (does it have a camera, are there apps available , does it have a nice data plan, does it have 3G and Wifi etc) but as a developer I mostly want to code for it... That is why my current phone is a Windows Mobile device since I can easily use MS Visual Studio.Net with C# without having any other cost.

The iPhone is a great device (like the new iPhone 4G will b even better) but its hard to code for it, a big disadvantage.... You need to buy a Mac, learn Objective C or some other tool (like MonoTouch etc), pay the USD $99.00 per year (that isn't actually very bad if you got the money)

With the release of the new terms and conditions for the iPhone OS 4.0, Apple disallow applications not written in C / C++ or rather Objective C.... Development just got harder!

I just want Apple and everyone to remember, for us developers and companies its about USERS/CUSTOMERS... If we can't develop applications easily because a platform is closed down then its the USERS/CUSTOMERS that will suffer since they will not get the kind of applications that they want.

THE USER / CUSTOMER MUST B MORE IMPORTANT, ALWAY!!

I hope this will change for Apple else I will go for another platform like Android where I can actually use a tool like Java to code or go for Windows Phone 7 where you can use MS Visual Studio.Net 2010.

3 comments:

Ewald Horn said...

Ugh!

Come on!

Didn't Apple learn ANYTHING from their Mac experience? If you think about it, they tried this in the past - closed systems that are darn near impossible to integrate with.

From a developer perspective it's just insane to code for something that's got very little market share and even less support in the developer community.

I think the iPhone can't run Java ME apps, right? So now, if you want to write an application, you need to write one for iPhone AND another for whatever your other mobile targets are. Given the limited language choice as well, and the fact that it's only for Apple, it doesn't make sense to invest all that time and effort.

Now, with Android you know that more and more phones will support it, so there is a life-expectancy on your code, a great thing. With the Apple... Nope, you don't know if any of what you do for it can be reused, something that is becoming more and more important in a market where new mobile device models pop up almost every day.

Here's a little note to the iPhone decision makers : This mistake has been made before, by YOUR company. Get real, be part of the global market or die out, again.

The iPod rescued Apple, the iPhone was set to make them a serious player in the mobile device market, but, alas, it seems they really dropped the ball on this on.

Just shows you - old apples do rot away with time.

Lennie De Villiers said...

Hi Ewald: We can all blame our "friend" Steve Jobs... that is all his fault. Same reason why they don't want Flash on the iPhone - its all personal just like it was years ago between Bill Gates vs Steve Jobs. Steve Jobs is making it personal and so all the customers suffer. The iPhone does have a big market share in the USA etc but not much in SA and yes your unfortunately stuck where you need to do development for both. So for all the other platforms you need to use Java or .Net (like Windows Phone 7) and for iPhone nasty Objective C. Tools like PhoneGap etc is not gonna exist anymore.

Ewald Horn said...

Yup - these two really need to retire so we can get some sanity back into the IT world. OR we should all just go Linux :)