Analyzing Apple's iPhone Strategy

Galen Gruman submitted infoworld's summary of Apple's grand strategy for the iPhone. He points out that the real important part of the new iPhone is the software, not the hardware. He talks about the new SDK stuff, the ad-hoc app distribution, and other stuff. It's a reasonable read if you have been ignoring the iPhone and want to know what the hype is about over this release, but doesn't break any new ground if you've been paying attention.

Comments

it's the apps, stupid!

[AceJohnny]

He points out that the real important part of the new iPhone is the software not the hardware. Well sure, now that the smartphone hardware is becoming powerful enough that you don't have to constrain your app to the capacities of that hardware, people are starting to realize that the hardware is actually inconsequential.

But this shift has only happened recently, and we needed something like the iPhone to show us that the hardware is actually darn good enough!

This is also why I'm so fascinated by Android, which is a powerful software platform (ok, for a given set of hardware). ...and I say this as an embedded software developer :p

Re:Strategy?

[porcupine8]

Yeah, I've actually been surprised - every single person I've known with an iPhone, I've seen using its non-phone features. Getting directions via Google maps, using Twitter, using the calendar, whatever. Usually you do see people paying way too much and then only using the most basic features, but people seem to actually be using iPhone as more than a standard phone.

Re:Objective C

[ImdatS]

You know, I started developing in Objective-C back in 1990/91 on NeXTstep (yes, it was lc 'step' at that time...) - Coming from Pascal, C, Forth (and some Basic dialects), I found it a bit weird at the beginning (the first 4-6 months). Then, one day, it made "click" - as we say in German. And from that day on, I couldn't really imagine doing it in a different way than MVC & Objective-C.

In order to fully grasp it, I started experiments with Smalltalk (great), Eiffel (great, but ugly syntax), and some other languages I forgot.

Remember: those times were the times when we wrote our frameworks ourselves (I remember writing objects like "Float", "Integer", "String", ... - they didn't exist in NeXTstep those days).

You have to switch from "Calling a Function" or "Calling a Member of an Object" to "Sending a Message to an Object" and get used to the idea that everything is an Object (even classes are instances of the class class and so on) and then you are set.

The syntax may turn you off a bit - that's what happens with Python for me (the indentation is still a psychological issue for me) - but you surely get used to it quickly.

Now, after having developed in Objective-C for such a long time (including having learned Smalltalk and Eiffel), I can't actually look at the "ugly" C++ or Java syntax - and I (more or less) believe the worst thing that could happen to the world in programming languages was C++ (my two EUR 0.01, which, by the way, results in 3.14 UScents by a strange coincidence today).

Anyway, try it out and you'll either hate it or love it.

Also, for me, a good programmer is someone who is personally, privately, and passionately interested in Esoteric Programming Languages - which brings us to the "Indifference to Syntax" - or "Being amazed by Syntax" (some people should probably take this with a grain of salt).