1

One small and picky detail — Objective-C isn’t really a descendent of C, it’s a ‘strict superset’ of C. In other words, ObjC is C with objects added on. The object syntax is actually based on a language called Smalltalk.

posted at 09:43 am on August 17, 2010 by lhagan

2 There's other fruit than just apples

Excellent article, it helped a lot with my decision. I just had to find’n‘replace every apple and iphone with something more relevant, that is… desktop. I have no idea why the article is so Apple centric, and there’s no explanation for that in the text.

Just to make numbers clear: there is more Android phone out there than iPhones, and far more desktops/net/notebooks. So why the focus on web vs. iPhone?

I do follow ALA for years and it gave me so much, but this is first time I see such a consumer oriented (iPhone) focus.

posted at 10:32 am on August 17, 2010 by skrat

3 JavaScript is nothing like Objective-C

I know JS well, but I can do nothing with Objective-C. I can’t even understand the ObjC syntax.

They have different typing, and a lot of different concepts. There is no prototypes in ObjC (but there is something called “categories”), and no messages and protocols in JS. There is also different name binding rules and many other stuff.

Example in “Going native” section involves two different concepts: dynamic/static typing and dot-accessors/messages. It’s introduced like similar, but it’s not.

posted at 10:59 am on August 17, 2010 by scriptin

4

Thank you for the article. Still I’m not sure wether I should develop my “muscle learning app” strictly on the web or as an iPhone/Pad App.

posted at 11:35 am on August 17, 2010 by Robert Hauk

6 Universal design

Without any doubt, device and context specific web and native apps are powerful. However, in my opinion, you still need to optimize the interface as much as possible independent from the device and capabilities of the user as well.

posted at 01:33 pm on August 17, 2010 by glardon

7 Syntax

Interesting article. Not sure I quite agree with the notion that JS is similar to Objective-C. You have to deal with memory management for a start.

Also, correct me if I’m wrong but you have a syntax error in your Objective-C example. It should read…

BOOL beAwesome = YES;
NSString *myString = @“chocklock”;
if (beAwesome) { myString = [myString uppercaseString];
}

(Note the @ when assigning an NSString value)

Cheers

Chris

posted at 01:33 pm on August 17, 2010 by chrismwaite

9 FAIL

I want my 10 minutes back.

This article fails because it omits the obvious one single reason for iPhone App versus Web – everything has to do with the phone usability. The only paragraph that mentions usability even has the nerve to give code examples. Excuse me – users do not touch or care about tags. They might see the result, but the usability issue of iphone App versus web has to do with this: “App“s are presented in singular, graphical, isolated, low-friction one-click actions, where-as web pages require more intensive interaction. This is the one, first and foremost reason why the two dimensions battle on the iPhone and why the iPhone and App concept is succesful in the first place.

A List Apart – you can do better. I thought this blog was meant for user experience professionals.

posted at 02:47 pm on August 17, 2010 by thomasg