This document introduces you to the iPhone environment and how it shapes the user experience of iPhone content. Then, it explains how to design a superlative user interface for your web content so it displays and works well on iPhone. It does this by first examining different types of iPhone content and exploring how you can decide which type to create. It then discusses how to apply user interface design principles to iPhone content, and finally provides numerous metrics and guidelines to help you handle specific design issues. For the implementation details and guidance you need to write the code for your iPhone product, see the See Also section below.

Wonder what Jobs means by "more intimate apps" when he answered this question at the London event?

Quote

10:37 - Q: Have you thought about opening the iPhone to 3rd parties?

Steve: "Yes, we've already done that with Web 2.0. We're looking at more intimate apps. But people hold their phones to a higher standard than their PC. The more open you are, the less predictable." Again, same ol' same ol'.

There are a few good examples of sites actually implementing the stuff Apple is talking about in this HIG. That is not to say they read it, they may just known how to design a good website, but it would be nice to see some others follow their lead.

i.wund.com and iphone.facebook.com are both fantastic. i would really like to see one for netflix and for either blogger or wordpress. that will be enough to hold me over until these "more intimate" applications come along.

I think eventually Apple will allow 3rd party apps, possibly as soon as MacWorld. I really think they just want to get a lot of iPhones out there and get the majority of the minor problems worked out before they allow these apps. It is also likely that if Apple does this, they have some cool apps up their sleeves. I say give it another 3-6 months before we rule out any chances of ever having Apple support 3rd party apps.

To me it seems very very obvious Apple is going to allow 3rd party apps. The release of these guidelines for web apps is just another step in that direction. However, they are going to want to have a firm grip on what is being released, so phone functionality, security and overall usability will not be jeopardized by bad, malicious, unexperienced or lazy developers. Therefore, I am convinced they will, in time, release an iTunes only install tool, with applications for sale (or for free in some cases) through iTunes. They are going to want to sign each and every app that becomes available for compliance with iPhone usability guidelines and security guidelines. AND they are going to want a piece of the pie of software development, taking in a profit for each app being sold.

And this is probably a very smart move. For phones, more so than for computers as Jobs said, interface usability and phone security is trickier than for computers.

Usability
Computers have a fairly well know interface architecture (which is actually not that great, but at least it's known), so app interfaces developed for computers automatically fit in reasonably well with what people expect and have come to know. Not so for the iPhone interface, which is completely new. So extra thought has to go into making applications usable, as Apple has meticulously done for the applications already available. Even experienced software developers (read: the biggest one ) have perpetually shown to be really bad at designing usable interfaces. So they are going to want a whip to beat developers with to focus on usability.

Security and functionality
Imagine people secretly installing backdoors in apps allowing them to e-mail off the contact lists of iPhone owners to spammers. Imagine a sprawling of unusable apps developed by 16 year old pimple faces, crashing iPhones all over the place. This would REALLY be bad for the iPhone.

So don't count on an SDK for the general public. IMO it is all going to be tightly controlled by apple, and this is going to bring really great apps. We just need a little patience. And for those who do not have patience, they can simply stick with 1.0.2

My biggest complaint with web apps is the lack of sound. It's like watching a movie with a missing soundtrack. It sucks. I don't care how smooth you can get your web apps to work online or how wonderful and user friendly they are, but if you can't get physical feedback (no buttons) and no audio feedback (no sound), what's the point.

It's a f**king iPod that makes phone calls, I would think that sound would be slightly important when developing something for it.

I couldn't disagree more and I think Ars have it spot on. It not just the currently part, it's the fact the statement is there at all and the way it is worded.

If Apple had no intention of releasing a 3rd party SDK, I doubt they would publicly go to the trouble of releasing HIGs. They already have developer guidelines.

This is the exact quote (in a special box on the document).

Quote

"Note: Currently, developers create web applications for iPhone, not native applications. Therefore, this document focuses solely on the presentation of web applications and other web content on iPhone."

Click to expand...

Reading between the lines that says:

- No SDK yet
- But in the future this document will be updated to so it is applicable to native apps.

I also think it is funny how Apple have released HIGs for iPhone, but seem to have almost abandoned them for the Mac.

"Intimate" may not mean Cocoa apps. It may just mean widgets, which would still be an improvement over what we have. I'm not sure if I'd call widgets "native", which would explain the discrepancy in his language.

I also think it is funny how Apple have released HIGs for iPhone, but seem to have almost abandoned them for the Mac.

Click to expand...

i think we'll see an update to the mac developer's HIG with the release of 10.5... and if not, whatever... they are simply guidelines, and in some cases (like "use textured windows only for apps that require hardware") they're kinda silly...

i assume an SDK will be released for iPhone eventually... perhaps after the OS has matured enough to support a good one... until then, it's developers = webdesigners...

Click to expand...

As a native iPhone developer (I did web design for iPhone originally, but I realized that the platform sucked for creating anything polished--there's no way to use the items you'd need to create an app that behaved like the native iPhone ones, just a poor ugly imitation), I'm at least a little offended by your comment.

The native development community is alive and well, and growing daily. Still hoping Apple will release an SDK, but for now, the SDK the iPhone Dev Team has put together is good enough to create some pretty impressive apps.

I think eventually Apple will allow 3rd party apps, possibly as soon as MacWorld. I really think they just want to get a lot of iPhones out there and get the majority of the minor problems worked out before they allow these apps. It is also likely that if Apple does this, they have some cool apps up their sleeves. I say give it another 3-6 months before we rule out any chances of ever having Apple support 3rd party apps.

Click to expand...

I agree, give them some time to let the platform simmer and be widley distributed. These guys know what they are doing. After all they developed the iPhone.

set the viewport width and height properties to ensure your content fits the screen precisely. In addition, you’ve turned off user-scaling so your application looks right in both portrait and landscape orientation.

Click to expand...

Even Google is better, at least it fits properly on the screen, and the buttons don't overlap the fields.

MacRumors attracts a broad audience
of both consumers and professionals interested in
the latest technologies and products. We also boast an active community focused on
purchasing decisions and technical aspects of the iPhone, iPod, iPad, and Mac platforms.