Facebook have begun to roll out their new profile design: Timeline, to iPhone through the mobile optimized version of their website. The redesign features most of the important features of Timeline.

• Viewing and changing Cover Images.
• Scrolling back through time – from birth to the present day

Other features are missing, like the ability to add ‘life events’, or change the date of photos to have them listed accurately in your timeline, but overall the interface is really nice.

The new timeline interface is only viewable on profiles that have enabled them on the normal website. Timeline hasn’t rolled out on the iPad, or the native app, but no doubt it will be soon.

Source: m.facebook.com

Cameron Daigle‘s “is the iPad just a big iPhone” user interface presentation from PodCamp Nashville. Note, the second slide is a gigantic “NO.”

[via Daring Fireball]

Sebastiaan de With — aside from gritting his teeth and almost blinding himself in one eye while reproducing the incomprehensibly pin-striped logo above — has bent his design-focus and Cocoia blog towards an analysis of Apple’s new iPhone 3.0 user interface:

Sometimes, I’m considering if other companies in the cellphone / personal media player market have caught up to Apple’s care to details and design sensibilities, but then things like these make the reality very obvious to me:

Apple’s still the leader of the pack by several tail lengths.

If you’re into the details of user interface and design, give it a read and let us know what you think about the look and feel of iPhone 3.0.

Back before my iPhone was torn from me (sniffle) for the Round Robin, Twitteriffic was (and will be again) my mobile Twitter client of choice. Since TiPb has also been looking into App development and iPhone UI lately, this all added up to make Craig Hockenberry’s post today on furbo.org especially interesting. Hockenberry talks about the importance of making choices in development, about what features to add and what to leave out, and perhaps most importantly to us, in variety of different approaches:

There will always be more than one way to solve a problem: a developer’s personal preferences will inevitably seep into the implementation. Having many choices for a Twitter client means that developers don’t need to create a “one size fits all” solution. In essence, users get to choose a developer whose preferences match their own.

If you’re at all interested in a behind-the-curtains peak into what makes a good app great, be sure to read the whole article.

Also, let us know if you’re currently using Twitterrific, if what he mentions was already obvious to you, or if you’re using another Twitter client, what you’re using and why you prefer it?