fetzig!

Workaround for iPhone's Smart Playlist bug

There is a bug (do a search for smart playlist in this forum) with smart playlists not displaying the correct songs on the iPhone.

I just tried something that seems to have worked…

I have a playlist in iTunes called “Recently Added” which I want to keep synced with my iPhone.

I created a new smart playlist called “Recently Added (iPhone)”. The playlist has one rule: “Playlist is Recently Added” with live updating checked.

I now sync this second playlist with the iPhone and all the correct songs show up in it.

Posted: Aug 3, 2007 10:38 AM

and still helpful in 2010. What up Apple?

Note: I sync “Playlist” and “Playlist (iPhone)” (otherwise I get a error from iTunes). Works with podcast smart playlists too.

learning from facebook about mobile webpages...

(This is a excerpt of small research project. I’m no expert when it comes to mobile websites. So this is no review or something like that.)

there are, as far as i know, 3 versions of facebook:

• facebook as is facebook.com
• the mobile version m.facebook.com
• the touch version *fancy* touch.facebook.com

facebook.com:

XHTML 1.0 Strict / CSS / Javascript

I think they make an explicit check against the user agent string.

if you make a request to (www.)facebook.com:

• Android: -> touch.facebook.com
• iPhone: -> touch.facebook.com
• [some mobile with browser]: -> m.facebook.com

Weird thing is: If you request some facebook link (i.e. from a event) the iPhone gets redirected to m.facebook.com (bug?).

m.facebook.com:

XHTML Mobile 1.0 / CSS / NO JavaScript

very simplified version of facebook. thus very useful, fast and works on pretty much all (mobile) browsers.compressed, compressed and compressed: gzip, minified js, css and html. when it comes to validation the css seems to be w3c valid. html not - pretty much because of the forms/form items.

touch.facebook.com:

no doctype HTML / CSS / JavaScript

Very cool. (In my opinion even cooler than the iPhone facebook app.)

Little bit bigger (fonts/input fields) than the m.facebook.com version. Still minimalistic -> great user experience.

NOTE: <u> tags to create custom submit buttons.

Conclusion:

Mobile phones with touchscreen seem to be worth supported. Statistics tell the same iPhone and Android based Smartphones have a big market share. So they get a own version. All other phones get redirected to a very generic mobile version.